Comment # 5
on bug 85866
from boombatower
Alright, I am unable to get a dmesg log after crashes since my system is completely unresponsive...even to ssh from another machine. I setup a watch -n 10 of dmesg to dump to file so I'll be able to grab it on reboot. I have identified 3 district crash states. All three start the same way, everything freezes except mouse, then: - screen will flash once or twice and drop to black screen - screen will flash once or twice and drop to tty7 (instead of 8) which has boot log with last message saying (starting X) - third state it will do the second one, but allow I can switch to another tty screen as the machine is responsive after that, just x is dead. The Xorg log differs between the first two states (see attachments): "xorg.log from crash" (being state one), and "xorg.log closed and dropped to tty" (being state two). I have seen the machine be stable for 12+ hours and then die while locked and displays off, other times it dies after 3-4 min, and others a couple hours. I cannot find a correlation between what I am doing (or applications open) when it dies (and the example of being entirely away seems to support that). Is there some reasonable instructions for performing a git bisect? I am familiar with all sorts of development, but not a kernel developer. Is it safe to assume this is in the driver and not Xorg?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
