Bug 4105

Summary: I830WaitLpRing() lockup on Intel 82915G/GV/910GL
Product: xorg Reporter: Jon Oberheide <jonojono>
Component: Driver/intelAssignee: Alan Hourihane <alanh>
Status: RESOLVED INVALID QA Contact:
Severity: major    
Priority: high    
Version: 6.8.2   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log.optiplex
none
dmesg.optiplex
none
kernel.config.optiplex
none
lspci.optiplex
none
xorg.conf.optiplex none

Description Jon Oberheide 2005-08-15 13:15:19 UTC
I can reproduce this relatively easily on 2 identical Dell Optiplex SX280s,
leading me to believe this is not a hardware problem.  While running our
in-house 3d visualization software, it is usually triggered when a large number
of polygons are attempted to be rendered.  One is running suse 9.3 and the other
gentoo.  All the following information and attachments are from the gentoo box.

xorg: 6.8.2
kernel: 2.6.11
gcc: 3.4.4

Error in I830WaitLpRing(), now is 9129, start is 7128
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 6db3ffff
LP ring tail: b0 head: 0 len: 1f001 start 0
eir: 0 esr: 1 emr: ffff
instdone: ffc1 instpm: 0
memmode: 108 instps: 800f0050
hwstam: fffe ier: 2 imr: 8 iir: a0
space: 130888 wanted 131064
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xf88c6000 at 0xb7d44000
Comment 1 Jon Oberheide 2005-08-15 13:15:49 UTC
Created attachment 2879 [details]
Xorg.0.log.optiplex
Comment 2 Jon Oberheide 2005-08-15 13:16:11 UTC
Created attachment 2880 [details]
dmesg.optiplex
Comment 3 Jon Oberheide 2005-08-15 13:16:25 UTC
Created attachment 2881 [details]
kernel.config.optiplex
Comment 4 Jon Oberheide 2005-08-15 13:16:38 UTC
Created attachment 2882 [details]
lspci.optiplex
Comment 5 Jon Oberheide 2005-08-15 13:16:53 UTC
Created attachment 2883 [details]
xorg.conf.optiplex
Comment 6 Alan Hourihane 2005-08-15 14:08:26 UTC
Jon,

Have you got a sample application that shows the problem ?

We won't be able to replicate it if it's your in-house 3d software.

Comment 7 Jon Oberheide 2005-08-15 15:32:47 UTC
Unfortunately, I can't provide a sample application.  It's a rather simple
opengl display rendering a large number of 3d bars within a cube.
Comment 8 Alan Hourihane 2005-08-16 09:41:22 UTC
Mmm. Without something that we can use to reproduce the problem it's unlikely to
even get a look in.
Comment 9 Kent 2005-09-03 11:17:48 UTC
(In reply to comment #8)
> Mmm. Without something that we can use to reproduce the problem it's unlikely 
to
> even get a look in.

I can reproduce this problem by running xine after getting my laptop from 
standby mode.

Kent
Comment 10 Alan Hourihane 2005-09-03 11:41:23 UTC
xine has no bearing on OpenGL issues, unless you are specifically using an
OpenGL backend in xine. Are you ?
Comment 11 Kent 2005-09-03 12:16:25 UTC
(In reply to comment #10)
> xine has no bearing on OpenGL issues, unless you are specifically using an
> OpenGL backend in xine. Are you ?

I'm not sure. How can I check it?

The thing is that it probably is not related to the OpenGL at all. I've been 
having this lockups for some time. It usually happens when I start playing 
movies with xine and the log says it is I830WaitLpRing() lockup, very similar to 
this bug report. I searched for similar bug reports and found bug report #1353 
(https://bugs.freedesktop.org/show_bug.cgi?id=1353) which was already closed. I 
downloaded a new i810_drv.o from your website and restarted X. First thing I 
noticed is a performance improvement and I didn't have lockups for sime time 
after that. But today I got the same lockup again, sign. 

Is there anything I can do to help you resolve this problem?

Kent.
Comment 12 Alan Hourihane 2005-09-03 14:25:13 UTC
(In reply to comment #11)

You should open a new bug report and post a log file from when the problem
happens with xine.
Comment 13 Alan Hourihane 2005-10-05 03:48:34 UTC
Jon,

If you can build the current source code, you might want to turn on the VERBOSE
option in intel_batchbuffer.h and define INTEL_DEBUG to 0x1fff in
intel_context.h and rebuild the 3D driver and install it.

Run your application and pipe stderr to a file and then upload that file as an
attachment to this bug.
Comment 14 Alan Hourihane 2006-01-05 05:53:16 UTC
Jon,

Can you try xorg 7.0.0 with mesa 6.4.1 and see if the problem still exists ?
Comment 15 Alan Hourihane 2006-01-25 04:15:11 UTC
Jon,

Have you got any time to try Xorg 7.0 & Mesa 6.4.1 ???
Comment 16 Alan Hourihane 2006-01-28 07:50:20 UTC
No response in over four months. Closing. Re-open if it's still a problem with
Xorg 7.0 & Mesa 6.4.1

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.