| Bug ID | 97248 |
|---|---|
| Summary | [regression] [amdgpu] New regression in 4.8-rc1 |
| Product | DRI |
| Version | DRI git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | mike@fireburn.co.uk |
Created attachment 125605 [details]
dmesg
I'm seeing a new regression since 4.8-rc1 on Linus's tree, drm-next, agd5f's
4.9-next-wip since 4.8-rc1 was merged. I'm about to start bisecting
[ 12.644973] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.720886] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.733891] amdgpu 0000:01:00.0: Refused to change power state, currently in
D3
[ 12.958093] amdgpu 0000:01:00.0: Wait for MC idle timedout !
[ 13.071062] amdgpu 0000:01:00.0: Wait for MC idle timedout !
[ 13.081607] [ powerplay ] Invalid VramInfo table.Failed to initialize MC reg
table!
[ 13.770954] [drm:gfx_v8_0_ring_test_ring] *ERROR* amdgpu: ring 0 test failed
(scratch(0xC040)=0xFFFFFFFF)
[ 13.772803] [drm:amdgpu_resume] *ERROR* resume of IP block <gfx_v8_0> failed
-22
[ 13.774713] [drm:amdgpu_resume_kms] *ERROR* amdgpu_resume failed (-22).
[ 13.776643] amdgpu 0000:01:00.0: couldn't schedule ib
[ 13.778602] [drm:amdgpu_job_run] *ERROR* Error scheduling IBs (-22)
[ 13.805924] amdgpu 0000:01:00.0: couldn't schedule ib
[ 13.805928] [drm:amdgpu_job_run] *ERROR* Error scheduling IBs (-22)
[ 18.934066] [drm:amdgpu_suspend] *ERROR* suspend of IP block <vce_v3_0>
failed -110
[ 18.943133] [drm:amdgpu_suspend] *ERROR* set_clockgating_state(ungate) of IP
block <uvd_v5_0> failed -16
These are probably the most relevant messages
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
