After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782929 - gnome-shell crashes when opening laptop lid
gnome-shell crashes when opening laptop lid
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-05-21 19:28 UTC by d.vicesss
Modified: 2017-05-22 16:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Error message of crash (2.59 MB, image/jpeg)
2017-05-21 19:28 UTC, d.vicesss
Details

Description d.vicesss 2017-05-21 19:28:39 UTC
Created attachment 352314 [details]
Error message of crash

Sometimes when I open my laptop I am greeted with the screen as shown in the attachment. This does not happen every time.

Sometimes it stays on that screen and I can't do anything. Other times I can see a blacks screen with text, similar to the picture, flash and it shows the login screen. When I click on my user, enter my password and press enter I am greeted with the login screen again. Because it only flashes by, I am unsure if it's the same output.

Also sometimes when I login the mouse is very slow/laggy. I'm not sure if it's related, but I thought I'd mention it anyway. No black screen with text flashes before the login screen in this case though.

I typed out some parts of the error message in case it was useful: https://izumi.tv/f/gshell.txt

If any other information is require, let me know what and how I can find it.
Comment 1 Rui Matos 2017-05-22 12:45:33 UTC
do you more details about this? anything in your system logs (e.g. journalctl) ? Did it start happening only after some update? Can you try with gnome 3.24 ?
Comment 2 d.vicesss 2017-05-22 15:48:09 UTC
It happened again and this is the journalctl since I opened my laptop: https://izumi.tv/f/crashstuff.txt

I can't remember any specific update, but it has only started recently. It just started one day about a week or so ago, but I can't be any more specific than that because it doesn't happen every time.

I'm on stable so I can't really try it with 3.24 I don't think. I have to use this for work so I don't think it's wise to update gnome.
Comment 3 Rui Matos 2017-05-22 16:13:42 UTC
...
May 22 17:38:01 izumi kernel: radeon 0000:01:00.0: Syncing to a disabled ring!
May 22 17:38:01 izumi kernel: radeon 0000:01:00.0: failed to sync rings (-22)
May 22 17:38:01 izumi kernel: [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-22)
May 22 17:38:01 izumi kernel: ------------[ cut here ]------------
May 22 17:38:01 izumi kernel: WARNING: CPU: 2 PID: 1814 at drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xf6/0x100 [radeon]
...

May 22 17:38:01 izumi org.gnome.Shell.desktop[1418]: radeon: Failed to allocate virtual address for buffer:
May 22 17:38:01 izumi org.gnome.Shell.desktop[1418]: radeon:    size      : 4096 bytes
May 22 17:38:01 izumi org.gnome.Shell.desktop[1418]: radeon:    alignment : 4096 bytes
May 22 17:38:01 izumi org.gnome.Shell.desktop[1418]: radeon:    domains   : 4
May 22 17:38:01 izumi org.gnome.Shell.desktop[1418]: radeon:    va        : 0x000000003477a000
...

This is a driver bug. Try with an older or more recent kernel and file a bug for the radeon driver.
Comment 4 d.vicesss 2017-05-22 16:44:00 UTC
Thanks for the help. I'll file a bug report with radeon.