Bug 1151052 - Kernel upgrade to 3.16.3-200.fc20 causes GUI/X11 to fail to start
Summary: Kernel upgrade to 3.16.3-200.fc20 causes GUI/X11 to fail to start
Keywords:
Status: CLOSED DUPLICATE of bug 1151757
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
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: 2014-10-09 13:48 UTC by Karl
Modified: 2014-10-13 14:06 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-13 14:06:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karl 2014-10-09 13:48:43 UTC
Description of problem:
Installed fresh Fedora 20, then updated (kernel 3.11.10-301.fc20 -> 3.16.3-200.fc20, among many other things) and restarted.  The X server won't start with the 3.16.x kernel; it gets as far as the Fedora logo, then the screen goes blank.  If I press Escape to see the bootup progress, it hangs immediately (i.e., before the Fedora logo would have gone away).  No login screen appears, and no text-only TTYs are available either (e.g., CTRL-ALT-F2 does nothing).  After a hard reset, I can reboot using the 3.11.x kernel, but never the 3.16.x kernel.

Version-Release number of selected component (if applicable):
kernel-3.16.3-200.fc20.x86_64
xorg-x11-xinit-1.3.4-1.fc20.x86_64
xorg-x11-xauth-1.0.9-1.fc20.x86_64
xorg-x11-server-common-1.14.4-11.x86_64
xorg-x11-server-Xorg-1.14.4-11.x86_64
gdm-3.10.0.1-1.fc20.x86_64

How reproducible:
Unknown

Steps to Reproduce:
I don't know how reproducible this is, or even what information to post; I will do my best to follow up if necessary with such information as may be required.

Actual results:
System crash with no keyboard recognition or interaction of any kind.

Expected results:
Normal startup of X11 server and GDM.

Additional info:
This bug is similar to Bug #1147543, but the symptoms are different (i.e., complete lack of output vs. limited text-only output).

Comment 1 Karl 2014-10-13 14:06:45 UTC

*** This bug has been marked as a duplicate of bug 1151757 ***


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