xserver-xorg-driver-i810: Error in I830WaitLpRing(), now is -99922196, start is -99924197

originally post can be viewed at:
http://permalink.gmane.org/gmane.linux.ubuntu.user/90238

Above is my report. Further experimenting shows that disabling *all* power management seems to prevent this from happening but obviously disabling acpi entirely is not a viable solution.

After update I also have the same error:
Error in I830WaitLpRing(), now is 600521876, start is 600519875

This happens when I attempt to play certain opengl games. For example, enemy terrirtory and billard-gl always work fine, but ppracer and slune always cause the fatal server error

This issue resolved itself for me at some point. Apologies for forgetting to say so here.

Unless someone else is still experiencing this issue, it should be marked as resolved.

If no one says otherwise I will close my bug.

Thanks for the information! I'll close this bug now, but if anyone can still reproduce the bug on Feisty feel free to reopen.

I reproduced the bug in Feisty Fawn.
Equipemnt is intel i915 on Lenovo X41.
There is no trace of anything in dmesg, only Xorg.0.log and gdm.log.

I am having the same error. Using Intel on Lenovo Thinkpad X60.

Gdm log says:

Error in I830WaitLpRing(), now is 7023360, start is 7021359
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 9b38 head: 938c len: 1f801 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 306 instps: f0000
hwstam: ffff ier: 0 imr: ffff iir: 0
space: 129100 wanted 131064

Fatal server error:
lockup

confirmed this bug. Running xubuntu 7.04 on intel 845GV chipset (onboard graphic card).

Relevant Xorg.log entries (whole file attached):

Error in I830WaitLpRing(), now is 67469, start is 65468
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x49
ipeir: 0 iphdr: 50300003
LP ring tail: a8 head: 144 len: 1f001 start 0
eir: 0 esr: 10 emr: ff7b
instdone: ffc1 instpm: 0
memmode: 0 instps: 424
hwstam: fffe ier: 82 imr: 53c iir: 0
space: 148 wanted 152
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8c8d000 at 0xb7c51000

confirmed this bug. Running xubuntu 7.04 on intel 845GV chipset (onboard graphic card).

Relevant Xorg.log entries (whole file attached):

Error in I830WaitLpRing(), now is 67469, start is 65468
pgetbl_ctl: 0x3ffe0001 pgetbl_err: 0x49
ipeir: 0 iphdr: 50300003
LP ring tail: a8 head: 144 len: 1f001 start 0
eir: 0 esr: 10 emr: ff7b
instdone: ffc1 instpm: 0
memmode: 0 instps: 424
hwstam: fffe ier: 82 imr: 53c iir: 0
space: 148 wanted 152
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8c8d000 at 0xb7c51000

Fatal server error:
lockup

I've got the same Error Message, but it happens in another way.
Only sometimes, when i start my Laptop, the mousepointer gets a foursqared fuzzy white background.
Directly after that the screen gets black and nothing happens anymore. Rebooting doesn't help either.
But, when I start in recovery mode, do "startx", exit X, then reboot, it works.
When I shutdown the computer in suspend-to-disk the problem doesn't appear.
My Laptop is a Fujitsu/Siemens Amillo L 6820 with a 82845G/GL[Brookdale-G]/GE Chipset Video Card.

Look for the Error Message in the Attachment.

Same problem here, HP TC4200 laptop
Kubuntu doe not resume correctly from 'suspend to ram'

After resuming, the login mask is displayed, enlarged, rather that
the suspended session.
Ctrl-Alt-Bksp restarts kdm, so that the login mask has the right resolution. My suspended session is lost however.

 In the kdm.log file, i have noticed the enclosed lines.

 Any ideas?
 What to look for, in the suspend2ram.log file?

 Thank you for your help

 Pol

 -- enc.
 /var/log/kdm.log
 (...)
 Synaptics DeviceOff called
 Error in I830WaitLpRing(), now is 1918364, start is 1916363
 pgetbl_ctl: 0x5ffc0001 pgetbl_err: 0x0
 ipeir: 0 iphdr: 0
 LP ring tail: 8 head: 0 len: 1f001 start 0
 eir: 0 esr: 1 emr: ffff
 instdone: ffc1 instpm: 0
 memmode: 306 instps: 2014c0
 hwstam: ffff ier: 0 imr: ffff iir: 0
 space: 131056 wanted 131064

 Fatal server error:
 lockup

 Error in I830WaitLpRing(), now is 1924451, start is 1919375
 pgetbl_ctl: 0x5ffc0001 pgetbl_err: 0x0
 ipeir: 0 iphdr: 0
 LP ring tail: 10 head: 0 len: 1f001 start 0
 eir: 0 esr: 1 emr: ffff
 instdone: ffc1 instpm: 0

 memmode: 306 instps: 2014c0
 hwstam: ffff ier: 0 imr: ffff iir: 0
 space: 131048 wanted 131064

 FatalError re-entered, aborting
 lockup

(...)

Could you please recheck it with Gutsy Final Live CD? In Gutsy i810 driver is deprecated and intel driver is used instead.

