kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes

[paquin pierre]

The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed.

I'm using
- Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station).
- Portable PC

The bug happen
- When I use my PC with screen pluged directly : some times
- When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently
- When à Use my docking station and watch some full screen video : very frequently

It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 4 10:17:54 2021
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-08 (1183 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[paquin pierre (castrogne)]

Hello,

1. I have 3 crash files in /var/crash but the ubuntu-bug command fail. Each one has a ".upload" and ".uploaded" file so I think they're already uploaded. Shall I empty the folder to have a clean start point for next time the bug appear?

2. Many files in this page. These are the 3 related with the crashs in my /var/crash, but there're many others :
2021-02-04 07:02 (the day when I opened this bug) - https://errors.ubuntu.com/oops/b95f8166-66b4-11eb-84cc-fa163e102db1
2021-01-27 09:01 : https://errors.ubuntu.com/oops/6b87b264-607b-11eb-83c4-fa163e102db1
2021-02-02 09:02 : https://errors.ubuntu.com/oops/46f3c61a-652e-11eb-90f7-fa163ee63de6

May I link the full url of https://errors.ubuntu.com/user/ID or is it unsafe?

[paquin pierre (castrogne)]

By the way, my "journalctl" is full of this, maybe related, maybe not...

févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: Errors:
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: [4886:4886:0205/073611.340319:ERROR:shared_context_state.cc(74)] Skia shader compilation error
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: ------------------------

[Daniel van Vugt (vanvugt)]

Thanks. It sounds like a few different DisplayLink problems.

It appears the display-related crashes are all in Xorg, Xwayland and DisplayLinkManager. The last one doesn't seem to be part of Ubuntu so I'll ignore that here. So the remaining two both come from the 'xorg-server' source package.

Unfortunately I can't tell exactly how Xorg is crashing. Next time it happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also share the contents of the '.uploaded' files. You don't need to share your whoopsie-id (also I can see it on those 'oops' pages).

[paquin pierre (castrogne)]

the uploaded file.

[paquin pierre (castrogne)]

there's no more uploaded file for xorg crash... I'll do what you ask on next crash and reboot.

I found the origin of the gnome-shell entries in journalctl, they came from chrome. I try to not use it today and we'll see if I have no more gnome crash. I have no idea if it's related but it's not, I'll have the crash even if I don't use chrome.

[Daniel van Vugt (vanvugt)]

Since DisplayLinkManager doesn't seem to be part of Ubuntu we will ignore that one.

As for the gnome-shell log entries from Chrome, yes I have seen lots of people have that problem. I don't know why it happens but it's also not relevant to this bug. This bug should really be about the Xorg and kernel crashes.

[paquin pierre (castrogne)]

I just have the gnome crash to login now. I join the result of the command :
journalctl -b-1 > prevboot.txt

Thanks for help

[paquin pierre (castrogne)]

Here is the new entry on Error tracker :
https://errors.ubuntu.com/oops/00b2327a-6785-11eb-9850-fa163e983629

[paquin pierre (castrogne)]

about last Error tracker, the datetime is strange because crash occured 05/02 at about 10:0x

[paquin pierre (castrogne)]

I see that in /var/crash directory :
-rw-r--r-- 1 someone whoopsie 0 févr. 5 08:37 _usr_lib_xorg_Xorg.1000.upload
-rw------- 1 whoopsie whoopsie 37 févr. 5 08:37 _usr_lib_xorg_Xorg.1000.uploaded
drwxrwsrwt 2 root whoopsie 4096 févr. 5 09:59 .
-rw-r----- 1 someone whoopsie 18861531 févr. 5 09:59 _usr_lib_xorg_Xorg.1000.crash

Yes crash may have occured at 09:59. "uploaded" file is before. I can't use ubuntu-bug on crash file.

[paquin pierre (castrogne)]

Just one more description, for information... My bug is a crash of gnome that redirect me to login screen, not a full reboot. So the shutdown information at the end of the "prevboot.txt" are not related to the bug.

Lines begin to be strange there :
févr. 05 09:59:51 XXXXXXXXXX kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) Backtrace:
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x564aeb43a59c]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f530a47e41f]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f530a2bb18b]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f530a29a859]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) unw_get_proc_name failed: no unwind info found [-10]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7f530840baec]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7f530915dc9c]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7f530846074d]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 7: /usr/lib/xorg/Xorg (present_register_complete_notify+0x673) [0x564aeb3b6cf3]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 8: /usr/lib/xorg/Xorg (present_register_complete_notify+0x1fd9) [0x564aeb3b9ee9]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 9: /usr/lib/xorg/Xorg (present_register_complete_notify+0x26bf) [0x564aeb3baa3f]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 10: /usr/lib/xorg/Xorg (present_register_complete_notify+0x1361) [0x564aeb3b8581]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x564aeb2d8f34]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x564aeb2dcfc4]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f530a29c0b3]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x564aeb2c6a2e]
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: Fatal server error:
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE) Caught signal 6 (Aborted). Server aborting
févr. 05 09:59:51 XXXXXXXXXX /usr/lib/gdm3/gdm-x-session[2728]: (EE)
févr. 05 09:59:51 XXXXXXXXXX /...

