Crashes at gpusGenerateCrashLog with graphics hardware errors '0x00000813', '0x00000803', '0x00008013', '0x00000003' and '0x00008003'
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: smichaud, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: topcrash, topcrash-startup)
Crash Data
There have been several of these recently, all on Intel graphics hardware, using the "AppleIntelKBLGraphics" drivers:
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.
Updated•3 years ago
|
Reporter | ||
Comment 1•3 years ago
|
||
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"
}
]
}
Reporter | ||
Comment 2•3 years ago
|
||
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"
}
]
}
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Comment 3•3 years ago
|
||
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"
}
]
}
Reporter | ||
Comment 4•3 years ago
|
||
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"
}
]
}
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Comment 5•2 years ago
|
||
Closing because no crashes reported for 12 weeks.
Reporter | ||
Comment 6•2 years ago
|
||
These are still happening, and under the same signature(s). But for some reason the signature(s) are being recorded differently:
Reporter | ||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
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.
Reporter | ||
Comment 8•2 years ago
|
||
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.
Updated•2 years ago
|
Comment 9•2 years ago
|
||
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•1 year ago
|
||
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.
Description
•