Comment 8 for bug 124023

Revision history for this message
Anders Norgaard (anders-norgaard) wrote :

Hi Bryce,

How is it fixed? Will there be an update to the driver? (or pymol?). And are you sure this issue is the same as "bug 119977"? the descriptions don't look similar at all.

Thanks
Anders

PS Here is an extract from my log after a pymol induced crash

Fatal server error:
lockup

(II) AIGLX: Suspending AIGLX clients for VT switch
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x7ff80001 pgetbl_err: 0x0
ipeir: 0 iphdr: bf149d99
LP ring tail: a48 head: 0 len: 1f001 start 0
Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffffffdf
instdone: ffe5fafd instdone_1: fffff
instpm: 0
memmode: 0 instps: 8001e022
HW Status mask (hwstam): fff8dffe
IRQ enable (ier): 2 imr: fff80000 iir: 20
acthd: 3e93f10 dma_fadd_p: 3e94000
ecoskpd: 307 excc: 0
cache_mode: 6800/180
mi_arb_state: 44
IA_VERTICES_COUNT_QW 0/0
IA_PRIMITIVES_COUNT_QW 0/0
VS_INVOCATION_COUNT_QW 0/0
GS_INVOCATION_COUNT_QW 0/0
GS_PRIMITIVES_COUNT_QW 0/0
CL_INVOCATION_COUNT_QW 0/0
CL_PRIMITIVES_COUNT_QW 0/0
PS_INVOCATION_COUNT_QW 0/0
PS_DEPTH_COUNT_QW 0/0
WIZ_CTL 0
TS_CTL 0 TS_DEBUG_DATA 223725fe
TD_CTL 0 / 0
space: 128432 wanted 131064

FatalError re-entered, aborting
lockup