Shutdown, reboot or init 0 on a EL5.9 snapshot 3 system does not switch from the desktop / graphical screen to the screen showing the shutdown messages. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install EL5.9 2. reboot Actual results: The xterm windows are closing and the (graphical) desktop screen is froozen Expected results: Showing the shutdown messages
There is no console screen switching at all. Only the graphical screen is usable.
Do you see this in snap2? There's a known regression in the kernel between snap2 and snap3 that could be related. Also, what hardware is this with?
I believe i saw it with all snapshots, but not with the beta release. I am quite sure, that it happened with snap2. The problem appears on all our hardware platforms, which means they all have MGA G200e VGA controller.
Can you attach /var/log/Xorg.0.log{,.old} from after this happens?
Created attachment 640165 [details] Xorg Logfile Old after reboot
Created attachment 640166 [details] Xorg Logfile (current) after reboot
Created attachment 640169 [details] Xorg Logfile after trying to switch to another screen
I suspect this build will fix it: https://people.redhat.com/~ajackson/868353/ Please test, as those fixes are anticipated to be included in RHEL 5.9.
yes, after updating to xorg-x11-server-Xnest-1.1.1-48.100.el5.x86_64.rpm, xorg-x11-server-Xorg-1.1.1-48.100.el5.x86_64.rpm and xorg-x11-server-Xvfb-1.1.1-48.100.el5.x86_64.rpm the problem is solved.
(In reply to comment #9) > yes, after updating to xorg-x11-server-Xnest-1.1.1-48.100.el5.x86_64.rpm, > xorg-x11-server-Xorg-1.1.1-48.100.el5.x86_64.rpm and > xorg-x11-server-Xvfb-1.1.1-48.100.el5.x86_64.rpm the problem is solved. Excellent, thanks.
I was able to reproduce on xorg-x11-server-1.1.1-48.98.el5. Upon installing xorg-x11-server-1.1.1-48.100.el5, I was able to switch consoles and all reboot messages were visible. Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0083.html