Bug 1404430 - drm initialisation fails with radeon Mobility
Summary: drm initialisation fails with radeon Mobility
Keywords:
Status: CLOSED EOL
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:
: 1404423 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 20:26 UTC by Didier Lecardez
Modified: 2019-01-09 12:54 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:40:33 UTC
Type: Bug


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

Description Didier Lecardez 2016-12-13 20:26:51 UTC
Created attachment 1231326 [details]
full dmesg trace for 4.8.13-300.fc25.x86_64

Description of problem:

Booting with modeset enabled fails at the drm initialization and hangs forever.
My system has an  ATI Mobility Radeon HD 5000 Series

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

How reproducible:
boot with modeset enabled


Expected results:
Have my sytem boot with modeset enabled.

Additional info:
In order to narrow the problem, I made the following test:

-boot with modeset disabled.
-log in
-issue command:  modprobe radeon modeset=1 this results in a hung system.
-reboot with modeset disabled  to get the dmesg traces (See file dmesg.4.8.13-300.fc25.x86_64.fail)
   Fetch pattern '============' in this file to see what happens immediately after issuing the modprobe radeon modeset=1 command


Now I made the same test on the SAME system running 3.9.5-301.fc19
- See dmesg.3.9.5-301.fc19.full (full dmesg)
- See dmesg.3.9.5-301.fc19 (dmesg containing drm traces  only)

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

Comment 2 Didier Lecardez 2016-12-13 20:28:54 UTC
Created attachment 1231328 [details]
dmesg.3.9.5-301.fc19.full drm traces only

Comment 3 Didier Lecardez 2016-12-13 20:33:25 UTC
All kernel versions after 3.9.5-301 have the same problem

Comment 5 Didier Lecardez 2016-12-14 07:20:05 UTC
*** Bug 1404423 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2017-11-16 19:42:35 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2017-12-12 10:40:33 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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