Comment 28 for bug 345714

Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, I'm curious about this. This latest info doesn't match up with the backtrace you posted earlier, which seemed to be in XKB rather than drm.

#2 0x080c86f1 in xf86ProcessActionEvent (action=ACTION_SWITCHSCREEN, arg=0xbfff7d40)
#3 0x081c590b in XkbDDXSwitchScreen (dev=0xd4096d0, key=67 'C', act=0x5606)
#4 0x081adfae in _XkbFilterSwitchScreen (xkbi=0xd3cfda8, filter=0xdcf5450, keycode=67,

Could it be possible that you have been experiencing two different crashes? I recently put in a fix for a bad XKB bug that was causing a couple other crashes (which did not seem related to your case, but who knows). Also, we have been tracking a crash in drm_intel_fake_bo_unreference_locked() on another report (bug 348428).

Perhaps the original bug is now resolved, and you are instead seeing bug 348428 now? What do you think?