Created attachment 403317 [details] failing Xorg.0.log Description of problem: Fedora 13 (pre-beta). Booting using KMS succeeds, plymouth displays the graphical building Fedora logo, then system hangs without starting X. Removing 'rhgb quiet' from kernel command line, system boots without plymouth, and X starts as expected. Fatal server error: xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call appears in Xorg.0.log Version-Release number of selected component (if applicable): xorg-x11-drv-intel -2.10.0-4.fc13.x86_64 xorg-x11-server-Xorg-1.7.99.902-3.20100319.fc13.x86_64 System is a Dell XPS M1330 laptop with Intel graphics. How reproducible: always Steps to Reproduce: 1. boot with 'rhgb quiet' on kernel command line Actual results: no X Expected results: X
Created attachment 403318 [details] working Xorg.0.log when removing 'rhgb quiet' from the kernel command line.
Also seeing this on a Fujitsu LifeBook S6510 with Intel GM965/GL960 graphics controller and kdm with F13 Beta RC3. kernel-2.6.33.1-19.fc13.x86_64 xorg-x11-server-Xorg-1.7.99.902-3.20100319.fc13.x86_64 xorg-x11-drv-intel-2.10.0-4.fc13.x86_64 kdm-4.4.1-2.fc13.x86_64
Created attachment 404735 [details] Failing Xorg.0.log I'm seeing this also. Seems to work more reliably if I hit 'ESC' during plymouth to get boot messages. Running: [tbl@tlondon ~]$ rpm -qa xorg-x11-server\* xorg-x11-drv-intel xorg-x11-server-common-1.7.99.902-3.20100319.fc14.x86_64 xorg-x11-server-utils-7.4-16.fc14.x86_64 xorg-x11-drv-intel-2.10.0-4.fc13.x86_64 xorg-x11-server-Xorg-1.7.99.902-3.20100319.fc14.x86_64 [tbl@tlondon ~]$ uname -a Linux tlondon.innopath.com 2.6.34-0.28.rc3.git3.fc14.x86_64 #1 SMP Mon Apr 5 17:05:31 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux [tbl@tlondon ~]$ I also am seeing this in /var/log/messages: Apr 6 08:26:05 tlondon kernel: [drm:i915_gem_madvise_ioctl] *ERROR* Attempted i915_gem_madvise_ioctl() on a pinned object and Apr 6 08:24:25 tlondon gdm-binary[1663]: GLib-GObject-WARNING: IA__g_object_set_valist: object class `GdmStaticDisplay' has no property named `force-active-vt'
Works for me with gdm, but not kdm.
Also, I'm stuck on the plymouth boot graphic when X crashes like this. I cannot ctrl-alt-Fn to another tty.
Appears that updating to gdm-2.30.0-2.fc14.x86_64 "fixes this for me"..... [changelog for this says: * Tue Apr 06 2010 Ray Strode <rstrode> 2.30.0-2 - Update plymouth patch to work with 0.8.1 ]
Yeah, pretty sure this was a gdm bug. Please reopen if you can reproduce with 2.30.0-2 or later.