Bug 1485743 - 4.12.9-300 kernel will not get to GUI mode as a QEMU guest
Summary: 4.12.9-300 kernel will not get to GUI mode as a QEMU guest
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: Unspecified
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: 2017-08-27 23:13 UTC by Ed Greshko
Modified: 2018-02-28 16:14 UTC (History)
29 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-28 16:14:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output from journalctl showing kernel BUG at drivers (156.83 KB, text/x-vhdl)
2017-08-27 23:13 UTC, Ed Greshko
no flags Details

Description Ed Greshko 2017-08-27 23:13:06 UTC
Created attachment 1318798 [details]
Output from journalctl showing kernel BUG at drivers

Description of problem: Unable to reach a GUI login on an F26 system with the latest kernel and KDE.  


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


How reproducible:


Steps to Reproduce:
1. Install F26 from KDE live media as QEMU guest and all works fine with the initial 4.11.8-300 kernel

2. Run dnf and update the system
3.

Actual results:  System will shows the Fedora icon in the middle of the screen.  Never gets to SDDM login


Expected results:  A working system.


Additional info:  One can ssh into the system and gather information.  The journal output is attached.

Comment 1 Paweł 2017-08-30 12:51:57 UTC
Also have this issue with standard GNOME version of F26 inside Boxes on F25. Reverting back to older kernel works ok.

Comment 2 Jimmy Martin 2017-09-12 22:27:55 UTC
I am also having this same issue.

Comment 3 Ed Greshko 2017-09-12 23:47:33 UTC
FWIW, I just did an update to the system which brought in the 4.12.11-300.fc26.x86_64 kernel.  No change.  Still fails.

Comment 4 Jimmy Martin 2017-09-15 15:27:01 UTC
Hi there, Ed,

The issue still occurs with the brand new 4.12.12-300.fc26 kernel I updated to today.

A workaround for you for now is:

1. At boot select the kernel not booting.

2. Hit 'e' on your keyboard to edit.

3. Find the kernel parameters line and remove 'rhgb' (Begins with linux16).

4. Hit Ctrl+x to boot.

This should get you past the Plymouth screen at least.

As a note:
On that new kernel, my display shows some occasional flashing. Replacing rhgb with nomodeset resolves it.

Comment 5 Chris Brodt 2017-09-19 17:22:58 UTC
I had the same issue with the 4.12.13-300.fc26 kernel. I was able to login to an X.Org GNOME session after removing 'rhgb' from boot params, but can't increase the display resolution past 1280x720.

Also it hangs if I try and enter a Wayland GNOME session regardless of resolution settings.

Comment 6 Jimmy Martin 2017-09-19 18:25:38 UTC
Hi there, Chris.

Replace 'rhgb'with 'nomodeset' this should allow you to get in with either an X session or Wayland. Then your screen resolution should go higher.
 
(In reply to Chris Brodt from comment #5)
> I had the same issue with the 4.12.13-300.fc26 kernel. I was able to login
> to an X.Org GNOME session after removing 'rhgb' from boot params, but can't
> increase the display resolution past 1280x720.
> 
> Also it hangs if I try and enter a Wayland GNOME session regardless of
> resolution settings.

Comment 7 Tim Landscheidt 2017-09-26 18:23:56 UTC
(To avoid having to remove "rhgb" in /etc/grub2.cfg after every kernel update, one can change the "template" in /etc/default/grub.)

Comment 8 Laura Abbott 2018-02-28 03:44:18 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  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 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 9 Ed Greshko 2018-02-28 04:10:44 UTC
I have moved on to F27 and 4.15.4-300.fc27.  At this level, the issue described doesn't exist.  So, whatever it was has been "fixed".  So, I doubt there is any value to keeping this BZ open.  If you agree, please close.

Comment 10 Laura Abbott 2018-02-28 16:14:55 UTC
I agree. Thanks for letting us know and feel free to reopen if you see the bug again.


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