Created attachment 16711 [details] The rest of Xorg.log This is what's in my xorg.log after the crash(I can still move to a different console and work there but I can't start X again). (attaching the rest of xorg.log). I used to get: [drm:i915_wait_irq] *ERROR* EBUSY -- rec: 1019076 emitted: 1019082 But After upgrading to mesalib 7_0_stable head I don't get that in dmesg anylonger. Software: xorg-server 1.4.0.90 mesalib 7_0_stable f2533e787eaeae84c41b85c7ff04d84922f5631d Software that causes me this after variable amounts of running and doing various things: planeshift bzflag Hardware this is running: EeePC 701 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04) 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04) If there's any more info needed let me know... ---- Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x7ffc0001 getbl_err: 0x00000000 ipeir: 0x00000000 iphdr: 0x02000011 LP ring tail: 0x0001fd48 head: 0x0001ec04 len: 0x0001f001 start 0x00000000 eir: 0x0000 esr: 0x0000 emr: 0xffff instdone: 0xfa41 instpm: 0x0000 memmode: 0x00000306 instps: 0x800f00c4 hwstam: 0xeffe ier: 0x0002 imr: 0x0008 iir: 0x10a0 Ring at virtual 0xa7ae6000 head 0x1ec04 tail 0x1fd48 count 1105 0001eb84: 00000000 0001eb88: 54f00006 0001eb8c: 03cc0080 0001eb90: 00400000 0001eb94: 0077001d 0001eb98: 021c6ec0 0001eb9c: 00000000 0001eba0: 00000080 0001eba4: 021c4ec0 0001eba8: 02000011 0001ebac: 00000000 0001ebb0: 02000011 0001ebb4: 00000000 0001ebb8: 02000011 0001ebbc: 00000000 0001ebc0: 02000011 0001ebc4: 00000000 0001ebc8: 02000011 0001ebcc: 00000000 0001ebd0: 02000011 0001ebd4: 00000000 0001ebd8: 02000011 0001ebdc: 00000000 0001ebe0: 54f00006 0001ebe4: 03cc0020 0001ebe8: 00000000 0001ebec: 00010008 0001ebf0: 020ad010 0001ebf4: 00000000 0001ebf8: 00000020 0001ebfc: 020acff0 0001ec00: 02000011 0001ec04: 00000000 Ring end space: 126644 wanted 131064 Fatal server error: lockup Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0x7ffc0001 getbl_err: 0x00000000 ipeir: 0x00000000 iphdr: 0x02000011 LP ring tail: 0x0001fd50 head: 0x0001ec04 len: 0x0001f001 start 0x00000000 eir: 0x0000 esr: 0x0000 emr: 0xffff instdone: 0xfa41 instpm: 0x0000 memmode: 0x00000306 instps: 0x800f00c4 hwstam: 0xffff ier: 0x0000 imr: 0xffff iir: 0x0000 Ring at virtual 0xa7ae6000 head 0x1ec04 tail 0x1fd50 count 1107 0001eb84: cece0000 0001eb88: cece0006 0001eb8c: cece0080 0001eb90: cece0000 0001eb94: cece001d 0001eb98: cece6ec0 0001eb9c: cece0000 0001eba0: cece0080 0001eba4: cece4ec0 0001eba8: cece0011 0001ebac: cece0000 0001ebb0: cece0011 0001ebb4: cece0000 0001ebb8: cece0011 0001ebbc: cece0000 0001ebc0: cece0011 0001ebc4: cece0000 0001ebc8: cece0011 0001ebcc: cece0000 0001ebd0: cece0011 0001ebd4: cece0000 0001ebd8: cece0011 0001ebdc: cece0000 0001ebe0: cece0006 0001ebe4: cece0020 0001ebe8: cece0000 0001ebec: cece0008 0001ebf0: ceced010 0001ebf4: cece0000 0001ebf8: cece0020 0001ebfc: cececff0 0001ec00: cece0011 0001ec04: cece0000 Ring end space: 126636 wanted 131064 FatalError re-entered, aborting lockup
After a few more tests this seems to happen with any terminal app being open anywhere on the desktop(it happens at random times). But if I don't have any apps open I can run for hours(it usually crashes within an hour). I'm running fvwm with nothing else than FvwmPager so there really isn't anything else running.
Andraž, do you still observe this problem with latest intel drivers and mesa?
Hi, Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org. To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default). Sorry about the noise!
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.