GNOME Bugzilla – Bug 747708
System hangs while switching between TTYs, GDM and GNOME-Session
Last modified: 2015-04-13 08:26:15 UTC
Created attachment 301371 [details] reverse journalctl Hello! Since GNOME 3.16 switching between GDM (TTY1), the active GNOME-Session (TTY2) and the other TTYs (3-6, manged by systemd to run getty) lead to graphic corruptions and a complete hang of the entire system. No INPUT is accepted and even the Power-Button doesn't initiate a controlled shutdown. Steps to reproduce: 1. Login to GNOME 2. Switch from GNOME to TTY 3-6 3. Switch to GNOME on TTY2 4. Switch from GNOME to TTY 3-6 5. Switch to GNOME on TTY2 6. Repeat until graphics get corrupted and finally the system hangs OR (this should be much faster): 1. Login to GNOME 2. Switch to TTY1 (GDM) 3. Switch to TTY 3-6 4. System hangs I've attached my lspci (ThinkPad X220), the reverse output of journalctl, a list of installed packages and the config of my self compiled kernel. As you can see, the graphics driver from intel get blown up, maybe a bug on it's own but it seem at least to be trigged by GNOME/GDM.
Created attachment 301372 [details] reverse journalctl
Created attachment 301373 [details] reversel journalctl
Created attachment 301374 [details] ThinkPad X220 lspci
Created attachment 301375 [details] package list, up-to-date archlinux
Created attachment 301376 [details] .config of self compiled kernel-3.19.3
This is also reported downstream on at Suse: https://bugzilla.opensuse.org/show_bug.cgi?id=925944 Thanks for your work Bye
Looks like a kernel bug to me. The DRM framebuffer is getting erroneously unreffed. It does not matter what userspace is doing -- kernel space can never crash. Please report a bug here to the kernel: https://bugs.freedesktop.org/enter_bug.cgi?product=DRI using component "DRI/Intel".
Thank you, for your fast response. I will report that to the people at Intel tomorrow! Good evening :-)
Hello! This bug is already fixed upstream on the kernel: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=33f62dc361a7cc15bffd28caf89382786868f3d3 https://bugzilla.kernel.org/show_bug.cgi?id=95621 https://bugs.archlinux.org/task/44491 I just booted up the standard kernel of Archlinux, same release "3.19.3" as mine self compiled kernel, and it worked. So I figured out the patch is responsible, because it cares about fbdev stuff. I applied it to my self compiled kernel and it is also fixed. Maybe we should contact Suse/Tumbleweed, so they don't was time on searching.