Bug 1404423 - drm initialisation fails with radeon Mobility
Summary: drm initialisation fails with radeon Mobility
Keywords:
Status: CLOSED DUPLICATE of bug 1404430
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 25
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 20:02 UTC by Didier Lecardez
Modified: 2019-01-09 12:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-14 07:20:05 UTC
Type: Bug


Attachments (Terms of Use)
dmesg.3.9.5-301.fc19.full trace (68.56 KB, text/plain)
2016-12-13 20:02 UTC, Didier Lecardez
no flags Details
dmesg.3.9.5-301.fc19.full drm trace only (2.79 KB, text/plain)
2016-12-13 20:05 UTC, Didier Lecardez
no flags Details
full dmesg trace for 4.8.13-300.fc25.x86_64 (94.05 KB, text/x-vhdl)
2016-12-13 20:06 UTC, Didier Lecardez
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.