Booting with intel graphics enabled results in a lockup

[Ian Booth]

Booting with intel graphics enabled results in a lockup loading lightdm or logging in results in the greeter screen appearing again. The laptop has a Nvidia GTX730 graphics card which can be switched off via bumblebee or prime.
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ian 2045 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
MachineType: Notebook P65_P67RGRERA
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro quiet splash
ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-43-generic N/A
 linux-backports-modules-3.19.0-43-generic N/A
 linux-firmware 1.155
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.10
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: P65_P67RGRERA
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1533221

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[penalvch (penalvch)]

Ian Booth, thank you for reporting this and helping make Ubuntu better.

Given attempting to deal with more than one issue in one report is unwieldy, let this report focus on only the first issue mentioned:
"1. Intel HD graphics Booting with intel graphics enabled results in a lockup loading lightdm or logging in results in the greeter screen appearing again."

Regarding the other issues mentioned, it will be most helpful to file a new report, one report per issue. Please feel free to subscribe me to them.

Focusing on the scope of this report, could you please both boot into a Ubuntu kernel (not mainline/upstream), and configuration allowing you to run apport-collect again?

Unfortunately, apport-collect'ing while booted into a mainline kernel doesn't provide helpful information.

Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

@Ian, is this issue a regression? Do you happen to know if there were prior kernel versions that did not exhibit this bug?

[Ian Booth (wallyworld)]

The only kernel I can get to work at all in terms of allowing lightdm to run and me to log in is 3.19.x

All Ubuntu kernels I have tried
- 4.2.0-23
- 4.3.0-6
- 4.4.0-0

cause boot to lock up. It's not just lightdm that fails. You can't even Alt-Shift F1 to a console.

The only 4.x kernel that works (which also allows networking) in mainline 4.4.

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[Ian Booth (wallyworld)]

apport information

[penalvch (penalvch)]

Ian Booth, the next step is to fully reverse commit bisect from kernel 4.3 to 4.4 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joseph Salisbury (jsalisbury)]

If the 4.4 kernel resolves this bug, I can help you perform a reverse bisect.

Can you also give the latest upstream 4.2 stable kernel a try, to see if the fix in mainline was also cc'd to stable? The upstream 4.2 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.8-ckt1-wily/

[Timo Aaltonen (tjaalton)]

4.2 didn't enable skylake support in drm/i915, and they (intel) refuse to send patches for v4.2.x.

[Ian Booth (wallyworld)]

Using the latest 4.4.0 kernel, I can now boot. But only with nvidia graphics card enabled. Intel graphics is still broken.

Backlight function keys are still not working. I have tried various combinations of:
acpi_osi=Linux acpi_backlight=native
acpi_osi=Linux acpi_backlight=vendor
etc

with no luck.

ian@wallyworld:~$ apt-cache policy linux-image-4.4.0
linux-image-4.4.0-0-generic:
  Installed: 4.4.0-0.12
  Candidate: 4.4.0-0.12
  Version table:
 *** 4.4.0-0.12 0
        500 http://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/ xenial/main amd64 Packages
        100 /var/lib/dpkg/status
linux-image-4.4.0-040400-generic:
  Installed: 4.4.0-040400.201601101930
  Candidate: 4.4.0-040400.201601101930
  Version table:
 *** 4.4.0-040400.201601101930 0
        100 /var/lib/dpkg/status
linux-image-4.4.0-0-lowlatency:
  Installed: (none)
  Candidate: 4.4.0-0.12
  Version table:
     4.4.0-0.12 0
        500 http://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/ xenial/main amd64 Packages

[penalvch (penalvch)]

Ian Booth:
>"Using the latest 4.4.0 kernel, I can now boot. But only with nvidia graphics card enabled. Intel graphics is still broken."

To clarify, when you tested 4.4, both the intel and nvidia card were enabled simultaneously?

If so, did it result in a lockup as this report is scoped to?

>"Backlight function keys are still not working."

To advise, the scope of this report has nothing to do with the backlight functionality. Hence, in order to avoid scope creep and confusion, please contain the results to how it relates to the scope of "Booting with intel graphics enabled results in a lockup"?

[Ian Booth (wallyworld)]

I have the nvidia binary drivers installed from the graphics-drivers ppa.
I use prime-select to choose either "nvidia" or "intel".

Using nvidia boots fine. When intel is selected:
- lightdm greeter screen displays in low res (maybe 640x480, not sure)
- logging in simply returns to the greeter screen

Using this latest kernel, I have not seen any blank screens trying to boot with intel. But as per above, I can't log in.

[penalvch (penalvch)]

Ian Booth, to clarify, using the nvidia PPA is not supported.

Hence, is this reproducible with a nvidia driver provided by the Ubuntu repositories, with all the non-default kernel parameters removed?

[Timo Aaltonen (tjaalton)]

do you have linux-image-extra-4.4.0 installed, and i915.ko module loaded when running with intel?

[Timo Aaltonen (tjaalton)]

also, attach dmesg from 4.4.0 running intel

[Ian Booth (wallyworld)]

Attached is dmesg as requested

[Ian Booth (wallyworld)]

Also lsmod | grep 915

parport 49152 3 lp,ppdev,parport_pc
i915 1204224 3
i2c_algo_bit 16384 1 i915
drm_kms_helper 135168 1 i915
drm 360448 5 i915,drm_kms_helper,nvidia
video 40960 1 i915

Yes, I have image-extra installed.

I tried removing nvidia-261 but this resulted in a freeze at boot just after the graphics drivers were loaded. Using the nvidia drivers is the only way I can get a functioning system.

[Ian Booth (wallyworld)]

Sorry, meant to say nvidia-361 in last comment.

