Comment # 129
on bug 81644
from Aaron B
Didn't mention it last night, but in my logs were this in my system log were messages about msc number being wrong, which we've seen before. But I also saw a "Chromium segfault" error which I haven't seen before, but would explain why it crashes. It's probably it's fault for not bailing from a bad return gracefully, but maybe the return isn't NULL when it should be, anything is possible. Also interesting in DMesg: [ 8531.831921] radeon 0000:01:00.0: Packet0 not allowed! Is it broken in all of radeonsi, and not only hawaii? I haven't seen this before. This was 500 seconds before my screen died. Still, anything else I should log from DPM and such to try to find what screws up when?
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
