Created attachment 363530 [details] Output of rpm -qa --last Description of problem: Following an update to a large number of packages, including xorg-x11-server packages, the system fails to boot into runlevel 5. Here's what I experience when I power up my Thinkpad X301 which has the x86_64 version of F11 installed, with all latest packages applied: I have all volumes other than /boot encrypted, so I am first prompted to enter the passphrase for that. Once that is accepted, I get the normal plymouth graphical boot screen. However once the final "flash" of the Fedora logo in the plymouth session ends, then the display begins to alternate between a graphical screen and a non-graphical console. The graphical screen has a black background with the animated "blue busy swirl" mouse pointer in the middle. The non-graphical console has a single underscore character in the extreme top left of the screen. The rate of alternation between these two states is approximately one cycle per second before finally settling on the non-graphical console after 5 cycles. It does not respond to ctrl+alt+Fx keys to get alternative ttys and doesn't respond to ctrl+alt+del or ctrl+alt+backspace. It does respond to depressing the power button for half a second, upon which I get the plymouth (graphical) shutdown to occur successfully. I am currently running kernel-2.6.30.8-64.fc11, but when I try either of the two previous kernels installed on the system (kernel-2.6.30.5-43.fc11 and kernel-2.6.29.6-217.2.16.fc11) I experience the same problem. Booting into runlevel 3 I can startx successfully. However, when I try to launch OpenOffice Writer, Xorg crashes completely, dropping me back to the console. When I downgrade xorg-x11-server-Xorg from 1.6.4-0.1 to the previous version (1.6.1.901-1), while it doesn't fix the runlevel 5/gdm problem, it does allow me to run OpenOffice.org Writer. Version-Release number of selected component (if applicable): kernel-2.6.30.8-64.fc11 xorg-x11-server-Xorg-1.6.4-0.1.fc11 How reproducible: Every time I try to boot into runlevel 5 I observe the problem. Steps to Reproduce: 1. On a lenovo x301 notebook, yum update. 2. Reboot (into runlevel 5) Actual results: As described above. Expected results: Graphical login screen is displayed. Additional info: I'm not at all certain that this problem is with the package set that I've filed this bug. The yum update that I believe caused the problem was carried out at approximately 0620HRS on Monday the 28th of September (GMT+10), following several weeks of no updates being carried out (I had been on holidays). This sounds strange, but I'm pretty sure that I rebooted following the completion of that update and everything was fine. However, on the subsequent reboot, the problem revealed itself. I'll attach output of rpm -qa --last. I'll also attach an Xorg log from an unsuccessful runlevel 5 boot. I'll look into installing any debug info packages. Let me know what more info is needed. I originally posted this description to RH bugzilla #523256. My workplace is a premium Red Hat support customer. Let me know if you'd like anything filed via the Red Hat support channel.
Created attachment 363531 [details] Xorg log from unsuccessful boot into runlevel 5
Created attachment 363559 [details] All /var/log/Xorg.* files
Created attachment 363560 [details] All contents of /var/log/gdm/
I've tested booting without KMS by applying nomodeset as a boot parameter. The boot process appears different (non-graphical) but it I more or less get the same problem - i.e. it looks like X is struggling to start up before it finally hangs. I've installed some debuginfo packages prior to capturing the recently attached logs libXvMC-debuginfo-1.0.4-6.fc11 Sun 04 Oct 2009 12:10:19 AM EST libXv-debuginfo-1.0.4-2.fc11 Sun 04 Oct 2009 12:10:19 AM EST libXext-debuginfo-1.0.99.1-3.fc11 Sun 04 Oct 2009 12:10:19 AM EST xorg-x11-drv-intel-debuginfo-2.7.0-7.fc11 Sun 04 Oct 2009 12:10:18 AM EST xorg-x11-drv-vesa-debuginfo-2.2.0-3.fc11 Sun 04 Oct 2009 12:03:41 AM EST zlib-debuginfo-1.2.3-22.fc11 Sat 03 Oct 2009 11:59:51 PM EST pixman-debuginfo-0.14.0-2.fc11 Sat 03 Oct 2009 11:59:51 PM EST libXau-debuginfo-1.0.4-5.fc11 Sat 03 Oct 2009 11:59:51 PM EST libselinux-debuginfo-2.0.80-1.fc11 Sat 03 Oct 2009 11:59:51 PM EST libfontenc-debuginfo-1.0.4-7.fc11 Sat 03 Oct 2009 11:59:51 PM EST audit-debuginfo-1.7.13-1.fc11 Sat 03 Oct 2009 11:59:50 PM EST libpciaccess-debuginfo-0.10.5-1.fc11 Sat 03 Oct 2009 11:59:49 PM EST libdrm-debuginfo-2.4.11-2.fc11 Sat 03 Oct 2009 11:59:48 PM EST dbus-debuginfo-1.2.12-2.fc11 Sat 03 Oct 2009 11:59:48 PM EST hal-debuginfo-0.5.12-29.20090226git.fc11 Sat 03 Oct 2009 11:59:47 PM EST libXfont-debuginfo-1.4.0-3.fc11 Sat 03 Oct 2009 11:59:46 PM EST openssl-debuginfo-0.9.8k-5.fc11 Sat 03 Oct 2009 11:59:45 PM EST xorg-x11-server-debuginfo-1.6.4-0.1.fc11 Sat 03 Oct 2009 11:59:39 PM EST libXdmcp-debuginfo-1.0.2-8.fc11 Sat 03 Oct 2009 11:59:35 PM EST More complete Xorg log files have been added, as well as GDM logs. I'll also attach a dmesg log from a failed runlevel 5 boot.
Created attachment 363562 [details] dmesg from failed runlevel 5 boot
These parts of the X log look interesting: (EE) intel(0): max_gtt_map_size: 53981kb. ... (WW) intel(0): [DRI2] Version 1 API (broken front buffer rendering) (II) intel(0): [DRI2] Setup complete (**) intel(0): Kernel mode setting active, disabling FBC. (**) intel(0): Framebuffer compression disabled (**) intel(0): Tiling enabled (==) intel(0): VideoRam: -1 KB (II) intel(0): Attempting memory allocation with tiled buffers. Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e8516] 1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47d82f] 2: /lib64/libc.so.6 [0x3210833370] 3: /usr/lib64/libdrm_intel.so.1(drm_intel_bo_alloc+0x3) [0x7f9f4a881703] 4: /usr/lib64/xorg/modules/drivers//intel_drv.so(i830_allocate_memory+0x22a) [0x7f9f4aabcd1a] 5: /usr/lib64/xorg/modules/drivers//intel_drv.so(i830_allocate_2d_memory+0xac) [0x7f9f4aabdacc] 6: /usr/lib64/xorg/modules/drivers//intel_drv.so [0x7f9f4aab2593] 7: /usr/lib64/xorg/modules/drivers//intel_drv.so [0x7f9f4aab5f78] 8: /usr/bin/Xorg(AddScreen+0x1d4) [0x42c944] 9: /usr/bin/Xorg(InitOutput+0x76f) [0x4677cf] 10: /usr/bin/Xorg(main+0x1fe) [0x42d04e] 11: /lib64/libc.so.6(__libc_start_main+0xfd) [0x321081ea2d] 12: /usr/bin/Xorg [0x42c689] Fatal server error: Caught signal 11. Server aborting
I have carried out a fresh install of Fedora 11 x86_64 then run yum update and the problem is gone. The system was originally installed with Fedora 10, and it was updated to 11 from that, so that might have muddied the waters a bit, otherwise, I'm generally strict about not adding any 3rd party software or making any major modifications to the default installation.
Closing based on comment #7.