Bug 1404423

Summary: drm initialisation fails with radeon Mobility
Product: [Fedora] Fedora Reporter: Didier Lecardez <d.lecardez>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 25CC: cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-14 07:20:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg.3.9.5-301.fc19.full trace
none
dmesg.3.9.5-301.fc19.full drm trace only
none
full dmesg trace for 4.8.13-300.fc25.x86_64 none

Description Didier Lecardez 2016-12-13 20:02:53 UTC
Created attachment 1231321 [details]
dmesg.3.9.5-301.fc19.full trace

Description of problem:

Impossible to boot if 'nomodeset' is not set.  The system hangs during the drm initialisation.
Last kernel version working is 3.9.5-301.fc19.i686.PAE
Tested all versions after 3.9.5-301.fc19 without success.


Version-Release number of selected component (if applicable):
4.8.13-300.fc25.x86_64 

How reproducible:
My system is Laptop hp dv6 with ATI Mobility Radeon HD 5000 Series
If modeset is enabled, when it  reach the drm initialization, it hangs forever.
.

Actual results:


Expected results:


Additional info: In order to narrow the problem I performed the following steps:
   -boot in nomodeset
   -issued command: modprobe radeon modeset=1
   -Now system is completely hung.
   -reboot in nomodeset and get the dmesg trace. See file jctl.fail and fetch pattern '==============' to see what's happens when modeset is enabled by command modprobe.

I made the same test with 3.9.5-301.fc19 on the SAME machine:
   -See file dmesg.3.9.5-301.fc19.full the full dmesg trace.
   -See file dmesg.3.9.5-301.fc19 that contain only the drm traces.

Comment 1 Didier Lecardez 2016-12-13 20:05:28 UTC
Created attachment 1231322 [details]
dmesg.3.9.5-301.fc19.full drm trace only

Comment 2 Didier Lecardez 2016-12-13 20:06:53 UTC
Created attachment 1231323 [details]
full dmesg trace for 4.8.13-300.fc25.x86_64

Comment 4 Didier Lecardez 2016-12-14 07:20:05 UTC

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