Created attachment 31967 [details]
script used from acpi trigger to capture state during hang
I just had an X.org hang, running 2.6.31 (linux-image-2.6.31-1-686 version 2.6.31-2 from debian unstable) and X.org's intel drivers (2:2.9.1-1, also from debian unstable). i was not using KMS, and the system would not switch to a text-mode console with Ctrl-Alt-F1 :(
this is on an Asus EeePC 900 with the following hardware:
0 dkg@pip:~$ lspci -s 00:02
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
I triggered my acpi script (see attachment) to record the state of the system by pressing the power button, but it looks like it caused the system to hang. I waited for for several minutes, and then i had to press and hold down the power button for 15 seconds to hard-kill the machine.
Interestingly, it recorded everything *except* for the data from /proc/dri -- maybe it hung the system trying to read /proc/dri, as that is the last thing copied out by my script. maybe that's a clue?
I'll attach a tarball of the dump next.
Created attachment 31968 [details]
captured data from recent EeePC 900 X.org hang with intel driver
here is the data captured from the acpi trigger
Created attachment 32148 [details]
dump capture from another hang
I had another hang. Attached is a dump from that hang -- again it appears that trying to copy /proc/dri locked up the script, and the dump did not complete.
Created attachment 32149 [details]
dump from system when not hanging
just for reference, here is the output of my dump script when the system is *not* hung. (i captured this after i rebooted the machine this morning)
I don't have any solid theory as to the bug yet.
But, is there a specific reason you're not using KMS?
I'd be very interested to know if using KMS helps avoid the bug.
And if there's something that KMS doesn't let you do, then that's something
we need to fix. (With more recent drivers, KMS is mandatory.)
i'm now using KMS, and more recent versions of all of these tools in an attempt to resolve this bug (see bug 25765), so i don't have this configuration available for testing any more :(
If the bug is not reproducible under KMS, then there is no way we can fix it...