Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1299933 - i915 freezes after GNOME session launch on 4.3.x kernels
Summary: i915 freezes after GNOME session launch on 4.3.x kernels
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 15:07 UTC by steven.merrill
Modified: 2016-01-20 05:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-20 05:19:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Kernel oops log from the system journal. (deleted)
2016-01-19 15:07 UTC, steven.merrill 		no flags Details
dmesg log gnome-shell 100% CPU (deleted)
2016-01-19 21:46 UTC, mm19827 		no flags Details
dmesg from kernel 4.3.3-302 after starting a GNOME Wayland session (deleted)
2016-01-19 23:25 UTC, steven.merrill 		no flags Details
View All

Description steven.merrill 2016-01-19 15:07:11 UTC 
Created attachment 1116201 [details]
Kernel oops log from the system journal.

Description of problem:

I have a Dell Inspiron 7548 running Fedora 23. This laptop has AMD and Intel graphics and I am using the free radeon drivers.

All Fedora 4.3.x kernel releases (including 4.3.3-302 just released to Bodhi) freeze up after I authenticate in GDM. Sometimes it freezes on the gray GDM background and sometimes I can see my GNOME background and a notification icon on the top.

Launching a GNOME Wayland session works, although Wayland is somewhat buggy.

I am attaching the kernel crash logs from the system journal. I'd be happy to help track this down however I can - I'm currently keeping the 4.2.8 kernel around since it's the last one I can use with non-Wayland GNOME sessions.

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

kernel-4.3.3-302.fc23
kernel-4.3.3-301.fc23
kernel-4.3.3-300.fc23

Steps to Reproduce:
1. Authenticate to GDM with "GNOME Session" selected.
2. The screen freezes.
Comment 1 Josh Boyer 2016-01-19 15:12:52 UTC 
Can you attach the output of dmesg from a fresh boot if that is possible?  The attachment here is somewhat helpful but it is not the first issue that occurred.
Comment 2 steven.merrill 2016-01-19 19:54:13 UTC 
Sure. Just to clarify, would you like the dmesg output from a successful boot into 4.2.8 where I start GNOME, or the dmesg output from a boot into 4.3.3-302 where I switch to a a different TTY and dump it (and/or start a GNOME Wayland session?)
Comment 3 Josh Boyer 2016-01-19 20:15:51 UTC 
The latter please.  Or both if it isn't too much trouble, but 4.2.8 likely isn't going to tell us much.
Comment 4 mm19827 2016-01-19 20:46:58 UTC 
Having probably the same problem on a dual-core Dell Latitude D620 with i945GM
After upgrade to kernel-4.3.3-300.fc23, display broken (Bug 1298309)
With kernel-4.3.3-301.fc23 no garbage on screen, but the GNOME desktop is _very_ slow (not really usable), top shows gnome-shell consuming 100% CPU.
KDE and Xfce run fine.
Same with kernel-4.3.3-302.fc23
KDM login screen also works fine (I do not use GDM)
4.2.8 works OK with GNOME, KDE, xfce
Comment 5 mm19827 2016-01-19 21:46:32 UTC 
Created attachment 1116397 [details]
dmesg log gnome-shell 100% CPU
Comment 6 Josh Boyer 2016-01-19 22:54:23 UTC 
(In reply to mm19827 from comment #4)
> Having probably the same problem on a dual-core Dell Latitude D620 with
> i945GM
> After upgrade to kernel-4.3.3-300.fc23, display broken (Bug 1298309)
> With kernel-4.3.3-301.fc23 no garbage on screen, but the GNOME desktop is
> _very_ slow (not really usable), top shows gnome-shell consuming 100% CPU.
> KDE and Xfce run fine.
> Same with kernel-4.3.3-302.fc23
> KDM login screen also works fine (I do not use GDM)
> 4.2.8 works OK with GNOME, KDE, xfce

Your hardware and bug do not appear to be at all similar to the original reporters.  Please file your own bug against xorg-x11-drv-intel.
Comment 7 steven.merrill 2016-01-19 23:25:12 UTC 
Created attachment 1116412 [details]
dmesg from kernel 4.3.3-302 after starting a GNOME Wayland session
Comment 8 steven.merrill 2016-01-19 23:31:26 UTC 
Josh,

Thanks for offering to help. I've attached dmesg from a boot into 4.3.3-302. I was able to launch a GNOME Wayland session and dump that. I then switched back into a regular GNOME session and got the freeze but the kernel crash logs for this time do not appear to be in my system journal.

I'll also note that both kernels are started using the 'i915.enable_ips=0' option because it fixes some strange display issues for me, and I have also added 'omit_drivers+=" hid_multitouch "' into a file in /etc/dracut.conf.d because without doing that I would get kernel panics before reaching GDM approximately 30-50% of the time.

Please let me know what else I can do to help test this out.
Comment 9 Josh Boyer 2016-01-20 01:23:18 UTC 
[    1.178272] Setting dangerous option enable_rc6 - tainting kernel
[    1.178274] Setting dangerous option enable_fbc - tainting kernel
[    1.178276] i915: unknown parameter 'lvds_downclock' ignored
[    1.178277] Setting dangerous option semaphores - tainting kernel

I don't see these options on the kernel cmdline, but something is clearly setting them.  What happens if you remove the entries in whatever file is doing that?
Comment 10 steven.merrill 2016-01-20 05:19:09 UTC 
Josh,

That did it.

I had made an /etc/modprobe.d/i915.conf file that had those 4 options in there. After removing the file and re-running dracut from GNOME Wayland, I'm happy to report that I'm booted into GNOME on 4.3.3-302. I'll run this tomorrow during the work day and if everything's good, karma the kernel update at the end of the day.

Thanks again for the help!
Note You need to log in before you can comment on or make changes to this bug.