Some screensavers (especially "StonerView") lockup xorg server with the following message: Error in I830WaitLpRing(), now is -1948563193, start is -1948565194 pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 0 LP ring tail: 1e260 head: 1e1b0 len: 1f001 start 0 eir: 0 esr: 1 emr: ffdf instdone: 0 instpm: 0 memmode: 0 instps: 0 hwstam: cffe ier: 82 imr: 0 iir: 1040 space: 130888 wanted 131064 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x2efff000 at 0x2b9de63fe000 Fatal server error: lockup (II) AIGLX: Suspending AIGLX clients for VT switch Error in I830WaitLpRing(), now is -1948561191, start is -1948563192 pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 0 LP ring tail: 1e268 head: 1e1b0 len: 1f001 start 0 eir: 0 esr: 1 emr: ffdf instdone: 0 instpm: 0 memmode: 0 instps: 0 hwstam: cffe ier: 82 imr: 0 iir: 1040 space: 130880 wanted 131064 FatalError re-entered, aborting lockup Not only xorg crashes, but also it locks periferials (mouse, keyboard), so the only one thing I can do is log in using ssh and reboot system (xorg refuses to start again). This bug is hard to reproduce. When I run this screensaver manualy I can't reproduce it, the bug also doesn't reveal in 'preview mode' in screensaver preferences. Steps to reproduce: 1. Enable "StonerView" screensaver. 2. Leave the computer and wait until xorg crashes. Versions used: x11-misc/xscreensaver-5.02 x11-base/xorg-x11-7.2 x11-base/xorg-server-1.3.0.0
Created attachment 119275 [details] Xorg log
I haven't noticed this behavior on any particular screensaver, nor have I seen it actually crash X, but quite frequently with xscreensaver or xlockmore, after I unlock the screen, my cpu will be stuck at about 50%, with X taking up 99-100% of the cpu, and the system will be extremely sluggish. I wonder if this is a similar bug.
Which video driver and version are both of you using?
[ebuild R ] x11-drivers/ati-drivers-8.37.6-r1 USE="acpi -qt3" 0 kB
[ebuild R ] x11-drivers/xf86-video-i810-2.0.0 [ebuild R ] x11-base/x11-drm-20070314
I get the same problem as the original poster. If I leave the laptop unattended, I sometimes find it in a crashed state, with the screensaver on top. The mouse and keyboard do not work. I am able to shut down the machine if I press the power button, though. x11-drivers/xf86-video-i810-2.1.0 x11-misc/xscreensaver-5.02-r1
Try with xf86-video-i810 v1.7.4, I bet it is not affected
(In reply to comment #7) > Try with xf86-video-i810 v1.7.4, I bet it is not affected > I've been testing v1.7.4 for almost a week and I can't reproduce this issue, so You might be right.
xscreensaver locked xorg also with xf86-video-i810 v1.7.4. However, it happended for the first time after 2 weeks, while with v2 it was much more often. Error in I830WaitLpRing(), now is 97742320, start is 97740319 pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 0 LP ring tail: 1bea8 head: 1bce0 len: 1f001 start 0 eir: 0 esr: 1 emr: ffdf instdone: 0 instpm: 0 memmode: 0 instps: 0 hwstam: dffe ier: 82 imr: 0 iir: 70 space: 130608 wanted 131064 (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0x1efff000 at 0x2abe53a5f000 (II) I810(0): [drm] Closed DRM master. Fatal server error: lockup (II) Mouse0-usb-0000:00:1d.1-1/input0: Off (II) UnloadModule: "evdev" (II) AIGLX: Suspending AIGLX clients for VT switch Error in I830WaitLpRing(), now is 97744533, start is 97742532 pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 0 LP ring tail: 1beb0 head: 1bce0 len: 1f001 start 0 eir: 0 esr: 1 emr: ffdf instdone: 0 instpm: 0 memmode: 0 instps: 0 hwstam: dffe ier: 82 imr: 0 iir: 70 space: 130600 wanted 131064 FatalError re-entered, aborting lockup
Hum, I've been letting this one slip through. So ping :) Could any of you give me an update on the bug here? Does it work with an stable intel package? Thanks
Sorry, but I can't tell because of bug 194186.
I've been testing xscreensaver for some time, but I can't reproduce it with intel driver 2.2.1 (I also have much more RAM, this may be connected...). I'll reopen it if I encounter lockups.
Alright, thanks for the follow up.
