Bug 107301

Summary: System display will be gone suddenly after amdgpu is loaded and gdm is started
Product: DRI Reporter: jian-hong
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium    
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
System's journal log with 4.18-rc5 none

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.