[Hardy] gdm freezes system randomly at startup (965Q)

Thanks for reporting this bug and attaching necessary files. Please also collect a full backtrace on this issue - see http://wiki.ubuntu.com/X/Backtracing for directions on how to do this.

Is it possible to get a backtrace when the system freezes completely?

I tried to follow the directions on http://wiki.ubuntu.com/X/Backtracing. After booting the system with Driver "i810" in xorg.conf to avoid the system hanging at boot, I ssh'ed in from another computer, stopped gdm (/etc/init.d/gdm stop), changed the driver to "intel" and started "gdb /usr/bin/Xorg". At the gdm prompt, I entered "run -keeptty -dumbSched". After a few lines of output from Xorg, the system froze completely, including the network connection going down, so it was impossible to enter "backtrace full". I have attached the output on screen from editing xorg.conf until the system freeezes. Did I do anything wrong?

Would it be helpful to have the ouptut of "strace /usr/bin/Xorg -f -oOutfile" or simlilarly with ltrace? This seems to hang even when I use the i810 driver, but the system doesn't freeze completely then (I can still ssh in).

I don't know if this is useful information, but I tried to run "/usr/bin/Xorg -probeonly" to see if it would also freeze the system then. The system still froze.

I can confirm that this problem occurs about 50% of the time with the the same (Optiplex 745) system, with all the recent updates applied running:

"Linux isap56 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux"

However, after applying the kernel update to : '2.6.24-17-generic' , the problem is constant - i.e. the system will not display GDM at all. The bootloader runs, the system appears to load devices etc, but when it would normally show the logon prompt, there is simply a black screen.

Even after entering recovery mode and attempting to 'automatically fix xorg.conf', the problem persists. Hence, I am back to using 2.6.24-16, which at least works on every 2nd boot.

Is this duplicate of bug #223870 or not?

Hi Guys,

I'd agree with Jouni that this is a duplicate of bug 223870. The graphics cards are the same and you are experiencing the same issues. I'll go ahead and mark this as a duplicate of bug 223870 as it has more update debugging information. Please feel free to add any additional information to that bug report and continue any future correspondence there. Thanks!