Bug 1320992 - Can't load desktop environment on kernels newer than 4.4.3
Summary: Can't load desktop environment on kernels newer than 4.4.3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-24 12:48 UTC by Henrik Pauli
Modified: 2016-10-11 11:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-11 11:10:36 UTC
Type: Bug


Attachments (Terms of Use)
Successful (kernel 4.4.3) Xorg.log (50.05 KB, text/plain)
2016-03-24 12:48 UTC, Henrik Pauli
no flags Details
Unsuccessful (kernel 4.4.5) Xorg.log (49.86 KB, text/plain)
2016-03-24 12:49 UTC, Henrik Pauli
no flags Details

Description Henrik Pauli 2016-03-24 12:48:31 UTC
Created attachment 1139940 [details]
Successful (kernel 4.4.3) Xorg.log

I have an HP laptop, and I'm running Fedora 23 with various DMs and DEs.  Currently LightDM and MATE, but it has seen GDM, and Plasma 5, XFCE, all of which show the exact same problem.

With the newer kernels (4.4.4 and above) the machine boots, switches to the DM, and I can interact with it just fine, but the moment I log in to any of the mentioned desktops, the machine locks up hard: the mouse cursor doesn't move even.

With 4.4.3 everything works fine.

Here's my fpaste --sysinfo: http://paste.fedoraproject.org/344530/45881575/

The only significant difference between the Xorg.logs is the last two lines, where the machine doesn't lock up, it will say:

(II) intel(0): resizing framebuffer to 3840x1369
(II) intel(0): switch to mode 1920x1080 on eDP1 using pipe 0, position (1920, 289), rotation normal, reflection none

Comment 1 Henrik Pauli 2016-03-24 12:49:19 UTC
Created attachment 1139941 [details]
Unsuccessful (kernel 4.4.5) Xorg.log

Comment 2 Laura Abbott 2016-03-24 15:41:59 UTC
Please test 4.4.6. There were known bugs fixed there.

Comment 3 Henrik Pauli 2016-03-24 16:44:46 UTC
I wish I could pin 4.4.3 to stay so any other kernels get replaced but I always have one version that is known to work -- AFAIK this is only possible with yum (`yumdb set installonly keep ...`) and not possible with dnf, right?

I'll extend the number of kept kernel images in dnf.conf and will give 4.4.6 a try when I can

Comment 4 Josh Boyer 2016-03-24 17:03:24 UTC
(In reply to Henrik Pauli from comment #3)
> I wish I could pin 4.4.3 to stay so any other kernels get replaced but I
> always have one version that is known to work -- AFAIK this is only possible
> with yum (`yumdb set installonly keep ...`) and not possible with dnf, right?

No, that is not correct.  If you boot into 4.4.3 on your machine and install 4.4.6, dnf should refuse to remove 4.4.3 because it is the currently running kernel.  It will remove a kernel older/newer than 4.4.3 kernel instead.

> I'll extend the number of kept kernel images in dnf.conf and will give 4.4.6
> a try when I can

That's another possibility but it should not be required.

Comment 5 Henrik Pauli 2016-03-25 11:19:26 UTC
4.4.6 appears to work, thank you.

Comment 6 Laura Abbott 2016-09-23 19:46:56 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 7 Henrik Pauli 2016-10-11 10:59:53 UTC
As I said in the previous comment, 4.4.6 appeared to work at the time.  The issue has not resurfaced since.

Comment 8 Josh Boyer 2016-10-11 11:10:36 UTC
Thank you again.


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