I've just ran hard into this bug. The machine exhibiting the problem is a Dell Latitude D505 with an 855GM chip. It may be of interest to note that I've only encountered this once, and that was _after_ installing 2.6.15-26-686 and the corresponding modules, so I hadn't seen it on the 386 flavored kernel. The kernel is not tainted BTW.
More importantly, I *hadn't* put the system into sleep when this happened. It was triggered through MPlayer, trying to get a movie with the XV backend go into fullscreen. The result was a constantly respawning gdm. I did manage to reboot the system gracefully through an SSH login.
Still, I plan on using 6.06 for a long time (I used Warty satisfactorily on this same machine until it was EOL'ed and Breezy came out!), and it would be quite bad if the X system would go down randomly when something uses XV, rendering the for me fantastic 3 year desktop support useless :(.
Anyway, here's the relevant part of the X.org.log file. It's not the original log of the server when it crashed, as it was scribbled over a few times by a continuously respawning GDM.
Error in I830WaitLpRing(), now is -1067443022, start is -1067445023
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 38 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: 82 imr: 9 iir: 220
space: 131008 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8d06000 at 0xb78ba000
I've just ran hard into this bug. The machine exhibiting the problem is a Dell Latitude D505 with an 855GM chip. It may be of interest to note that I've only encountered this once, and that was _after_ installing 2.6.15-26-686 and the corresponding modules, so I hadn't seen it on the 386 flavored kernel. The kernel is not tainted BTW.
More importantly, I *hadn't* put the system into sleep when this happened. It was triggered through MPlayer, trying to get a movie with the XV backend go into fullscreen. The result was a constantly respawning gdm. I did manage to reboot the system gracefully through an SSH login.
Still, I plan on using 6.06 for a long time (I used Warty satisfactorily on this same machine until it was EOL'ed and Breezy came out!), and it would be quite bad if the X system would go down randomly when something uses XV, rendering the for me fantastic 3 year desktop support useless :(.
Anyway, here's the relevant part of the X.org.log file. It's not the original log of the server when it crashed, as it was scribbled over a few times by a continuously respawning GDM.
Error in I830WaitLpRing(), now is -1067443022, start is -1067445023
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 38 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: 82 imr: 9 iir: 220
space: 131008 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8d06000 at 0xb78ba000
Fatal server error:
lockup
Error in I830WaitLpRing(), now is -1067440824, start is -1067442825
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 40 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: 0 imr: ffff iir: 0
space: 131000 wanted 131064
FatalError re-entered, aborting
lockup