i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
This is on Ubuntu focal development series, with latest kernel 5.4.0-13-generic, with patch for #673 (closed) cherry-picked in
Mesa is 19.3.3, this is a ThinkPad T480s with an i5-8250U, connected to an external monitor via USB-C, running Hangouts Meet in a browser window, amongst other things.
Relevant dmesg log:
[10161.268097] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
[10161.268101] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[10161.268103] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[10161.268104] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[10161.268106] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
[10161.268107] GPU crash dump saved to /sys/class/drm/card0/error
[10161.269122] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[10169.272831] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[10650.592176] mce: CPU3: Core temperature above threshold, cpu clock throttled (total events = 2113)
[10650.592177] mce: CPU7: Core temperature above threshold, cpu clock throttled (total events = 2113)Activity
Same issue, system freeze.
Fist time - work in vscode + firefox
Second time - Work in OBS - while configuration wizard making some fps testsOS: Clear Linux OS x86_64
Host: HP Spectre x360 Convertible 15-bl1XX
Kernel: 5.4.18-902.native
CPU: Intel i7-8550U (8) @ 4.000GHz
GPU: Intel UHD Graphics 620
GPU: NVIDIA GeForce MX150Edited by Alexander CherryTea@Akiyamka that looks like #673 (closed) though. This is specifically a bug that still occurs after the fix for that has been cherry-picked. There's a reason dmesg tells you to report a new bug rather than just commenting on another one.
@julian-klode you right, i create separate issue #1164 (closed)
marked this issue as a duplicate of #1164 (closed)
