Bug 107301 - System display will be gone suddenly after amdgpu is loaded and gdm is started
Summary: System display will be gone suddenly after amdgpu is loaded and gdm is started
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-20 07:18 UTC by jian-hong
Modified: 2019-11-19 08:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
System's journal log with 4.18-rc5 (1.26 MB, text/plain)
2018-07-20 07:18 UTC, jian-hong
no flags Details

Description jian-hong 2018-07-20 07:18:44 UTC
Created attachment 140723 [details]
System's journal log with 4.18-rc5

I have a hardware whose MB is Acer Nitro N50-100 (AMD Ryzen: ZD2600BBM68AF_38/34_Y) and graphic card is AMD Radeon RX 580.

I have tried Linux kernel 4.18-rc5 with parameters "amdgpu.dc_log=1 drm.debug=7" on this hardware.  System display will be gone suddenly and not come back after amdgpu is loaded and gdm is started.  However, I still can ssh into the system. The error was shown:

[   23.007070] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, last signaled seq=173, last emitted seq=175
[   23.007087] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=26, last emitted seq=27
[   23.007088] [drm] GPU recovery disabled.
[   23.007090] [drm] GPU recovery disabled.

The attachment is the full journal log.

If I blacklist amdgpu module, it can boot and go into the desktop environment correctly.
Comment 1 Martin Peres 2019-11-19 08:45:00 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/458.


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.