When enabling the option pagefile of xorg.conf,runing the YUV test, no video window shows and outputs the following infomations: Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 2000000 LP ring tail: 300 head: 2fc len: 1f001 start 0 Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffffffdf instdone: 3f65fafd instdone_1: fffcd instpm: 10 memmode: 0 instps: 8001e035 HW Status mask (hwstam): fffecffe IRQ enable (ier): 2 imr: fffe0000 iir: c0 acthd: 2fc dma_fadd_p: 300 ecoskpd: 307 excc: 0 cache_mode: 6800/180 mi_arb_state: 44 IA_VERTICES_COUNT_QW 3/0 IA_PRIMITIVES_COUNT_QW 1/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 a64a00/0 WIZ_CTL 0 TS_CTL 0 TS_DEBUG_DATA 66effe58 TD_CTL 0 / 0 space: 131060 wanted 131064 Fatal server error: lockup Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 2000000 LP ring tail: 308 head: 2fc len: 1f001 start 0 Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffffffdf instdone: 3f65fafd instdone_1: fffdd instpm: 10 memmode: 0 instps: 8001e035 HW Status mask (hwstam): fffecffe IRQ enable (ier): 2 imr: fffe0000 iir: c0 acthd: 2fc dma_fadd_p: 308 ecoskpd: 307 excc: 0 cache_mode: 6800/180 mi_arb_state: 44 IA_VERTICES_COUNT_QW 3/0 IA_PRIMITIVES_COUNT_QW 1/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 a64a00/0 WIZ_CTL 0 TS_CTL 0 TS_DEBUG_DATA 66effe58 TD_CTL 0 / 0 space: 131052 wanted 131064 FatalError re-entered, aborting lockup X connection to :0.0 broken (explicit kill or server shutdown). +++++++++run I420+++++++++ Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /pipeline0/xvimagesink0: Could not write to resource. Additional debug info: xvimagesink.c(1284): gst_xvimagesink_xcontext_get (): /pipeline0/xvimagesink0: Could not open display Setting pipeline to NULL ... FREEING pipeline ... +++++++++run YV12+++++++++ Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /pipeline0/xvimagesink0: Could not write to resource. Additional debug info: xvimagesink.c(1284): gst_xvimagesink_xcontext_get (): /pipeline0/xvimagesink0: Could not open display Setting pipeline to NULL ... FREEING pipeline ... +++++++++run YUY2+++++++++ Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. ERROR: from element /pipeline0/xvimagesink0: Could not write to resource. Additional debug info: xvimagesink.c(1284): gst_xvimagesink_xcontext_get (): /pipeline0/xvimagesink0: Could not open display Setting pipeline to NULL ... FREEING pipeline ... [1]+ Aborted (core dumped) X
Created attachment 10214 [details] xorg.conf
Created attachment 10215 [details] Xorg.0.log
Ondrej Certik reported in Debian bug[1] that he sees the same "Error in I830WaitLpRing(), timeout for 2 seconds" on i965 *without PageFlip* enabled (I guess the submitter wrote PageFile instead of PageFlip in comment #1). The problem occurs with both Intel drivers 2.0 and 2.1. He doesn't know how to reproduce, and it doesn't seem Xv/PageFlip related as stated in the title here. Brice [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432110
Brice, I can't find xorg conf and log on that debian bug track, good to know what 2d accel was used. And what's the application user was running that might be point of problem, as i965 mesa driver is known still broken with some 3d apps.
The log and config from a regular session (without lockup) is included in: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=19;filename=xserver.log;att=1;bug=432110 I asked him to provide details about the application.
The submitter says he was writing an email in gmail in firefox (iceweasel actually). And in the middle of the sentence it fell down. He was using kde. I don't know if he had some other application in the background. I told him to note what is running when the crash will occur again.
He's using xaa and dri enabled, which seems not pageflip related. Brice, I think you may reference other bugs or open another new one. Thanks.
The updated intel.man says pageflip is unstable so not recommending to use at this point. *** This bug has been marked as a duplicate of bug 11182 ***
Hi, i'm running Debian testing, and had very similar problem: ... Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x3ffc0001 getbl_err: 0x00000000 ipeir: 0x00000000 iphdr: 0x54f00006 LP ring tail: 0x0001cb50 head: 0x0001cb6c len: 0x0001f001 start 0x00000000 eir: 0x0000 esr: 0x0000 emr: 0xffff instdone: 0xfa41 instpm: 0x0000 memmode: 0x00000108 instps: 0x800f04d1 hwstam: 0xfffe ier: 0x0002 imr: 0x0008 iir: 0x00d0 Ring at virtual 0xa7950000 head 0x1cb6c tail 0x1cb50 count 32761 0001caec: 02000000 0001caf0: 54f00006 0001caf4: 03cc2000 0001caf8: 002c0244 0001cafc: 00300248 0001cb00: 01000000 0001cb04: 00000000 0001cb08: 00000010 0001cb0c: 02000000 0001cb10: 54f00006 0001cb14: 03cc2000 0001cb18: 002c0248 0001cb1c: 0030024c 0001cb20: 01000000 0001cb24: 00000000 0001cb28: 00000010 0001cb2c: 02000000 0001cb30: 54f00006 0001cb34: 03cc2000 0001cb38: 002c024c 0001cb3c: 00300250 0001cb40: 01000000 0001cb44: 00000000 0001cb48: 00000010 0001cb4c: 02000000 0001cb50: 00ff0000 0001cb54: 00ff0001 0001cb58: 00ffcf90 0001cb5c: 00ff0000 0001cb60: 00ff0010 0001cb64: 00ff6ec0 0001cb68: 00ff0006 0001cb6c: 00ff0040 Ring end space: 20 wanted 32 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xf8f4c000 at 0xb7a81000 (II) intel(0): [drm] Closed DRM master. Fatal server error: lockup I was browsing WWW using Opera while this bug trigered, and crashed xserver (restart of whole system was needed, because driver have problem detecting gfx card). Mayby some flash using xv? Full log: http://smp.if.uj.edu.pl/~baryluk/Xorg.log.intel-crash
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.