Bug 110538 - [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
Summary: [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-28 09:14 UTC by baopeng
Modified: 2019-11-19 09:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
gpu-reset-dmesg (59.81 KB, text/plain)
2019-04-28 09:14 UTC, baopeng
no flags Details

Description baopeng 2019-04-28 09:14:22 UTC
Created attachment 144102 [details]
gpu-reset-dmesg

We want to reset the radeon gpu. When we have reset, the following print will appear. And the screen is screened, how can I fix this problem. Thank you。

[  415.343591] radeon 0000:01:00.0: WB enabled
[  415.347801] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8021dcba0c00
[  415.358637] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8021dcba0c04
[  415.369471] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8021dcba0c08
[  415.380304] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8021dcba0c0c
[  415.391138] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8021dcba0c10
[  415.403381] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffff000014e35a18
[  415.515380] radeon 0000:01:00.0: failed VCE resume (-110).
[  415.860855] [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
[  415.870585] [drm:si_resume [radeon]] *ERROR* si startup failed on resume
Comment 1 Martin Peres 2019-11-19 09:35:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/865.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.