[Timo Aaltonen (tjaalton)]

switch to intel, boot with 'drm.debug=14' added to kernel cmdline, login from console (ctrl-alt-F1) and copy dmesg log and /var/log/Xorg.0.log somewhere, then attach here once you have the system back on nvidia..

[Ian Booth (wallyworld)]

Attached is the X log after adding the debug line.

[Ian Booth (wallyworld)]

And the dmesg output.

[Timo Aaltonen (tjaalton)]

[ 12.239] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: undefined symbol: _glapi_tls_Dispatch)
[ 12.239] (EE) AIGLX: reverting to software rendering
[ 12.263] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
[ 12.263] (EE) GLX: could not load software renderer

there's your error.. do you use gpu-manager? When switching to intel it should also switch to mesa libs.. so maybe there's a bug

[Ian Booth (wallyworld)]

I've never run gpu-manager.
I use prime-select to choose between nvidia and intel.

I could not install wily on this laptop from a usb stick as the install process locked up trying to load the graphics drivers. I had to start with vivid as the older kernel did work. Upgrading to wily, the only way I could get things to work is to use a recent kernel with the binary nvidia drivers. I need a recent kernel to support the Intel 8260 wireless chipset. I'd prefer just to use the Intel graphics to get better battery life. But so far attempts to do that and have a working machine have failed.

If I try and boot after uninstalling the nvidia drivers, the I can't get a graphical login to work (see comment #33).

Is there anything I can do to resolve the above error with switching to Intel using prime-select? Or ideally, I'd not install the nvidia drivers at all. But no luck so far doing that.

[Timo Aaltonen (tjaalton)]

Then you need to provide more logs with nvidia purged away. Do check Xorg.0.log for lines with "(EE)", and maybe also try blacklisting nouveau from loading.

[Ian Booth (wallyworld)]

I totally purged nvidia drivers and blacklisted nouveau. Everything was straight intel.

The machine would boot to the greeter and attempts to login would result in a freeze; console was not obtainable.

Attached is the dmesg log, and to follow the Xorg log. I couldn't see any obvious errors.

[Timo Aaltonen (tjaalton)]

thanks, yes everything looks fine...

what do you mean by "freeze"? blank screen or something else?

[Timo Aaltonen (tjaalton)]

one thing to try would be the latest drm-intel-next kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/

[Ian Booth (wallyworld)]

The login screen shows ok. But when I type the password and hit enter, the cursor freezes. I can't even switch to a console login at that point. I got the logs by going straight to a console login instead of attempting to login normally.

When trying to install wily direct from a USB stick, I also got freezes as it was trying to display the install dialog. But the vivid install worked (as it was using a 3.9 kernel maybe?). But after install I still had to install the nvidia drivers from the console to get X working properly I think. And from there I could upgrade to wily. And from there I installed the 4.4.0 kernel to get wireless networking happy.

I don't understand why the login screen can show and then not the desktop.

[Ian Booth (wallyworld)]

Progress - using the next intel kernel works *with* nvidia installed also. ie prime-select intel | nvidia works.
It hangs on shutdown, but at least I can log in now.

A 4.4.x kernel is not scheduled for inclusion in xenial is it. The 4.4.x is the only one that works for me from what I can tell.

Thanks for the help :-D

[Timo Aaltonen (tjaalton)]

xenial will get 4.4, but drm-intel-next has code for i915 that'll be in 4.5, so if there's something that fixed intel for you then that'd need to be bisected and backported to 4.4

[Sönke von Heymann (svheymann)]

I have the same problem, my hardware is a Clevo P640RE with intel i7-6700HQ and a nvidia GTX970M.

With 15.10 i got it working (a little bit) with i915.preliminary_hw_support=1 and nomodeset, but the system always froze after some seconds, except if starting in recovery mode. I tried different nvidia-drivers but that did not change anything.

So i tried 16.04 alpha but i had the same issues with kernel 4.3 as with 4.2, only recovery mode was working. After compiling & installing the latest 4.4.0.1.15 kernel (4.3 config and default to all questions) and with the newest nvidia-361 i can still not use the nvidia-card (the login problem mentioned above) but at least it starts with the intel gpu if i boot in recovery mode.

Also i cannot change the brightness using the intel gpu.

At some point after installing/uninstalling nvidia-drivers i got a working nvidia-config for a moment and i was able to change brightness, but that did only last until the next reboot and everything was broken again.

If i start with 4.4.0.1.15 without recovery mode, it switches to a blank black screen after grub, cpu seems to go to 100% and freezes. nomodeset has no effect.

[Sönke von Heymann (svheymann)]

I just tested this with acutal kernel 4.4.0.2, it is still the same issue.
Laptop screen gets black shortly after boot, recovery mode is still working.

[Scott Deagan (scott-deagan)]

I have a P65_P67RGRERA with an nVidia GTX 970m. I too have "kind of" got it working by:

1. Installing the 4.6 kernel.
2. Installing the proprietary nVidia 364 driver.
3. sudo prime-select intel
4. Reboot, go in to the BIOS, and select "MSHYBRID" for the Graphics option.
5. Save BIOS changes and exit the BIOS settings (save and exit).
6. Unload the nVidia modules: sudo rmmod nvidia_drm nvidia_modeset nvidia_uvm nvidia
7. Cut power to the nVidia GPU: tee /proc/acpi/bbswitch <<<OFF
8. Make sure the nVidia GPU is turned off: cat /proc/acpi/bbswitch

By using the above, my battery life doubles (I'm getting around 4 hours 30 minutes).

Unfortunately, while the above will reduce idle power consumption from around 25-30 Watts to around 12-15 Watts, certain commands will cause a kernel freeze (such as lshw or lspci).