Bug#491205: update

2008-08-07 Thread Arthur Machlas
I tried running with the NoDRI option in xorg.conf, but it still crashed
unexpectedly and unrecoverably. I have never experienced a crash when
not using firefox. Or, to put it differently, this has only ever
happened when firefox is running (both version 2 and 3, oh and by
firefox I mean iceweasel). Also, I don't recall this ever happening
before a suspend / resume cycle. Or, it only ever has happened after
resuming from suspend at least once. 

I'll include crash part of my xorg.log, the video section of xorg.conf
and a list of running processes at the time of the crash. The section of
the log with the crash is different this time. It looks like it crashed
twice and it's much longer. Also, the error message is somewhat
different. I'd guess this has something to do with the NoDRI option?

At this point, I think as a "workaround" I'm going to use a different
browser. Maybe Epiphany or opera. 

~$ aptitude show xorg
Package: xorg
State: installed
Version: 1:7.3+14

~$ aptitude show xserver-xorg
Package: xserver-xorg
State: installed
Version: 1:7.3+14

~$ aptitude show xserver-xorg-video-intel
Package: xserver-xorg-video-intel
State: installed
Version: 2:2.3.2-2

~$ uname -r
2.6.25-2-686


##
## Crash section from xorg.log ##
##
(WW) intel(0): ESR is 0x0010, page table error
(WW) intel(0): PGTBL_ER is 0x0013, host gtt pte, host pte data,
display A pte
(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
(WW) intel(0): PRB0_HEAD (0x58017a8c) and PRB0_TAIL (0x00018488)
indicate ring buffer not flushed
(WW) intel(0): Existing errors found in hardware state.
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 getbl_err: 0x0013
ipeir: 0x iphdr: 0x7d06
LP ring tail: 0x00018490 head: 0x00017a8c len: 0x0001f001 start
0x
eir: 0x esr: 0x0010 emr: 0x
instdone: 0xfa41 instpm: 0x
memmode: 0x010f instps: 0x800f00c4
hwstam: 0x ier: 0x imr: 0x iir: 0x
Ring at virtual 0xa790a000 head 0x17a8c tail 0x18490 count 641
00017a0c: 
00017a10: 
00017a14: 
00017a18: 
00017a1c: 
00017a20: 
00017a24: 
00017a28: 
00017a2c: 
00017a30: 
00017a34: 
00017a38: 
00017a3c: 
00017a40: 
00017a44: 
00017a48: 
00017a4c: 
00017a50: 
00017a54: 
00017a58: 
00017a5c: 
00017a60: 
00017a64: 
00017a68: 
00017a6c: 
00017a70: 
00017a74: 
00017a78: 
00017a7c: 
00017a80: 
00017a84: 
00017a88: 
00017a8c: 
Ring end
space: 128500 wanted 131064

Fatal server error:
lockup

Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 getbl_err: 0x0013
ipeir: 0x iphdr: 0x7d06
LP ring tail: 0x00018498 head: 0x00017a8c len: 0x0001f001 start
0x
eir: 0x esr: 0x0010 emr: 0x
instdone: 0xfa41 instpm: 0x
memmode: 0x010f instps: 0x800f00c4
hwstam: 0x ier: 0x imr: 0x iir: 0x
Ring at virtual 0xa790a000 head 0x17a8c tail 0x18498 count 643
00017a0c: 
00017a10: 
00017a14: 
00017a18: 
00017a1c: 
00017a20: 
00017a24: 
00017a28: 
00017a2c: 
00017a30: 
00017a34: 
00017a38: 
00017a3c: 
00017a40: 
00017a44: 
00017a48: 
00017a4c: 
00017a50: 
00017a54: 
00017a58: 
00017a5c: 
00017a60: 
00017a64: 
00017a68: 
00017a6c: 
00017a70: 
00017a74: 
00017a78: 
00017a7c: 
00017a80: 
00017a84: 
00017a88: 
00017a8c: 
Ring end
space: 128492 wanted 131064

FatalError re-entered, aborting
lockup

##
## Driver section from xorg.conf ##
##
Section "Device"
Identifier  "Intel945GM"
Driver  "intel"
Option  "NoDRI" "true"
EndSection

##
## Running processes (ps aux)
##
USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
root 1  0.1  0.0   2048   728 ?Ss   11:58   0:01 init
[2] 
root 2  0.0  0.0  0 0 ?S<   11:58   0:00
[kthreadd]
root 3  0.0  0.0  0 0 ?S<   11:58   0:00
[migration/0]
root 4  0.0  0.0  0 0 ?S<   11:58   0:00
[ksoftirqd/0]

Bug#491205: Update, new error message?

2008-07-29 Thread Arthur A
Hi, I promise I'm not coming back here at every crash, but only when I think 
I've got something new that might help.


This time when it crashed I saw the following text above the thin multi-coloured 
bar (like scattered pixels of random colours) along the top, it said:


local soft_irq_pending 800

I may be wrong about the underscores and the 800. It went by real quick. There 
was something else written underneath it I didn't catch.


Can I do something useful, like always run 'x' in debugging mode or check other 
logs or use a systrace to somehow find and post more useful errors?


Many thanks,



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]