Random freezing with "Resetting rcs0 for hang on rcs0"

Hi All,

Since the latest update from 29/12/2019 ([Stable Update] 2019-12-29 - Kernels, KDE Apps 19.12, Xorg-Stack, Mesa, Qt5) I am having problems with random freezing. And in every single occasion my log in flooded with "Resetting rcs0 for hang on rcs0" messages.

My specs:

Does anybody is having the same problem?

Another one (@sour ) having the same issue as me:

@mat250 and @Schlaefer in the same thread pointed to links with additional information:

After today's update ([StableUpdate] 2020-01-20 - Kernels, Plasma 5.19a, Pamac 9.3rc, Gambas, Virtualbox) no freezing yet.

Thanks @Rick !
I'll try this right now :star_struck:

Sorry @mat250, but my laptop just got frozen again :disappointed: , even after the latest update, so it seems that kernel 5.4.13 is causing the problem. Now I began using 5.3.18 to see if it works better.

After the reboot there was a message informing about a few updates, being kernel 5.4 (from 5.4.13-2 to 5.4.13-3) one of them, but I don't know if the problem was solved in that new version.

Damn it ! I haven't yet reboot my laptop to test :disappointed:
But thanks anyway to notify me about the update :hugs:

It looks like the only difference between 5.4.13-2 and 5.4.13-3 is this AMD GPU patch (0001-drm-amdgpu-allow-direct-upload-save-restore-list-for.patch).

Yeah... definitely it will not solve our problem.
Thank you for letting us now about it, though.

Known issue...

Should be fixed with linux55 though.

Thank you for the information @philm.

It's seem that the last release ([Stable Update] 2020-01-26 - Kernels, Pamac 9.3, GameMode, Brave, AMDVLK) fix some backports on i915 drivers. Check the changelog :wink:

I'll test that right now !

Thank you @mat250 for letting me know!

You're right! It was fixed in the last update. I just have looked in the logs and there was no messages related to problem anymore (and no more freezing too!). I was not waiting for a solution before the kernel 5.5 release.

Thank you @philm and the Manjaro team for the quick fix.

Yes and no more freeze for me too ! :tada:
Thanks @philm, the Manjaro Team and all Linux contributors :clap:

I'm sorry for telling you guys (@mat250 and @philm), but I just have had a freezing with the exactly the same log:

jan 31 09:13:51 gemini kernel: i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0                                                                                              │
│jan 31 09:13:51 gemini kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.                                                                          │
│jan 31 09:13:51 gemini kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel                                                                              │
│jan 31 09:13:51 gemini kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.                                                                     │
│jan 31 09:13:51 gemini kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.                                                                             │
│jan 31 09:13:51 gemini kernel: GPU crash dump saved to /sys/class/drm/card0/error                                                                                                           │
│jan 31 09:13:51 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           │
│jan 31 09:13:51 gemini kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}                                               │
│jan 31 09:13:51 gemini kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0                                                                                                           │
│jan 31 09:13:51 gemini kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}                                               │
│jan 31 09:13:51 gemini kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}                                               │
│jan 31 09:13:54 gemini kernel: Asynchronous wait on fence i915:xfwm4[5820]:1945c timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915])                                                 │
│jan 31 09:13:57 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           │
│jan 31 09:14:05 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           │
│jan 31 09:14:07 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           │
│jan 31 09:14:09 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           │
│jan 31 09:14:11 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0                                                                                                           ┤
│jan 31 09:14:13 gemini kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 

It seems that the problem persists...

EDIT: I forgot to include my specs, sorry.

inxi -Fxxxz
System:    Host: gemini Kernel: 5.4.15-2-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 
           info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Inspiron 7472 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Dell model: 082HPJ v: A03 serial: <filter> UEFI: Dell v: 1.2.1 date: 05/31/2019 
Battery:   ID-1: BAT0 charge: 39.9 Wh condition: 39.9/42.0 Wh (95%) volts: 12.7/11.4 model: SMP DELL Y3F7Y6B type: Li-ion 
           serial: <filter> status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 32012 
           Speed: 1476 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 1695 2: 1707 3: 1778 4: 1796 5: 1714 6: 1816 7: 1702 
           8: 1879 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 
           Device-2: NVIDIA GP108M [GeForce MX150] driver: N/A bus ID: 01:00.0 chip ID: 10de:1d10 
           Display: x11 server: X.Org 1.20.7 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.6 Mesa 19.3.2 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9d71 
           Sound Server: ALSA v: k5.4.15-2-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8168 v: 8.048.00-NAPI 
           port: d000 bus ID: 02:00.0 chip ID: 10ec:8168 
           IF: enp2s0 state: down mac: <filter> 
           Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel 
           port: d000 bus ID: 03:00.0 chip ID: 168c:003e 
           IF: wlp3s0 state: up mac: <filter> 
           Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-7:4 chip ID: 0cf3:e007 