I've got the bug with Gutsy.

Kubuntu was upgraded to Gutsy from Feisty. Latest updated are applied (at 14 Nov 2007).
Hardware: ASUS A3500L laptop (i852 integrated graphics controller).

/etc/X11/xorg.conf:

Section "Device"
        Identifier "Intel Corporation 82852/855GM Integrated Graphics Device"
        Driver "i810"
        BusID "PCI:0:2:0"
EndSection

/var/log/kdm.log:

Error in I830WaitLpRing(), now is 1056628492, start is 1056626491
pgetbl_ctl: 0x1ffe0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 1810000
LP ring tail: 168 head: 0 len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 108 instps: 0
hwstam: ffff ier: a2 imr: 9 iir: 250
space: 130704 wanted 131064

FatalError re-entered, aborting
lockup

(numbers after "now is", "start is", "LP ring tail:", "space:" differs from time to time)

I just tried to open an AVI file from Dolphin with usual double click. For some files crash happens not regularly, but I found the file which causes crash always :( Kaffeine starts playing (I can listen soundtrack) and no video can appear. X server crashes and I see restart attempts (watches cursor). DVDs plays fine. I never saw the bug with Feisty (but I didn't have "good" AVI).

Can change of the driver help? What driver should I write to xorg.conf?

Can't repeat the bug when the laptop is battery powered.
Can't repeat the bug with "intel" driver.

I am closing this bug because it seems to be fixed. Feel free to open it again if the issue still happens with Gutsy Gibbon and the new Intel driver.

> This bug has been reported via reportbug on ubuntu-users

it´s ok with me anyway

Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux Freak 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686

Driver "intel"

IBM T61p laptop

Running blender for 3-5 minutes makes X dead with this error in logs.

Same error on kubuntou gutsy, hp-tc4200 interl x server i915

From kdm.log:
SetClientVersion: 0 9
SetGrabKeysState - disabled

Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x5ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 30 head: 0 len: 0 start 0
eir: 0 esr: 0 emr: ffff
instdone: ffc0 instpm: 0
memmode: 10f instps: 0
hwstam: ffff ier: 0 imr: ffff iir: 0
Ring at virtual 0xa7920000 head 0x0 tail 0x30 count 12
...
Ring end
space: 131016 wanted 131064

Fatal server error:
lockup

I have yet at hardy rc

I have the exact behavior from this post. ( i founded here this bug :)
http://ubuntuforums.org/showthread.php?t=236531

Error in I830WaitLpRing(), now is 1258277, start is 1256276
pgetbl_ctl: 0x3ef80001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: f8 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffdf
instdone: 0 instpm: 10
memmode: 0 instps: 0
hwstam: dffe ier: 82 imr: 0 iir: 70
space: 130816 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf8feb000 at 0xb79c8000
(II) I810(0): [drm] Closed DRM master.

Fatal server error:
lockup

(II) AIGLX: Suspending AIGLX clients for VT switch
Error in I830WaitLpRing(), now is 1260337, start is 1258336
pgetbl_ctl: 0x3ef80001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 100 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffdf
instdone: 0 instpm: 10
memmode: 0 instps: 0
hwstam: dffe ier: 82 imr: 0 iir: 70
space: 130808 wanted 131064

FatalError re-entered, aborting
lockup

Could please everybody who still experiences this problem with current Hardy regenerate their xorg.conf? Just run the command >>sudo dpkg-reconfigure xserver-xorg<< and after a logout the -intel driver should be used.
If it still happens with the new xorg.conf please attach your /var/log/Xorg.0.log.

Also on an X60, both with the Hardy intel driver as well as v2.3.2...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484049
http://bugs.archlinux.org/task/8976
http://groups.google.com.mx/group/lucky.freebsd.x11.digest/browse_thread/thread/397c15b6a9797e95

v2.4.0 seems to have some relevant fixes included:
http://lists.freedesktop.org/archives/xorg-announce/2008-July/000621.html

v2.4.1 is out now, will try that and report back in a few days:
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.4.1.tar.bz2

Errors and Warnings (minus AIGLX "not supported visual" warnings) with 2.3.2:

(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) intel(0): Bad V_BIOS checksum
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
(WW) intel(0): PRB0_HEAD (0xeb41931c) and PRB0_TAIL (0x000001b8) indicate ring buffer not flushed
(WW) intel(0): Existing errors found in hardware state.

Errors and Warnings (minus AIGLX "not supported visual" warnings) with 2.4.1:

(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) intel(0): Bad V_BIOS checksum
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Hardware claims pipe A is on while software believes it is off
(WW) intel(0): Hardware claims plane A is on while software believes it is off
(EE) intel(0): underrun on pipe B!

The disappearance of the PRB0_CTL/HEAD/TAIL warnings is reassuring, but not liking the new pipe A/B warnings/errors so much... I only zapped X though, and didn't do a clean reboot when switching drivers though, so perhaps they'll disappear too.

Display locked up again w/ 4.2.1. Highlights from Xorg.0.log (started after clean boot, not from the crashed instance - see below):

(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) intel(0): Bad V_BIOS checksum
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd0000009
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000203 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) intel(0): Hardware claims pipe A is on while software believes it is off
(WW) intel(0): Hardware claims plane A is on while software believes it is off
(EE) intel(0): underrun on pipe B!

The Xorg.0.log file from the X crash is unavailable since it was overwritten by X restarting in safe mode, and then starting after boot. If it happens again (and it certainly seems like it will) I'll make sure to preserve the log file before rebooting.

I also get these errors in /var/log/messages coinciding with lockups, but I expect they're occurring after the fact due to intel_agp.ko being left in an unuseable state by the crash:

Aug 13 23:46:18 innis01 kernel: [18898.264514] mtrr: no more MTRRs available
Aug 13 23:46:18 innis01 kernel: [18898.264677] mtrr: no more MTRRs available
Aug 13 23:46:41 innis01 kernel: [18904.202589] mtrr: no more MTRRs available
Aug 13 23:46:41 innis01 kernel: [18904.202749] mtrr: no more MTRRs available
Aug 17 14:18:51 innis01 kernel: [ 3226.570505] mtrr: no more MTRRs available
Aug 17 14:18:51 innis01 kernel: [ 3226.570558] mtrr: no more MTRRs available
Aug 17 14:21:54 innis01 kernel: [ 3248.064310] mtrr: no more MTRRs available
Aug 17 14:21:54 innis01 kernel: [ 3248.064363] mtrr: no more MTRRs available
Aug 17 14:22:13 innis01 kernel: [ 3251.217249] mtrr: no more MTRRs available
Aug 17 14:22:13 innis01 kernel: [ 3251.218653] mtrr: no more MTRRs available
Aug 17 15:57:25 innis01 kernel: [ 435.563481] mtrr: no more MTRRs available
Aug 17 15:57:25 innis01 kernel: [ 435.563534] mtrr: no more MTRRs available
Aug 17 15:57:34 innis01 kernel: [ 438.657178] mtrr: no more MTRRs available
Aug 17 15:57:34 innis01 kernel: [ 438.657394] mtrr: no more MTRRs available
Aug 18 18:02:25 innis01 kernel: [ 4559.638813] mtrr: no more MTRRs available
Aug 18 18:02:25 innis01 kernel: [ 4559.639027] mtrr: no more MTRRs available
Aug 18 22:35:45 innis01 kernel: [ 1511.812187] mtrr: no more MTRRs available
Aug 18 22:35:45 innis01 kernel: [ 1511.812362] mtrr: no more MTRRs available
Aug 18 22:36:05 innis01 kernel: [ 1515.154690] mtrr: no more MTRRs available
Aug 18 22:36:05 innis01 kernel: [ 1515.154745] mtrr: no more MTRRs available
Aug 19 02:36:33 innis01 kernel: [ 1445.795427] mtrr: no more MTRRs available
Aug 19 02:36:33 innis01 kernel: [ 1445.795593] mtrr: no more MTRRs available

I have the same video card, and the same problem, as Net-Zwerg wrote. I use Ubuntu 8.04 LTS.

Someone says this problem is fixed, but the problems I have experienced seem fairly similar. I'm running an HP Pavilion 522a with 1 GB RAM and using Intrepid Ibis (beta something). I tried this and that but pretty well nothing worked. In the end I just removed Hibernate from the shut down options. To me the option of doing an orthodox shut down was much more palatable and less harmful to the computer than trying to use Hibernate and then having to do a non-standard shutdown.
I still have problems with the suspend to ram, but they now occur less frequently than before. The symptoms of the suspend to ram are the screen "jitters" or "twitches" after restoring from suspend to RAM. Also the line "(EE) intel(0): underrun on pipe A!" appears in the Xorg.0.log. For those who experience this problem this is about the best advice I can offer: Remove the Nvidia drivers, download pretty well every Intel graphics driver, and don't use Suspend. Along the way I accidentally lost gnome, so I had to install it again. I used the aptitude command as I read this was better than apt-get. I don't know if this had any relevance or not, although I suspect it didn't.
I did have problems under Hardy with the ACPI and the kacpid hogging the processor, so Intrepid is a much better OS. I think the biggest problem is the Pavilion is quite an old computer and I suspect that has a lot to do with the problems I experienced.

These I830WaitLpRing() messages are generic error messages, that typically pop up for a wide variety of different kinds of bugs. I know the messages are extremely confusing and cryptic, but they are *not* the same bug, and each needs to be handled as a separate bug and solved separately.

Something that fixes the issue for one person will not necessarily fix it for others, and the fixes tend to be very, very different from case to case.

As well, the error log output alone is usually insufficient to troubleshoot the bug, so the many people who have added their 'me too' to this bug don't yet have enough info posted to solve their issue. Thus I must ask that each person please file a new bug report. You can do this easily as follows:

 ubuntu-bug xserver-xorg-video-intel

Please do NOT reopen this bug; file a NEW bug.