Created attachment 14558 [details]
Several times per day my X.Org server locks up. I cannot determine the conditions, but working using Firefox, Thunderbird, kile etc. seems to be sufficient.
After locking up the server tries to restart but finds "existing errors in hardware state". Only reboot helps to get it up again.
945GM using driver intel 2.2.1
DRM kernel modules from git as of today
Logs will be attached as well as my xorg.conf
Created attachment 14559 [details]
Thanks for the reporting this. But it's hard to fix without a steady reproducing way. Could you provide more info like dmesg according to http://www.intellinuxgraphics.org/how_to_report_bug.html? And please attach log without zipped.
Pls don't use tarball, and stick with text/plain mime type for all logs and config files.
Could you help to verify does this happen with default options? Or which option
you're using might cause this problem?
OK, here the logs in plain ascii text. :)
dmesg says exactly nothing at all.
I am sorry that I cannot see an exact way to reproduce the problem. :(
Created attachment 14575 [details]
Log after attempt to restart X server
X server takes 100% CPU after restart attempt
Created attachment 14576 [details]
X log of the lockup
I forgot to mention: The problem also occurs with driver's default options.
It's working on our side. Without a specific reproducing steps, we can do little. I'm giving this tough bug to jbarnes to see if he happens to have some findings.
Hm, backtrace indicates we're coming in through an EXA path (is the backtrace the same whenever you see crashes?); there have been lots of changes to the server in this area, does the problem still occur with older or newer X servers?
The problem does not occur using the distro's X.org server (1.4 from X.Org 7.3).
I can try a newer one next week.
Any news? Can we close this one?
(In reply to comment #10)
> The problem does not occur using the distro's X.org server (1.4 from X.Org
> I can try a newer one next week.
Johannes, what xserver version were you using when you met the problem? Isn't it the xserver from your distro's release?
Using actual X.Org from git master the problem does not occur anymore at the moment. I'll tell you once it happens again. So let's close this one for now.