Comment # 2
on bug 88558
from Hannu
(In reply to Michel Dänzer from comment #1) > Did this happen when you were doing anything in particular? I wasn't using the computer myself and didn't pay attention to it, probably it crashed while playing in steam or watching flash video. I'll see if it can be reproduced with the same video testing as in bug 85647. Those VM_CONTEXT1_PROTECTION_FAULT_ADDR messages start at 16:41 and then at 17:17 it says "ring 3 stalled" and at that point screen went black, SSH into the box worked and I could get the journalctl report. Jan 18 16:41:35 kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x04124802 Jan 18 16:41:35 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00096D20 Jan 18 16:41:35 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048002 Jan 18 16:41:35 kernel: VM fault (0x02, vmid 9) at page 617760, read from TC (72) ---------------------- Jan 18 17:17:19 kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x00b24801 Jan 18 17:17:19 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0FD37C05 Jan 18 17:17:19 kernel: radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x12048001 Jan 18 17:17:19 kernel: VM fault (0x01, vmid 9) at page 265518085, read from TC (72) Jan 18 17:17:29 kernel: radeon 0000:01:00.0: ring 3 stalled for more than 10191msec
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
