Created attachment 21226 [details]
Got this during random usage, I think I was trying to open a feed in Firefox's Feed Sidebar extension. Nothing relevant in kernel log.
I'm terribly sorry if this was already fixed or isn't relevant anymore, as I was running http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=768f317cf0da4cd6682af2e71e71c3e130e05182 .
Is there something I could do to get better backtraces from the server? Would compiling it with debugging info help?
You could refer to http://intellinuxgraphics.org/how_to_report_bug.html:
-- Provide gdb backtrace. See the guide for how to use gdb for X server crash
Are you able to stably reproduce this? Do you have a driver version with which it works fine?
You need to upgrade to latest git and test again, kernel, drm, xf86-video-intel, etc.
I've put ModeDebug in my xorg.conf. Unfortunately, I don't think I can get a gdb backtrace most of the time, because the X server is frozen and I can't switch to a text VT. I can try to have ssh running more of the time, so that I can remote into my laptop, but that's the only situation in which I could do it.
No, I don't currently have a reliable way of reproducing this, but I thought it'd be good to have a bug to track the problem nonetheless.
I'll try to only report bugs against latest git versions in the future, but since there's no clear evidence that this has been fixed, I don't think it should be closed.
Hit this again. I'll recompile with debugging info and start up sshd so I can get a backtrace next time.
Created attachment 21245 [details]
Another X log (with ModeDebug)
Created attachment 21261 [details]
Yet another X log
And again... *sigh* I'll get a real backtrace on this at some point, I swear.
I don't know if this means anything, but I seem to be getting this a lot while using Openoffice Writer.
any update? I have no idea what the problem might be with current info.
It could be that this was caused by trying to use intelfb along with everything else. I'll have to do some more testing.
Oh, and I was able to log in remotely via ssh at one point when I hit this problem, but gdb was being retarded so I couldn't get a backtrace. Sorry. :(
Is this still there with recent updates? 22.214.171.124 has been released and for testing.
ping? Does this happen with 2.6.1?
Ari, I assume you don't see this issue now, so close, feel free to open if you still can see it and provide more info.