[Daniel van Vugt (vanvugt)]

Thanks. Yes, I think the Xorg crash shown in comment #13 is the important one here. Unfortunately it is "strange" as you say, because debug symbols are not installed.

Next please try installing the debug symbols:

  https://launchpad.net/ubuntu/+archive/primary/+files/xserver-xorg-core-dbgsym_1.20.9-2ubuntu1.2~20.04.1_amd64.ddeb

and then send us another:

  journalctl -b-1 > prevboot.txt

[paquin pierre (castrogne)]

I assume I had to rename "ddeb" to "deb" in extension. I did that and redo the journalctl command line. Here's the file it outputs.

I don't see anything different, but I don't realy know what i'm searching (debug symbols). Hope that help.

[Daniel van Vugt (vanvugt)]

It looks like the information we're missing is in /usr/lib/x86_64-linux-gnu/dri/iris_dri.so so please install:

  https://launchpad.net/ubuntu/+archive/primary/+files/libgl1-mesa-dri-dbgsym_20.2.6-0ubuntu0.20.04.1_amd64.ddeb

and then after the next crash and reboot, send us another:

  journalctl -b-1 > prevboot.txt

Or if you didn't need to reboot then please:

  journalctl -b0 > curboot.txt

Also, you don't need to rename .ddeb files. You can just install them with:

  sudo dpkg -i *.ddeb

[paquin pierre (castrogne)]

Hello,

I had the bug just now. It was a bit different, the screen freeze in a strange way before "gnome reboot", so maybe it's different...

Here are the 2 files, before and after reboot just in case you need both. They may be the same file or nearly.

[paquin pierre (castrogne)]

same file, after reboot.

[paquin pierre (castrogne)]

There's something new in /var/crash, I have a gnome-shell entry, with uploaded file. Here is file

[paquin pierre (castrogne)]

Error tracker entry :
https://errors.ubuntu.com/oops/3d57ee6e-69f3-11eb-8529-fa163e102db1

[paquin pierre (castrogne)]

Another time, another log :).

Thanks for help.

[Daniel van Vugt (vanvugt)]

Thanks for all that.

Confusingly you now seem to be getting hangs in the Intel kernel driver followed by gnome-shell crashes. This seems to be a different bug to what we were looking at before, probably caused by using Wayland instead of Xorg...

févr. 08 10:51:19 PORTABLE-PPAQUIN kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: GNOME Shell crashed with signal 6
févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: == Stack trace for context 0x55e1400292a0 ==

févr. 08 12:58:22 PORTABLE-PPAQUIN kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: GNOME Shell crashed with signal 6
févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: == Stack trace for context 0x5618d81e35d0 ==

