Comment # 4
on bug 105733
from Allan
If you set amdgpu.dc=1 as a boot parameter and then try openning pavucontrol, the screen hungs with artifacts (mouse cursor keeps moving) and you get this error : ``` [ 125.640254] amdgpu 0000:0e:00.0: GPU fault detected: 147 0x04f00402 [ 125.640259] amdgpu 0000:0e:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001C389E [ 125.640262] amdgpu 0000:0e:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04004002 [ 125.640264] amdgpu 0000:0e:00.0: VM fault (0x02, vmid 2) at page 1849502, read from 'TC1' (0x54433100) (4) [ 125.640641] amdgpu 0000:0e:00.0: GPU fault detected: 147 0x05004802 [ 125.640643] amdgpu 0000:0e:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001C38A0 [ 125.640644] amdgpu 0000:0e:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x04048002 [ 125.640646] amdgpu 0000:0e:00.0: VM fault (0x02, vmid 2) at page 1849504, read from 'TC4' (0x54433400) (72) ``` I'm using kernel 4.15. Then when you request a poweroff from ssh the call trace appears again and hungs the system, then you have to do a hard reset.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
