Bug 106496 - Hung screen at modprobe amdgpu
Summary: Hung screen at modprobe amdgpu
Status: RESOLVED DUPLICATE of bug 106245
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-13 00:56 UTC by Aaron
Modified: 2018-05-14 10:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg output from a failed attempt to load amdgpu (80.65 KB, text/plain)
2018-05-13 00:56 UTC, Aaron
no flags Details
kernel config used to build test kernel (132.66 KB, text/x-mpsub)
2018-05-13 00:57 UTC, Aaron
no flags Details

Description Aaron 2018-05-13 00:56:40 UTC
Created attachment 139536 [details]
dmesg output from a failed attempt to load amdgpu

I currently have an AMD 2400G with Integrated graphics that i am trying to get to a screen with amdgpu. At the moment, booting up to a VGA console works with amdgpu blacklisted. When attempting to modprobe amdgpu, the system hangs on the vga console and the display seems to stop updating. The underlying system seems unaffected, because blindly typing 'reboot' causes the system to reboot. 

Steps to reproduce: 
1. Use kernel 4.17-rc4, compiled with the attached config. 
2. Blacklist amdgpu in modprobe.conf.d (or else booting to ANY screen will fail)
3. modprobe amdgpu

Expected result:
-Successful driver load. 

Observed result: 
-See attached dmesg output. 
(It is worth noting that the dmesg attached also shows a nvidia gpu in the pci bus. This issue is not affected by its presence or absence. This issue has been tested both ways so far.)
Comment 1 Aaron 2018-05-13 00:57:53 UTC
Created attachment 139537 [details]
kernel config used to build test kernel
Comment 2 Michel Dänzer 2018-05-14 10:24:44 UTC
You'll have to disable SME for the time being.

*** This bug has been marked as a duplicate of bug 106245 ***


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.