ever since the last couple of versions of the intel driver X crashes on me. Sometimes this happens several times a day, some times not for days. Don't appear to be doing the same. It can happen with little or no apps running, but mostly I have a lot of stuff running. It happens with 2 monitors, or just 1.
Original bug report is here:
Still need to enable the ModeDebug. Will report back once I have useful output from that.
It concerns my laptop, a HP/Compaq n6320.
More details follow.
Created attachment 18439 [details]
Created attachment 18440 [details]
Created attachment 18441 [details]
Created attachment 18442 [details]
emerge --info (Gentoo linux)
Created attachment 18443 [details]
Sorry about not responding this long. Some how ever since I enabled the
ModeDebug (and this is all I changed to X) it doesn't crash anymore (well not
yet anyways). Kind of strange, it never ran this long without crashing w/o the
Do have 2 other problems, don't know if they are related. They seem opposites
of each other too.
If in X i switch to console with Ctrl+Alt+F1 and then switch back, I usually
don't get any screen anymore (it remains black). Can switch back to console
If the laptop suspends to memory and comes out of it, X will show just gray
with pale colored lines. I have to switch to terminal, the terminal will stay
black, and switch back to X. X is usually fine then, but the consoles don't
It finally crashed again. I'll attach the Xorg.0.log.old
Created attachment 18650 [details]
Log after crash with modedebug on.
Sorry I haven't replied to this one until now...
There are a few other, similar 945GM reports open at the moment, but none of them have a reliable set of steps we can use to reproduce the problem. Both the 3D driver and the render acceleration code make heavy use of the GPU via the ring, so disabling one or both of those might make the problem go away, can you give that a try?
Marking this one as a dup of 14263. If we ever get info indicating that they're separate we can file another bug... Last comment still stands though, we need to isolate this and find a way of reproducing it.
*** This bug has been marked as a duplicate of bug 14263 ***