Bug 1378193 - drm initialisation results in a hung system
Summary: drm initialisation results in a hung system
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 19:30 UTC by Didier Lecardez
Modified: 2017-08-09 02:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:34:08 UTC
Type: Bug


Attachments (Terms of Use)
Contains attachment files in tar format (780.00 KB, application/x-tar)
2016-09-21 19:30 UTC, Didier Lecardez
no flags Details
messages of the working system (97.05 KB, text/plain)
2016-09-21 19:41 UTC, Didier Lecardez
no flags Details
messages of the hung system (174.25 KB, text/plain)
2016-09-21 19:42 UTC, Didier Lecardez
no flags Details
Graphic configuration (76.68 KB, image/jpeg)
2016-09-21 19:43 UTC, Didier Lecardez
no flags Details
diff of the drm messages (421.52 KB, image/jpeg)
2016-09-21 19:44 UTC, Didier Lecardez
no flags Details

Description Didier Lecardez 2016-09-21 19:30:04 UTC
Created attachment 1203446 [details]
Contains attachment files in tar format

Description of problem:

Laptop hp dv6 with ATI Mobility Radeon HD 5000 Series

Impossible to boot if 'nomodeset' is not set.  The system hangs during the drm initialisation.

Version-Release number of selected component (if applicable):

4.7.3-200. or any versions starting 3.10.x.x.


The problem already started with latest Fedora 19 kernels:
 With: 3.9.5-301.fc19  --> Never got any boot problems.
 Problem started with version  3.10.x.x.

If 'nomodeset' is used the problem disappears. But I cannot use an external monitor.
Tested with Ubuntu 16.04.1 LTS --> Same problem.

 In order to narrow the problem, I made the following test with 3.9.5-301.fc19  and 4.7.3-200.fc24
 
 1- boot in nomodeset and run level 2
 2 -log in
 3- type: modprobe radeon modeset=1
    No problems with 3.9.5-301.fc19 
    System hung with 4.7.3-200.fc24

 4- get the /var/log/message file.

Attached files:
	Messages.3.9.5-301.full
	Messages.4.7.3-200.full
	diff-drm.jpeg
	Graphic.Config.jpeg

Looking at the diff-drm.jpeg file , I noticed that the GTT value is 512K for 3.9.5-301.fc19 but 1024k for  4.7.3-200.fc24
I have no explanations as both traces are from the same machine.

Comment 1 Didier Lecardez 2016-09-21 19:41:53 UTC
Created attachment 1203452 [details]
messages of the working system

Comment 2 Didier Lecardez 2016-09-21 19:42:44 UTC
Created attachment 1203453 [details]
messages of the hung system

Comment 3 Didier Lecardez 2016-09-21 19:43:27 UTC
Created attachment 1203454 [details]
Graphic configuration

Comment 4 Didier Lecardez 2016-09-21 19:44:17 UTC
Created attachment 1203455 [details]
diff of the drm messages

Comment 5 Justin M. Forbes 2017-04-11 14:43:34 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 6 Didier Lecardez 2017-04-11 19:18:34 UTC
Yes, I tried to install Fedora 25 and the problem still persists.
Nevertheless I have a new laptop that does not show the problem.
This means I do not need a fix anymore.

Comment 7 Fedora End Of Life 2017-07-25 23:10:44 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 8 Fedora End Of Life 2017-08-08 17:34:08 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.