Re: Laptop GUI crash - was - Re: what laptop to buy - suggestion for Debian project developers
On Thu, 18 Feb 2010 23:02:27 +0800 (WST)
Bret Busby <bret@busby.net> wrote:
...
> /var/log/Xorg.0.log.old (shows last crash, which occurred tonight, after
> (I believe) less than a day of running) is below.
When looking at Xorg crash logs, one looks for lines beginning with
'(EE)' [(II) - information, (WW) - warning, (EE) - error], or the word
'error' (case insensitive).
Looking at your log, I see no evidence that the crash is related to the
browsers, although I'm certainly no expert.
> This is from the HP/Compaq NX5000 "laptop".
>
> I was running Iceweasel
> ("Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.16) Gecko/2009121610
> Iceweasel/3.0.6 (Debian-3.0.6-3)")
> and Iceape
> ("Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US;
> rv:1.8.0.14eol) Gecko/20070505 Iceape/1.0.9
> (Debian-1.0.13~pre080614i-0etch1)")
> ,
> which appear to be the latest versions for Debian 5, at the time of the
> crash.
>
> I apologise in advance, if what is below, is too much, but to include
> what is below, is all that I know (?) to do, at this stage.
...
> X.Org X Server 1.4.2
> Release Date: 11 June 2008
> X Protocol Version 11, Revision 0
> Build Operating System: Linux Debian (xorg-server 2:1.4.2-10.lenny2)
> Current Operating System: Linux bretlaptop-debian5 2.6.26-1-686 #1 SMP
> Fri Mar 13 18:08:45 UTC 2009 i686
> Build Date: 08 June 2009 09:12:57AM
...
> (--) Configured Mouse: PnP-detected protocol: "ExplorerPS/2"
> (II) Configured Mouse: ps2EnableDataReporting: succeeded
Everything until here seems pretty normal.
> Error in I830WaitLpRing(), timeout for 2 seconds
> pgetbl_ctl: 0x7ffe0001 getbl_err: 0x00000000
> ipeir: 0x00000000 iphdr: 0x54f00006
> LP ring tail: 0x00018980 head: 0x0001898c len: 0x0001f001 start
> 0x00000000
> eir: 0x0000 esr: 0x0000 emr: 0xffff
> instdone: 0xff41 instpm: 0x0000
> memmode: 0x00000108 instps: 0x00000431
> hwstam: 0xffff ier: 0x0002 imr: 0x0009 iir: 0x0020
> Ring at virtual 0xaf924000 head 0x1898c tail 0x18980 count 32765
> 0001890c: 003400e8
> 00018910: 00800000
> 00018914: 00000000
> 00018918: 00000010
> 0001891c: 00c00000
> 00018920: 54f00006
> 00018924: 03cc1000
> 00018928: 003000e8
> 0001892c: 003400ec
> 00018930: 00800000
> 00018934: 00000000
> 00018938: 00000010
> 0001893c: 00c00000
> 00018940: 54f00006
> 00018944: 03cc1000
> 00018948: 003000ec
> 0001894c: 003400f0
> 00018950: 00800000
> 00018954: 00000000
> 00018958: 00000010
> 0001895c: 00c00000
> 00018960: 54f00006
> 00018964: 03cc1000
> 00018968: 003000f0
> 0001896c: 003400f4
> 00018970: 00800000
> 00018974: 00000000
> 00018978: 00000010
> 0001897c: 00c00000
> 00018980: ffff0050
> 00018984: ffff95d0
> 00018988: ffff0006
> 0001898c: ffff0370
> Ring end
> space: 4 wanted 32
> (II) intel(0): [drm] removed 1 reserved context for kernel
> (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8b55000 at
> 0xb7af3000
> (II) intel(0): [drm] Closed DRM master.
>
> Fatal server error:
> lockup
>
> (II) AIGLX: Suspending AIGLX clients for VT switch
> (II) intel(0): xf86UnbindGARTMemory: unbind key 0
> (II) intel(0): xf86UnbindGARTMemory: unbind key 1
> (II) intel(0): xf86UnbindGARTMemory: unbind key 2
> (II) intel(0): xf86UnbindGARTMemory: unbind key 3
> (II) intel(0): xf86UnbindGARTMemory: unbind key 4
> (II) intel(0): xf86UnbindGARTMemory: unbind key 5
> (II) intel(0): xf86UnbindGARTMemory: unbind key 6
> (II) intel(0): xf86UnbindGARTMemory: unbind key 7
> (II) intel(0): xf86UnbindGARTMemory: unbind key 8
> (II) intel(0): xf86UnbindGARTMemory: unbind key 9
> .........................................
This is your crash. The 'Error in I830WaitLpRing()' business is
apparently a common bug with the Xorg drivers for Intel graphic
chipsets. I've experienced this myself, but not for about a year. My
bug report is here:
http://bugs.freedesktop.org/show_bug.cgi?id=16262
Googling for the error message, and looking around on the above
Bugzilla may help, and you can always file your own bug. I'm pretty
sure that this is a driver bug, but you're running a pretty old X
version. I don't know if the devs are interested in bugs in that
version, but you can try filing a report. They will expect you to help
them by providing various logs and diagnostic results:
http://intellinuxgraphics.org/how_to_report_bug.html
In any event, my very non-expert guess is that this has nothing to do
with the quantity of mainboard RAM or the CPU of your system.
Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
Reply to: