Bug 20634

Summary:	i945 Crashing with Error in I830WaitLpRing()
Product:	xorg	Reporter:	Jamie Jackson <myspamb8>
Component:	Driver/intel	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	medium
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Jamie Jackson 2009-03-12 12:54:40 UTC

As of a week or two ago, my laptop started crashing a few times a day. I don't have any reliable sort of trigger, it's happened during all kinds of usage. (I guess that is one thing that's consistent--it's happened *while* I've been using the machine.) The screen starts flashing black and blacker, and the only way to issue any commands is via ssh from another box (which usually is not convenient, so I have to hard reset).

I've dumbed down my xorg.conf, but no luck.

8086:27a6 (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

jamie@mercury:/var/log$ uname -m
i686
jamie@mercury:/var/log$ glxinfo
...
server glx version string: 1.2
...
client glx version string: 1.4

I'll submit more information in a moment. I'm afraid x will crash and I'll lose what I've got so far.

Comment 1 Jamie Jackson 2009-03-12 13:02:51 UTC

jamie@mercury:/var/log$ uname -r
2.6.27-11-generic
jamie@mercury:/var/log$ lsb_release -d
Description:	Ubuntu 8.10

Machine: Dell Latitude D620

xorg.conf: http://jamiejackson.pastebin.com/f7b80fc8c (doesn't have modedebug on, i'll add that now)
xorg.0.log.old: http://jamiejackson.pastebin.com/f63f13e93
dmesg: http://jamiejackson.pastebin.com/f5f36aca8
xrandr --verbose: http://jamiejackson.pastebin.com/f476814dc

Comment 2 Jamie Jackson 2009-03-12 13:08:07 UTC

Found the Mesa Version:
$glxinfo
...
OpenGL version string: 1.4 Mesa 7.2
...

Comment 3 Gordon Jin 2009-03-12 18:48:17 UTC

looks like 17638

*** This bug has been marked as a duplicate of bug 17638 ***

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.