Bug 1714235 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

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. This method is called from `IOAccelFIFOChannel2::restart()` in the same module, and 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.
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.

Back to Bug 1714235 Comment 0