Marco Nenciarini wrote: > After executing mu-cade (entered today in sid) my X server died, then > X server refuse to start (sometime locking the video hardware) until > next reboot. >
Sorry for the delay, your report seems to have been caught by some filter on the list. Can you reproduce the problem easily? > Error in I830WaitLpRing(), timeout for 2 seconds > pgetbl_ctl: 0x7ff80001 pgetbl_err: 0x800000 > ipeir: 0 iphdr: 0 > LP ring tail: 1ffe8 head: 0 len: 1f001 start 0 > Err ID (eir): 0 Err Status (esr): 11 Err Mask (emr): ffffffdf > instdone: ffe5fafd instdone_1: fffff > instpm: 0 > memmode: 0 instps: 8001e020 > HW Status mask (hwstam): fff8dffe > IRQ enable (ier): 82 imr: fff80000 iir: 20 > acthd: 10000000 dma_fadd_p: 10000100 > 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 1/0 > PS_INVOCATION_COUNT_QW 2a/0 > PS_DEPTH_COUNT_QW 19e01e/0 > WIZ_CTL 0 > TS_CTL 0 TS_DEBUG_DATA aa9bfefe > TD_CTL 0 / 0 > space: 16 wanted 32 > (II) intel(0): [drm] removed 1 reserved context for kernel > (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8dd7000 at 0xb7b43000 > > Fatal server error: > lockup > That's a GPU lockup and it's very hard to debug unfortunately. We have several reports like this, without any idea whether they are actually similar in the beginning. So if you have a reproducible way to make the lockup occur, that would help. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]