| Bug ID | 109790 |
|---|---|
| Summary | [ 11.594966] [drm:r600_ring_test [radeon]] *ERROR* radeon: ri= ng 0 test failed (scratch(0x850C)=3D0xCAFEDEAD) |
| Product | DRI |
| Version | DRI git |
| Hardware | ARM |
| OS | All |
| Status | NEW |
| Severity | critical |
| Priority | medium |
| Component | DRM/Radeon |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | baopeng88_com@163.com |
Created attachment 143482 [d=
etails]
error_dmesg
We enabled the Radeon OLAND series of graphics cards on ARM, very old graph=
ics
cards,
The kernel is a 4.14 kernel and there is a problem with GPU acceleration not
being enabled:
The kernel initialization log is as follows, there are 2 errors, one is rad=
eon
0000:43:00.0: failed VCE resume (-110).
One is [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x850C)=3D0xCAFEDEAD), this error causes the GPU acceleration func=
tion
to be turned off.
Can you ask me what it is, or how to position it next?
thank you.
(In reply to baopeng from comment #0) > Created attachment 143= 482 [details] > error_dmesg >=20 > We enabled the Radeon OLAND series of graphics cards on ARM, very old > graphics cards, > The kernel is a 4.14 kernel and there is a problem with GPU accelerati= on not > being enabled: > The kernel initialization log is as follows, there are 2 errors, one is > radeon 0000:43:00.0: failed VCE resume (-110). This one is harmless. > One is [drm:r600_ring_test [radeon]] *ERROR* rad= eon: ring 0 test failed > (scratch(0x850C)=3D0xCAFEDEAD), this error causes the GPU acceleration > function to be turned off. > Can you ask me what it is, or how to position it next? For this one, make sure you have this patch: https://cgit.freedesktop.org/drm/drm/commit/?id= =3De02f5c1bb2283cfcee68f2f0feddcc06150f13aa and also make sure your ARM platform supports cache coherence as required by the PCI spec.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | WONTFIX |
And also please try an up to date kernel. We certainly won't f= ix any architecture specific problems in 4.14 any more.
*** Bug 109789 has been marked as a du= plicate of this bug. ***