Bugzilla – Bug 251166
complete keyboard/screen freeze during boot during X i810 startup: I830WaitLpRing error
Last modified: 2007-04-26 21:51:31 UTC
Since an update to openSUSE 10.2 on my Fujitsu Siemens machine I experience frequent boot lockups during X startup with the following errors in /var/log/Xorg.0.log: --------- Error in I830WaitLpRing(), now is 46649, start is 44648 pgetbl_ctl: 0x1ff60001 pgetbl_err: 0x49 ipeir: 0 iphdr: 50300003 LP ring tail: 160 head: 144 len: 1f001 start 0 eir: 0 esr: 10 emr: ff7b instdone: ffc1 instpm: 0 memmode: 0 instps: 24 hwstam: ffff ier: 0 imr: ffff iir: 0 space: 131036 wanted 131064 Fatal server error: lockup Error in I830WaitLpRing(), now is 48657, start is 46656 pgetbl_ctl: 0x1ff60001 pgetbl_err: 0x49 ipeir: 0 iphdr: 50300003 LP ring tail: 168 head: 144 len: 1f001 start 0 eir: 0 esr: 10 emr: ff7b instdone: ffc1 instpm: 0 memmode: 0 instps: 24 hwstam: ffff ier: 0 imr: ffff iir: 0 space: 131028 wanted 131064 FatalError re-entered, aborting lockup --------- I can find a bunch of reports regarding this problem on the net, however, most of them are related to suspend/resume or video playback. I'm doing none of these, it's just happening in about 50% of cases during cold boot when trying to start X for kdm. Adding the following option seems to prevent the problem from happening - however, X is unbearable slow afterwards (reminds me to i486 times...): Section "Device" ... Option "NoAccel" ... EndSection Full configs/logs will be attached in a few seconds...
I think the system is up-to-date, all available online updates should be installed: > rpm -qa | grep xorg | sort xorg-x11-7.2-26 xorg-x11-devel-7.2-19 xorg-x11-driver-input-7.2-19 xorg-x11-driver-video-7.2-33 xorg-x11-fonts-7.2-14 xorg-x11-fonts-core-7.2-14 xorg-x11-fonts-devel-7.2-8 xorg-x11-libfontenc-7.2-12 xorg-x11-libfontenc-devel-7.2-12 xorg-x11-libICE-7.2-13 xorg-x11-libICE-devel-7.2-13 xorg-x11-libs-7.2-19 xorg-x11-libSM-7.2-12 xorg-x11-libSM-devel-7.2-12 xorg-x11-libX11-7.2-13 xorg-x11-libX11-ccache-7.2-12 xorg-x11-libX11-devel-7.2-13 xorg-x11-libXau-7.2-8 xorg-x11-libXau-devel-7.2-8 xorg-x11-libXdmcp-7.2-8 xorg-x11-libXdmcp-devel-7.2-8 xorg-x11-libXext-7.2-12 xorg-x11-libXext-devel-7.2-12 xorg-x11-libXfixes-7.2-13 xorg-x11-libXfixes-devel-7.2-13 xorg-x11-libxkbfile-7.2-12 xorg-x11-libxkbfile-devel-7.2-12 xorg-x11-libXmu-7.2-13 xorg-x11-libXmu-devel-7.2-13 xorg-x11-libXp-7.2-8 xorg-x11-libXp-devel-7.2-8 xorg-x11-libXpm-7.2-12 xorg-x11-libXpm-devel-7.2-12 xorg-x11-libXprintUtil-7.2-8 xorg-x11-libXprintUtil-devel-7.2-8 xorg-x11-libXrender-7.2-12 xorg-x11-libXrender-devel-7.2-12 xorg-x11-libXt-7.2-13 xorg-x11-libXt-devel-7.2-13 xorg-x11-libXv-7.2-8 xorg-x11-libXv-devel-7.2-8 xorg-x11-proto-devel-7.2-10 xorg-x11-server-7.2-30.4 xorg-x11-util-devel-7.2-8 xorg-x11-xtrans-devel-7.2-12 xorg-x11-Xvnc-7.1-33.1
Created attachment 122248 [details] /var/log/Xorg.0.log of a crash
Created attachment 122249 [details] hwinfo output for the machine Key hardware details: Fujitsu Siemens Scenic W600, P4 @ 3.06 GHz, 512 MB RAM Graphics: Intel i845GE
Created attachment 122251 [details] my xorg.conf This is my xorg.conf with manually added "NoAccel" option. When removing (or uncommenting) this option, I do get the described crash. Only adding "DRI" "off" (also suggested on some threads on the net) doesn't help, the only working workaround I found so far is "NoAccel"
We're aware of this problem. For now I propose to try the i810beta driver instead ("sax2 -r -m 0=i810beta"). It might already fix this problem. Since this happens to you quite regularly it could make sense to investigate it - on your machine. Matthias, please reopen if you're interested. *** This bug has been marked as a duplicate of bug 159962 ***
Matthias, see previous comment.
This "Error in I830WaitLpRing()" failure reminds me of a "typical" LaTeX error message: Something is wrong. It's about the least specified error possible, so no wonder you're seeing it in various circumstances in the net. If anything is to be done here at all, we would have to escalate it to Intel (and the bug would need at least L3 status for that).
Ok, sorry for the delay, but I wanted to be sure before telling that the workaround worked... So it currently seems that just choosing "i810beta" did fix the issue for me. At least I saw no problem during a number of reboots in the last days. But should you change your mind and be interested in debugging stuff, I'll be happy to assist...
Just to complete this, I wanted to let you know that I also experienced the problem with the new i810beta driver in the meantime. However, it seems to occur much more seldom. Let's see how this behaves in 10.3...
Yes, even the latest intel driver is still affected by this problem. :-(