Please change back to 'Ubuntu' instead of 'Ubuntu on Wayland', and then follow the steps in comment #16.

[paquin pierre (castrogne)]

Hello,

You're true, I changed to Wayland because it seems to be the next default of ubuntu, and it's recommended to use with Displaylink (even if in the past it had some troubles). Whatever, I'll use Xorg as you ask and I'll send you next crash information.

[Daniel van Vugt (vanvugt)]

We should probably open a new bug about those problems in Wayland sessions. If you wanted to just focus on Wayland then we can close this bug about Xorg crashes. If you like? Or we can keep two bugs open, I don't mind.

[paquin pierre (castrogne)]

I opened my session in Xorg this morgning. I only want one of Wayland or Xorg to work, which one you think we have a better chance? You already see some logs and probably have some idea about Xorg. My suggest is to continue for this day with Xorg, I'll send you logs each time I get the crash (I used to send you only one or two) for you to get as much as information I can.

After that, maybe you'll have a better idea if continue with Xorg is a better solution, or switch to Wayland.

Many thanks for help,

[paquin pierre (castrogne)]

Hello,

I just had the crash. I send you the new curboot file for investigation.

I have a new entry on /var/crash, but no "uploaded" and i can't ubuntu-bug the crash file. There's no entry on "Error reports" webpage. As the crash file is "_usr_lib_xorf_Xorg.1000.crash", i did a "ubuntu-bug xorg". That created this bug :
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915125

If it doesn't help, you can close 1915125 new bug.

[Daniel van Vugt (vanvugt)]

Thanks. That does seem to be the same crash again. But did you install the file requested in comment #16 first?

févr. 09 08:46:11 PORTABLE-PPAQUIN kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE)
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) Backtrace:
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x564bfa29459c]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fea86d4541f]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fea86b8218b]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fea86b61859]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) unw_get_proc_name failed: no unwind info found [-10]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fea84cd2aec]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fea85a24c9c]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fea84d2774d]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 7: /usr/lib/xorg/Xorg (present_register_complete_notify+0x673) [0x564bfa210cf3]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 8: /usr/lib/xorg/Xorg (present_register_complete_notify+0x1fd9) [0x564bfa213ee9]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) unw_get_proc_name failed: no unwind info found [-10]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 9: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fea876a3fe0]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) unw_get_proc_name failed: no unwind info found [-10]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 10: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fea876a50b0]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmHandleEvent+0x9d) [0x7fea8748a91d]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 12: /usr/lib/xorg/Xorg (OsCleanup+0x5c1) [0x564bfa295421]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 13: /usr/lib/xorg/Xorg (WaitForSomething+0x193) [0x564bfa28dc83]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 14: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x564bfa132cf7]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr/lib/gdm3/gdm-x-session[2848]: (EE) 15: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x564bfa136fc4]
févr. 09 08:46:11 PORTABLE-PPAQUIN /usr...

[Daniel van Vugt (vanvugt)]

Some small good news: Both the Xorg crash and the Wayland crash appear to have the same cause. Both are always preceded by:

kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

and then either Xorg or gnome-shell (for Wayland sessions) crashes.

[Daniel van Vugt (vanvugt)]

I wonder if this is related to the fix for bug 1861395.

[Daniel van Vugt (vanvugt)]

I'm now convinced this is probably the same bug as 1907142 so we should track it there.

[paquin pierre (castrogne)]

Hi,

I Have no idea for bu 1861398. Tell me if i can do anything.

Yes, i did #16 install when you asked it. I just did it again, seems I can do it again with no warning. I expected something like "yet installed". How may I check if it's already installed?

[paquin pierre (castrogne)]

Yes it seems to be the same thing.

What can i do next to help?

[Daniel van Vugt (vanvugt)]

You can use 'dpkg -l' to find out what's installed.

As for bug 1907142, I have now subscribed a DisplayLink engineer so let's see what he says.

[paquin pierre (castrogne)]

Ok, seems installed, I'll report on the other bug id next time :

$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for xserver-xorg-core