| Summary: | drm initialisation fails with radeon Mobility | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Didier Lecardez <d.lecardez> | ||||||||
| Component: | xorg-x11-drv-ati | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 25 | CC: | cz172638, gansalmon, ichavero, itamar, jonathan, j, 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: | 2017-12-12 10:40:33 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: |
|
||||||||||
Created attachment 1231327 [details]
dmesg.3.9.5-301.fc19.full trace
Created attachment 1231328 [details]
dmesg.3.9.5-301.fc19.full drm traces only
All kernel versions after 3.9.5-301 have the same problem *** Bug 1404423 has been marked as a duplicate of this bug. *** 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. 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. |
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)