Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1654622 [details] journal 1. Please describe the problem: Gnome-shell suddenly freezed while watching a youtube video in Firefox and some other applications running. I had to hard-reset the system. 2. What is the Version-Release number of the kernel: kernel-5.4.12-200.fc31.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : It firsst appeared in the 5.4.z series 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: It has happened a couple of times. Firefox was the main application, but not sure how to reproduce. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: I haven't tried that 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. Secure boot is enabled. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Created attachment 1654623 [details] /sys/class/drm/card0/error
I do get similar crashes all the time I'm using Slack or Zoom for video conferencing and switching graphical tasks. A colleague at work mentioned that this is a known i915 bug introduced back in Linux kernel 5.2ish times and still not fixed? In the system journal it looks as follows: Jan 24 13:16:25 marcel-nb-toradex-int kernel: perf: interrupt took too long (2541 > 2500), lowering kernel.perf_event_max_sample_rate to 78000 Jan 24 13:16:51 marcel-nb-toradex-int kernel: i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0 Jan 24 13:16:51 marcel-nb-toradex-int kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 24 13:16:51 marcel-nb-toradex-int kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 24 13:16:51 marcel-nb-toradex-int kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 24 13:16:51 marcel-nb-toradex-int kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it. Jan 24 13:16:51 marcel-nb-toradex-int kernel: GPU crash dump saved to /sys/class/drm/card0/error Jan 24 13:16:51 marcel-nb-toradex-int kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Jan 24 13:16:51 marcel-nb-toradex-int kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Jan 24 13:16:51 marcel-nb-toradex-int kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0 Jan 24 13:16:51 marcel-nb-toradex-int kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Jan 24 13:16:51 marcel-nb-toradex-int kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} ... Jan 24 13:19:43 marcel-nb-toradex-int kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 Jan 24 13:19:48 marcel-nb-toradex-int audit[3209]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3209 comm="GpuWatchdog" exe="/opt/google/chrome/chrome" sig=11 res=1 Jan 24 13:19:48 marcel-nb-toradex-int kernel: show_signal_msg: 3 callbacks suppressed Jan 24 13:19:48 marcel-nb-toradex-int kernel: GpuWatchdog[3225]: segfault at 0 ip 0000558654d67ded sp 00007f05ea947500 error 6 in chrome[558650e2c000+7171000] Jan 24 13:19:48 marcel-nb-toradex-int kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 <c7> 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80 7d 8f 00 Jan 24 13:19:48 marcel-nb-toradex-int systemd[1]: Started Process Core Dump (PID 43752/UID 0). Jan 24 13:19:48 marcel-nb-toradex-int audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-43752-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 24 13:19:48 marcel-nb-toradex-int google-chrome.desktop[2319]: --2020-01-24 13:19:48-- https://clients2.google.com/cr/report Jan 24 13:19:48 marcel-nb-toradex-int google-chrome.desktop[2319]: Resolving clients2.google.com (clients2.google.com)... 172.217.168.78, 2a00:1450:400a:803::200e Jan 24 13:19:48 marcel-nb-toradex-int google-chrome.desktop[2319]: Connecting to clients2.google.com (clients2.google.com)|172.217.168.78|:443... connected. Jan 24 13:19:48 marcel-nb-toradex-int systemd-coredump[43756]: Process 3209 (chrome) of user 1000 dumped core. This is on a ThinkPad T470p and yeah, Google Chrome was also running dumping core. I believe this started about two weeks ago still on 5.3 something? Now I am on latest 5.4.12-200.fc31.x86_64.
In my case, the system is not entirely dead (responds to ping), but since GPU is frozen, there's no choice but to reboot. I'm on 5.4.13-201.fc31.x86_64. The crashes seem to be prompted more by Rambox, which is an Electron application. That's like having several browsers overlaid (one for each of Discord, Slack, and Google channel). With Rambox the freeze happens a couple times per day. But it happens with just Firefox, too, just not as often.
Got the same crash few times since updated to fedora 30 # uname -a Linux happyfed 5.4.17-100.fc30.x86_64 #1 SMP Sat Feb 1 19:15:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I think it's usually happened when some video playing. When this hang happened "num lock/caps lock" were unresponsive so rebooted my lap. [ 957.145672] perf: interrupt took too long (2523 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 2070.376857] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0 [ 2070.376860] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2070.376862] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2070.376863] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2070.376864] The GPU crash dump is required to analyze GPU hangs, so please always attach it. [ 2070.376865] GPU crash dump saved to /sys/class/drm/card0/error [ 2070.377875] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [ 2070.378665] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [ 2070.378852] i915 0000:00:02.0: Resetting chip for hang on rcs0 [ 2070.380641] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [ 2070.381416] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [ 2078.377748] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [ 2086.377690] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [ 2094.377644] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
Created attachment 1662569 [details] dmesg of a hang in F31
Created attachment 1662570 [details] /sys/class/drm/card0/error in F31
Still hangs in kernel-5.4.17-200.fc31, I attached a couple of diagnostic files.
I can confirm still getting a rare hang but at least it no more freezed do far on my T470p. I may add more information later today when I get it again.
Created attachment 1662686 [details] Unrecoverable Hang on 5.4.17-200.fc31.x86_64
Created attachment 1662766 [details] Recoverable Hang on 5.4.17-200.fc31.x86_64
5.4.19-200.fc31.x86_64 and still freezing completely none recoverable!
I am on Fedora 31 and with recent updates (last few days from now) it's failing on my laptop too. It seems to only happen while I am using Slack. I can recover by closing the laptop lid and opening it again (this doesn't work always). I am running kernel: 5.4.19-200.fc31.x86_64 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz [..] [20638.754387] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0 [20638.755428] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20638.756195] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [20638.756286] i915 0000:00:02.0: Resetting chip for hang on rcs0 [20638.758025] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [20638.758765] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} [20642.786410] Asynchronous wait on fence i915:gnome-shell[2175]:731d0 timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915]) [20648.738386] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20656.738357] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20658.722362] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20660.706360] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [..] [20704.082792] show_signal_msg: 56 callbacks suppressed [20704.082794] GpuWatchdog[5266]: segfault at 0 ip 000055c6829cbe32 sp 00007f1f6c18e500 error 6 in chrome[55c67ea85000+7287000] [20704.082799] Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0 0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17 a6 fe <c7> 04 25 00 00 00 00 37 13 00 00 c6 05 2c 74 b9 03 01 80 7d 8f 00 [20704.738319] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20706.722322] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20708.706313] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20710.754330] i915 0000:00:02.0: GPU recovery timed out, cancelling all in-flight rendering. [20710.754491] i915 0000:00:02.0: Resetting chip for hang on rcs0 [20718.754302] i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0 [20722.146330] Asynchronous wait on fence i915:gnome-shell[2175]:731d4 timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915]) [20726.755315] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20728.739296] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20730.723293] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20732.708284] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20734.755291] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20735.855095] GpuWatchdog[117840]: segfault at 0 ip 0000561f64014e32 sp 00007f5d1ce8e500 error 6 in chrome[561f600ce000+7287000] [20735.855100] Code: 83 c3 e8 75 e9 41 8b 85 00 01 00 00 85 c0 0f 84 99 00 00 00 48 8d 3d 63 61 4b fb be 01 00 00 00 ba 03 00 00 00 e8 fe 17 a6 fe <c7> 04 25 00 00 00 00 37 13 00 00 c6 05 2c 74 b9 03 01 80 7d 8f 00 [20736.739235] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [20738.723282] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 [..]
Still there on 5.4.20-200.fc31.x86_64. But this time it got unstuck [zaitcev@suzdal ~]$ dmesg | tail -2 [269301.327817] i915 0000:00:02.0: GPU HANG: ecode 9:1:0xeacfffff, in Xwayland [2319], hang on rcs0 [269301.328847] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
For me the issue went away after an update which incl. 5.5.5-200.fc31.x86_64
The 5.5.5-200.fc31.x86_64 fixes the problem for me too.
I haven't reproduced the problem with 5.5.5 either.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Can't reproduce with 5.5.7
Thank you for letting us know.