Bug 1317572 - kernel-4.4.4-301.fc23 - computer frozen after logging on (gdm) [NEEDINFO]
Summary: kernel-4.4.4-301.fc23 - computer frozen after logging on (gdm)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 15:15 UTC by Miroslav Pragl
Modified: 2016-10-26 17:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:59:41 UTC
Type: Bug
labbott: needinfo? (miroslav)


Attachments (Terms of Use)
lspci (1.64 KB, text/plain)
2016-03-15 09:09 UTC, lambda.xy.x
no flags Details
/var/log/messages (258.71 KB, application/x-gzip)
2016-03-15 09:11 UTC, lambda.xy.x
no flags Details

Description Miroslav Pragl 2016-03-14 15:15:49 UTC
Description of problem: kernel-4.4.4-301.fc23 - computer frozen after logging on (gdm) 


Version-Release number of selected component (if applicable):
kernel-4.4.4-301.fc23 hangs up

How reproducible:
Easily

Steps to Reproduce:
1. boot kernel-4.4.4-301.fc23
2. enter GDM l/p
3. computer frozen completely

Comment 1 lambda.xy.x 2016-03-15 09:08:34 UTC
The same happens to me with kernel-4.4.4-301.fc23.x86_64. Power off via pressing the power button for 4s works. Before login, switching to the console from gdm works (including login), after the freeze it does not. Booting with kernel-4.4.3-300.fc23.x86_64 works again. I don't see any relevant errors in my log files, but will attach lspci and today's /var/log/messages .

Comment 2 lambda.xy.x 2016-03-15 09:09:11 UTC
Created attachment 1136462 [details]
lspci

My lspci

Comment 3 lambda.xy.x 2016-03-15 09:11:25 UTC
Created attachment 1136463 [details]
/var/log/messages

obtained by grep -a "Mar 15" /var/log/messages (contains strings of \0, I assume from they come from the freeze)

Comment 4 Laura Abbott 2016-03-15 16:24:12 UTC
Please test http://koji.fedoraproject.org/koji/taskinfo?taskID=13347691

Comment 5 lambda.xy.x 2016-03-15 16:51:33 UTC
Thanks for having a look - the freeze still happens with kernel-4.4.5-300.radeonfix.fc23.x86_64.rpm . Can I provide more information?

Comment 6 Laura Abbott 2016-03-15 18:43:21 UTC
There is apparently yet another radeon fix. http://koji.fedoraproject.org/koji/taskinfo?taskID=13356645 is building with just the 2nd fix. Please test that when it finishes.

Comment 7 lambda.xy.x 2016-03-15 23:24:02 UTC
The second build (kernel-4.4.5-300.radeonfix2.fc23.x86_64.rpm) did the trick, thanks a lot for the help!

Comment 8 Miroslav Pragl 2016-03-18 15:01:33 UTC
Probably merge with https://bugzilla.redhat.com/show_bug.cgi?id=1317179 pls. Occurs on radeon as well.

Thanks

MP

Comment 9 Laura Abbott 2016-09-23 19:54:23 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is 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 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  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 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 10 Laura Abbott 2016-10-26 16:59:41 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 11 lambda.xy.x 2016-10-26 17:04:21 UTC
Just to be precise: this bug has been resolved (see comments above). Thanks again to Laura Abbott :)


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