1714235 - Crashes at gpusGenerateCrashLog with graphics hardware errors '0x00000813', '0x00000803', '0x00008013', '0x00000003' and '0x00008003'

Status: REOPENED

(Core :: Graphics, defect, P3)

Description

[Steven Michaud [:smichaud] (Retired)]

There have been several of these recently, all on Intel graphics hardware, using the "AppleIntelKBLGraphics" drivers:

https://crash-stats.mozilla.org/search/?mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset&date=%3E%3D2021-05-03T00%3A17%3A00.000Z&date=%3C2021-06-03T00%3A17%3A00.000Z&_facets=signature&_facets=mac_crash_info&_facets=platform_version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-mac_crash_info

The mac_crash_info in all of them is as follows:

    {
      "num_records": 2,
      "records": [
        {
          "message": "abort() called",
          "module": "/usr/lib/system/libsystem_c.dylib"
        },
        {
          "module": "/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib",
          "signature_string": "Graphics hardware encountered an error and was reset: 0x00000813\n"
        }
      ]
    }

The "context error" is set to this value by a call to IOAccelContext2::affectedByHardwareReset(bool, unsigned int) in the IOAcceleratorFamily2 kernel-mode graphics driver, called from IOAccelFIFOChannel2::restart(). It gets the error number from IGAccelFIFOChannel::getHardwareDiagnosisReport(unsigned int*) in the AppleIntelKBLGraphics kernel-mode graphics driver. This method calls IGHardwareRingBuffer::doHangAnalysis() and IGHardwareRingBuffer::generateHangSig().

I haven't managed to figure out how the error number is generated, or what it means.

Comment 1

[Steven Michaud [:smichaud] (Retired)]

There are similar errors on Intel "AppleIntelICLGraphics" drivers:

bp-3d4c7732-daf1-4627-9f5b-bc1810210603

    {
      "num_records": 2,
      "records": [
        {
          "message": "abort() called",
          "module": "/usr/lib/system/libsystem_c.dylib"
        },
        {
          "module": "/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib",
          "signature_string": "Graphics hardware encountered an error and was reset: 0x00000803\n"
        }
      ]
    }

Comment 2

[Steven Michaud [:smichaud] (Retired)]

And similar errors on Intel "AppleIntelHD4000" drivers:

bp-09dd3dd5-53bb-4c55-bf28-6b4540210603

    {
      "num_records": 2,
      "records": [
        {
          "message": "abort() called",
          "module": "/usr/lib/system/libsystem_c.dylib"
        },
        {
          "module": "/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib",
          "signature_string": "Graphics hardware encountered an error and was reset: 0x00008013\n"
        }
      ]
    }

Comment 3

[Steven Michaud [:smichaud] (Retired)]

And similar errors on Intel "AppleIntelHD3000" drivers:

bp-8801cb18-e89a-4b86-af57-83acf0210604

    {
      "num_records": 2,
      "records": [
        {
          "message": "abort() called",
          "module": "/usr/lib/system/libsystem_c.dylib"
        },
        {
          "module": "/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupport.dylib",
          "signature_string": "Graphics kernel error: 0x00000003\n"
        }
      ]
    }

Comment 4

[Steven Michaud [:smichaud] (Retired)]

And similar errors on Intel "AppleIntelHD5000" drivers:

bp-61826652-3efc-4cf7-8748-eed890210605

    {
      "num_records": 2,
      "records": [
        {
          "message": "abort() called",
          "module": "/usr/lib/system/libsystem_c.dylib"
        },
        {
          "module": "/System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib",
          "signature_string": "Graphics hardware encountered an error and was reset: 0x00008003\n"
        }
      ]
    }

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.

Comment 6

[Steven Michaud [:smichaud] (Retired)]

These are still happening, and under the same signature(s). But for some reason the signature(s) are being recorded differently:

https://crash-stats.mozilla.org/search/?mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000813&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000803&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00008013&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000003&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00008003&platform=Mac%20OS%20X&date=%3E%3D2022-10-19T04%3A16%3A00.000Z&date=%3C2022-10-26T04%3A16%3A00.000Z&_facets=signature&_facets=mac_crash_info&_facets=proto_signature&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 desktop browser crashes on Mac on release (startup)

:bhood, could you consider increasing the severity of this top-crash bug?

For more information, please visit auto_nag documentation.

Comment 8

[Steven Michaud [:smichaud] (Retired)]

These crashes are still happening in significant numbers (53 in the last week). But that's still many fewer than tracking by signature indicates. There are serious disadvantages to tracking bugs only by signature.

https://crash-stats.mozilla.org/search/?mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000813&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000803&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00008013&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00000003&mac_crash_info=~Graphics%20hardware%20encountered%20an%20error%20and%20was%20reset%3A%200x00008003&platform=Mac%20OS%20X&date=%3E%3D2022-11-03T16%3A50%3A00.000Z&date=%3C2022-11-10T16%3A50%3A00.000Z&_facets=signature&_facets=mac_crash_info&_facets=proto_signature&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit auto_nag documentation.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criteria:

• Top 20 desktop browser crashes on release (startup)
• Top 5 desktop browser crashes on Mac on release (startup)

For more information, please visit BugBot documentation.

Comment 11

[BugBot [:suhaib / :marco/ :calixte]]

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.