Drives:    Local Storage: total: 1.03 TiB used: 519.47 GiB (49.4%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10SPZX-75Z10T2 size: 931.51 GiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 1A03 scheme: GPT 
           ID-2: /dev/sdb vendor: A-Data model: SU810NS38 SATA 128 GB size: 119.24 GiB speed: 6.0 Gb/s serial: <filter> 
           rev: 1101 scheme: GPT 
RAID:      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060 bus ID: 00:17.0 
           chip ID: 8086.282a rev: 21 
Partition: ID-1: / size: 898.75 GiB used: 480.08 GiB (53.4%) fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 17.12 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 69.0 C mobo: 38.0 C sodimm: 42.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 315 Uptime: 7m Memory: 15.54 GiB used: 3.55 GiB (22.8%) Init: systemd v: 242 Compilers: gcc: 9.2.0

No crash for me since the update (so 4 days ago), so sorry that you have this bug again :disappointed_relieved:
The kernel 5.5 is out now : maybe you should try it ?

Hi @mat250.

I am happy that the bug is not affecting you. Thank you for the tip. I just installed kernel 5.5 and rebooted my machine. Now I am using it and waiting to see if I will have any freezing.

I will give feedback here in few days time to tell if the new kernel solved my problem or not.

Cheers.

Hi. I have the same issue with GPU Hang on kernel 5.4. Unfortunately I can't use kernel 5.5 because of unstable wifi. So I keep using LTS kernel 4.19. No issues there.

1 Like

Hi @kainonergon .

Thank you for letting us know. If the problem happens in kernel 5.5 I will try to use 4.19 then.

Cheers

1 Like

Damn it. 5.4 is a big disaster anyways regarding Intel GPU's.
Now 5.5 seemed to be getting better until my sys just died (had to hard reset).
Back to 4.19...

Feb 01 21:59:56 T480s kernel: general protection fault: 0000 [#1] PREEMPT SMP PTI
...
Feb 01 21:59:56 T480s kernel: Call Trace:
Feb 01 21:59:56 T480s kernel:  i915_active_ref+0x65/0x180 [i915]
Feb 01 21:59:56 T480s kernel:  i915_vma_move_to_active+0x22/0x150 [i915]
Feb 01 21:59:56 T480s kernel:  i915_gem_do_execbuffer+0xd35/0x1860 [i915]
Feb 01 21:59:56 T480s kernel:  ? ttwu_do_wakeup+0x19/0x160
Feb 01 21:59:56 T480s kernel:  i915_gem_execbuffer2_ioctl+0x1df/0x3d0 [i915]
Feb 01 21:59:56 T480s kernel:  ? ____sys_recvmsg+0x98/0x190
Feb 01 21:59:56 T480s kernel:  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Feb 01 21:59:56 T480s kernel:  drm_ioctl_kernel+0xb2/0x100 [drm]
Feb 01 21:59:56 T480s kernel:  drm_ioctl+0x209/0x360 [drm]
Feb 01 21:59:56 T480s kernel:  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Feb 01 21:59:56 T480s kernel:  do_vfs_ioctl+0x4b7/0x730
Feb 01 21:59:56 T480s kernel:  ? _raw_spin_unlock_irq+0x1d/0x30
Feb 01 21:59:56 T480s kernel:  ? do_setitimer+0x12c/0x1f0
Feb 01 21:59:56 T480s kernel:  ksys_ioctl+0x5e/0x90
Feb 01 21:59:56 T480s kernel:  __x64_sys_ioctl+0x16/0x20
Feb 01 21:59:56 T480s kernel:  do_syscall_64+0x4e/0x150
Feb 01 21:59:56 T480s kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 01 21:59:56 T480s kernel: RIP: 0033:0x7f69587ef25b

Hi @Rick,
I got a crash too... :sob:

févr. 02 16:29:36 mat250-laptop kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
févr. 02 16:29:36 mat250-laptop kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
févr. 02 16:29:36 mat250-laptop kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.
févr. 02 16:29:36 mat250-laptop kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.
févr. 02 16:29:36 mat250-laptop kernel: GPU crash dump saved to /sys/class/drm/card0/error
févr. 02 16:29:36 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
févr. 02 16:29:36 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
févr. 02 16:29:36 mat250-laptop kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0
févr. 02 16:29:36 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
févr. 02 16:29:36 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
févr. 02 16:29:42 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

Back to 5.3...

I'm sorry @moson and @mat250 for your problems.

I think I was lucky, because it's been a few days now and no freezing... I'm starting to get hopeful ...

Luckily, I didn't have (yet?) any problem with kernel 5.5.

Forum kindly sponsored by