Red Hat Bugzilla – Bug 242964
X server on i915 (T60) locks on shutdown with "mottled" screen
Last modified: 2018-04-11 06:32:31 EDT
Description of problem: When shutting down the X server (either from system reboot/shutdown, quit button or ctrl-alt-backspace), sometimes the server locks with a mostly blank screen, littered with slightly lighter blocks about the size of a text cursor block. Reboot is required to recover Version-Release number of selected component (if applicable): $ rpm -q xorg-x11-drv-i810 xorg-x11-drv-i810-2.0.0-3.fc7 How reproducible: Random Steps to Reproduce: 1. Run X windows 2. stop the server (shutdown/reboot, quit/logout button, ctrl-alt-bs) 3. Look for blank screen lockup Actual results: random lockup Expected results: return to either console prompt or XDM screen or system shutdown/reboot Additional info:
Saw this today when trying to switch to vt1 with ctl-alt-f1. xorg-x11-drv-i810-2.0.0-4.fc8 kernel-2.6.21-1.3218.fc8 xorg-x11-server-Xorg-1.3.0.0-9.fc8
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 157124 [details] T60 X11 config file X11 config file
Created attachment 157125 [details] current X11 log file
Created attachment 157126 [details] archived X11 log file
Created attachment 157137 [details] X log from start with no xorg.conf This Xorg.0.log is from starting X+GNOME with no /etc/X11/xorg.conf
I am not sure, but it looks like you have problems with SELinux. Could you post here what you get from getenforce command? Could you please try to relabel your hard drive (as an user root touch /.autorelabel and reboot; could take some time, ten, fifteen minutes, before the reboot will finish). What are the results?
# getenforce Enforcing I'll relabel and reboot in a bit (got a kernel build going :))
We are still not done.
Reporter, could you please try to relabel your machine and try to reproduce the bug? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Argh. I completely forgot about this. I haven't had it happen in quite some time. I have relabeled my filesystem twice since reporting this and haven't seen the problem. I had some unrelated SELinux issues this week and disabled it, which is how I'm running now (on up-to-date rawhide). I suppose we should go ahead and close this, since I can't seem to reproduce it.
Thanks for letting us know.