Computer freezes after login - 4.10.0-22-generic

[Hagen Kuehn]

I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days ago. Login worked fine too.

A couple of days later I installed the suggested kernel update "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer freezes right after login (i.e. after pressing enter, the background image with the mouse is shown, no responses to any key strokes).

Syslog excerpt:

Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf intel_lpss_pci intel_pch_thermal
Jun 12 22:12:48 computername kernel: [ 47.603422] hci_uart btbcm btqca btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid pinctrl_sunrisepoint video wmi pinctrl_intel fjes
Jun 12 22:12:48 computername kernel: [ 47.603453] CPU: 1 PID: 1672 Comm: Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
Jun 12 22:12:48 computername kernel: [ 47.603453] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not observed with 4.10.0-21-generic. As I was not able to login to my computer I am writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore the information attached through the "ubuntu-bug linux" command here, are referring to the kernel that is actually working. I decided to nonetheless include that information as it might contain other kernel unrelated information that would help you troubleshooting.

Please see attached file "syslog-4.10.0-22-generic-----freeze-after-login.log" for the full syslog.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic 4.10.0-21.23
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hkuehn 1796 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon Jun 12 23:17:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-05-30 (13 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
 Bus 001 Device 004: ID 0c45:6713 Microdia
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-21-generic N/A
 linux-backports-modules-4.10.0-21-generic N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.3
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Does this issue go away if you boot with the prior kernel version?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/

[Hagen Kuehn (hag-k)]

In answer to your qeustion https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3

* Yes, the problem is NOT encountered when using Kernel linux-image-4.10.0-21-generic 4.10.0-21.23.

* The problem is encountered when using 4.10.0-22-generic

In response to your request https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/4

I have tested with upstream kernel 4.10.17

linux-headers-4.10.17-041017_4.10.17-041017.201705201051_all.deb
linux-headers-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb
linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb

and equally encountered the problem. I therefore added the tag: 'kernel-bug-exists-upstream'.

[Joseph Salisbury (jsalisbury)]

Can you also see if this bug happens with the latest mainline kernel? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5

[Hagen Kuehn (hag-k)]

In answer to your question https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/6

I have tested with Kernel 4.12.0, and DID NOT ENCOUNTER this problem.

linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb
linux-headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb
linux-image-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb

Note, while installing Kernel 4.12.0, I got below stdout.

$ sudo dpkg -i linux-*
Selecting previously unselected package linux-headers-4.12.0-041200rc5.
(Reading database ... 182643 files and directories currently installed.)
Preparing to unpack linux-headers-4.12.0-041200rc5_4.12.0-041200rc5.201706112031_all.deb ...
Unpacking linux-headers-4.12.0-041200rc5 (4.12.0-041200rc5.201706112031) ...
Selecting previously unselected package linux-headers-4.12.0-041200rc5-generic.
Preparing to unpack linux-headers-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb ...
Unpacking linux-headers-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) ...
Selecting previously unselected package linux-image-4.12.0-041200rc5-generic.
Preparing to unpack linux-image-4.12.0-041200rc5-generic_4.12.0-041200rc5.201706112031_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
Done.
Unpacking linux-image-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) ...
Setting up linux-headers-4.12.0-041200rc5 (4.12.0-041200rc5.201706112031) ...
Setting up linux-headers-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
Setting up linux-image-4.12.0-041200rc5-generic (4.12.0-041200rc5.201706112031) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.12.0-041200rc5-generic /boot/vmlinuz-4.12.0-041200rc5-generic
update-initramfs: Generating /boot/initrd.img-4.12.0-041200rc5-generic
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gm20b/pmu/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvid...

[Christian Adamski (christian-adamski)]

I'm confirming this issue on a DELL XPS 15 as well. It's still present with 4.10.0.24.

My workaround is to bot 4.10.0.21

[Adam Nave (xcorvis)]

Can confirm on Dell XPS 15 with 4.10.0-26. This is also the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696665 and another workaround is described here: https://rileymacdonald.ca/2017/06/26/ubuntu-broken-boot-on-dell-xps-15-after-kernel-update-upgrade/

[Ben (benjamin-o7p)]

Same here, with Dell XPS 15 (ngg9x) too

[Hagen Kuehn (hag-k)]

I have tested the suggested workarounds that were given with comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9 in conjunction with kernel 4.10.0-24. Those two workarounds basically suggest not to use the nouveau driver but instead the Nvidia drivers.

Those workarounds do not work. When the Nvidia driver is configured and the machine booted by using kernel 4.10.0-24, the computer freezer just before the login window.

[Hagen Kuehn (hag-k)]

In line with comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/11, the workarounds suggested with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/9 do not work with kernel 4.10.0-28 either. The computer freezes just before the login screen appears. Note, no key strokes are recognised and it's not possible to switch to another TTY (same as with originally reported problem).

[John Lewis (jlewis-johnlewis-deactivatedaccount)]

Well, I'm using 4.10.0.28 and nvidia-381 on my XPS 15 9560 and I'm able to login.

I did update to the latest BIOS version too though (1.34), so maybe that had an effect, IDK.

It did complain about a plymouthd crash, and I got it to send a report, so don't know if that will help.

http://www.linuxandubuntu.com/home/how-to-install-latest-nvidia-drivers-in-linux
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

I hope this information helps someone else - I did spend a few hours trying to find a workaround. :)

[Milan (donwey)]

Can confirm this issue on my Dell XPS 9560. I downloaded iso of ubuntu 16.04 made it bootable and i tried to boot into installation menu but i got stuck on loading screen, before it showed up error with noveau and cant create kernel channel, 22. Any fix please.

[hamid (alias-neo-one)]

I have the same issue on my Dell XPS 9560. It has been running fine in "intel" graphics mode up until and including kernel 4.8. With 4.10 and 4.11 it either freezes pre-boot, before I even reach the FDE password prompt, or, if I uninstall the nvidia drivers, it freezes at some point after.

Currently I have no nvidia drivers installed, and have had to move back to 4.8 to boot, because 4.10 lets me enter the FDE password and then freezes.

I've tested various combinations of kernel and drivers/no drivers and kernel versions, and have seen either a freeze preventing me from accessing the logs or, where possible seen "CPU stuck" messages.

[John Lewis (jlewis-johnlewis-deactivatedaccount)]

Well, I'm running 4.10.0-33-generic, and although sometimes I have to login twice, and it has frozen on a couple of occasions, it's pretty much okay. So I'm not sure what exactly is different about my combo than yours, except maybe the firmware version I'm running on the 9560.

[John Lewis (jlewis-johnlewis-deactivatedaccount)]

When you had the nvidia drivers installed, can you confirm how you installed them?

[Marco Scavazzon (marco-skv)]

Same issue here.
Dell XPS 15 9560, Ubuntu 16.04 (with the latest software updates), using Nouveau driver and the latest firmware available from Dell.
With kernel 4.10.0-33, the computer freezes after I enter the password of the login screen.
With kernel 4.8.0-58 the computer works well.

[hamid (alias-neo-one)]

John: I tried 4.10.0-33-generic, I tried 32-generic, and several versions before. I'm running the latest firmware from Dell, 1.3.4 I believe, and had something older before that.

Almost every time I boot with nvidia installed it freezes at the FDE prompt, and I can't enter my password. If I don't have nvidia installed, it freezes when I try to login.

I have tried various combinations of black/whitelisting modules, nvidia installed and uninstalled and nothing seems to work.

One think that probably contributed was that at one point I had XWayland installed, I went back and installed ubuntu-desktop but there is probably some holdout somewhere in the configs that's breaking it.

Since it freezes before the FDE pass, I can't get any useful logs and can't switch TTYs or get out of the plymouth splash to see what's behind it.

It's also worth mentioning that if I boot 4.10 into recovery mode and drop to a root shell it boots fine, which is why I'm certain it's related to video drivers (it's also one of the first things loaded in the grub config I noticed.

I suspect a fresh installed might help me get around this, but it's a work machine and I don't currently have the time to set up from scratch, also, that doesn't help pinpoint the issue. For the time being I'm stuck on 4.8 because it boots and I can carry on working.

I run only in intel mode, I have no requirement in my day to day work to run nvidia and the battery benefits of being on intel are more beneficial to any graphical/performance benefits.

[hamid (alias-neo-one)]

John: Sorry, I forgot to mention, I installed the drivers from the "Additional Drivers" menu (I run Gnome), and also from "the" PPA.

[hamid (alias-neo-one)]

For reference; 4.13.0-041300-generic also BOOTS fine on my machine which fails with 4.9, 4.10 and 4.11.

I didn't try 4.12 but Hagen says it works fine. Hopefully we can figure out where the fix is so it can be back-ported to stable kernels.

[Hagen Kuehn (hag-k)]

I have reviewed the kernel source code that was committed between the Ubuntu-4.10.0-21.23 and Ubuntu-4.10.0-22.24 and I believe commit b93843fcde501b92647777ac5dbe2c980eb0b479 introduced bug #1697556.

Commit b93843fcde501b92647777ac5dbe2c980eb0b479 corresponds to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687045

In the light of this I believe that Thierry Reding <email address hidden> and Stefan Bader <email address hidden> would be the best people to look into this.

BTW, as it was not mentioned so far, Dell XPS 15 (9560) uses Intel HD 630 NVidia GeForce GTX 1050 with 4GB GDDR5.

[Anmar Oueja (anmar)]

I just checked the the 17.10 live images on my XPS 15 (9560) and the kernel still doesn't boot without using "nomodeset" kernel boot arg.

[dani_bs (sdaniele78)]

I think is the same problem of kernel 4.10 described here:
- https://askubuntu.com/questions/941211/ubuntu-16-04-freezes-with-4-10-kernel-and-nouveau-driver
- https://askubuntu.com/questions/939417/ubuntu-16-04-freezes-with-4-10-kernel

Kernel 4.8 works good.

[dani_bs (sdaniele78)]

Sorry, I involuntarily changed the state to "Fix Released" :(

[hamid (alias-neo-one)]

Back to confirmed

[Hagen Kuehn (hag-k)]

@dani_bs(sdaniele78)

I trust you commented and changed the state of the bug with good intent. Please accept my apology for being so direct... it was a complete fail.

Both links referenced do not provide any solution. One link mentions to alter the "acpi_osi kernel parameters" without details what should be changed. The second link generically talks about installing the latest OS and Nvidia updates, which is manly only a suggestion by someone to assist someone to troubleshoot a similar problem. It's no way a solution, just an attempt by someone to assist someone. Therefore both of your references do not yield any relevance to this bug.

Furthermore, when referencing other sources in the internet, you should cite the information provided there in addition to the link. This is there to ensure that the key information is never lost, since those third party websites may make articles unavailable.

I understand that you "involuntarily" changed the bug status to "Fix Released". However, wouldn't it not been better if you would have voluntarily changed it back to "Confirmed" right away?

I have changed the bug back to "Confirmed" now!

BTW, the current workaround is to use the "nomodeset" kernel boot argument. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.

[dani_bs (sdaniele78)]

@Hagen Kuehn (hag-k)

Thanks for your suggestions, I will pay more attention next time I will add a comment.

I just want to say that after I changed the bug status to "Fix Released" I could not change back to "Confirmed" because all the status was grayed and disabled. So I added my comment <<Sorry, I involuntarily changed the state to "Fix Released">>.
I'm sorry for the inconvenient.

[Kai-Heng Feng (kaihengfeng)]

Correct me if I am wrong: 4.11 is bad but 4.12-rc5 works.

So, can you try 4.12-rc1, 4.12-rc2?
4.12-rc3 and 4.12-rc4 don't have any changes to nouveau so you can skip them.

[Hagen Kuehn (hag-k)]

@Kai-Heng Feng (kaihengfeng)

Based on your suggestion I have tested with the below mainline kernels as well as the current 17.04 kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc2/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5/

Short answer:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
4.10.0-35-generic with NOMODESET -> Successfully logged in.

Though, there have been slight different behaviours observed, which I believe are noteworthy.

Long answer:
I am using the Dell XPS 15 9560 with a Dell Thunderbolt dock – tb16. The laptop itself is closed and thus only using the external monitor. To turn the laptop on, I use the power button on the docking station.

Scenario 1: v4.12-rc1 without NOMODESET -> The external screen eventually shows the login screen background and I can move the mouse. Due to the way the mouse was moving out the display area I then got the impression that it might render the login dialog on the laptop screen instead. This was confirmed by opening my laptop.

Scenario 2: v4.12-rc1 with NOMODESET -> The external screen correctly shows the login screen and I can successfully login.

Note, kernel v4.12-rc1 and v4.12-rc2 behave identical.

Scenario 3: v4.12-rc5 without NOMODESET -> The external screen correctly shows the login screen and I can successfully login.

Scenario 4: v4.12-rc5 with NOMODESET -> Eventually shows a black screen. No response to key strokes.

Scenario 5: 4.10.0-35-generic without NOMODESET -> The Ubuntu splash screen is displayed (i.e. with the circling progress icon). It never shows the login screen and appears to be stuck in an endless loop. I have observed this for about 10 minute and then turned the computer off.

Scenario 6: 4.10.0-35-generic with NOMODESET -> The external screen correctly shows the login screen and I can successfully login. Note, this is the currently latest kernel that ships with Ubuntu 17.04. This is how I currently use Ubuntu 17.04 on Dell XPS 9560.

[Adam Nave (xcorvis)]

@Hagen Kuehn
When I try to add nomodeset on the 4.10.0-35-generic kernel, my laptop freezes on the disk encryption screen. I tried it with a usb3 dock and hdmi monitor attached and without any peripherals.

[hamid (alias-neo-one)]

With disk encryption enabled is more of an issue, because the Nvidia drivers need something on the encrypted partition and thus fails to boot.

The only kernel I have successfully booted after 4.8 was 4.13. I am currently running 4.13 with disk encryption, Nvidia drivers from the PPA and the Nvidia drivers are in Nvidia mode (not Intel as Intel mode fails to boot).

I have not added the nomodeset flag.

It seems 4.13 fixes the DA200 USBC dock which I can now connect an HDMI monitor to, albeit with other horrid side effects.

[Kai-Heng Feng (kaihengfeng)]

@Hagen,

Can you test it by only blacklisting nouveau? i915 should still be loaded.
You can do that by adding "blacklist=nouveau modprobe.blacklist=nouveau" to your kernel parameter.

[Hagen Kuehn (hag-k)]

@Kai-Heng

Here are the test results when starting the kernel with "blacklist=nouveau modprobe.blacklist=nouveau".
The Dell XPS 9560 is connected to Dell Thunderbolt Dock TB16 with the external monitor and the external keyboard being connected to the docking station.

Short answer:
v4.12-rc1 -> Successfully logged in.
v4.12-rc2 -> Successfully logged in.
v4.12-rc5 -> Successfully logged in. (This is the only one without negative side effects as explained with the long answer below.)
4.10.0-35-generic -> Successfully logged in.

Long answer:
The side effects observed are likely not all related to this particular bug but I mention them here for completeness.

v4.12-rc1 -> Login scree is displayed on the laptop screen but not on the external screen. Note, up to this point of booting, the laptop was closed. After opening the laptop I can see the login screen. Regardless whether the laptop is closed I can use the external keyboard to successfully login. However from this point onwards (after login) the external keyboard stops working (while connected to the docking station). I can then only use the laptop's built in keyboard. Furthermore, the screen resolution on both screens is very low (i.e. 1600x900) whereas it should be 3840x2160 as configured on my laptop.

v4.12-rc2 -> Same behaviour as with v4.12-rc1 and 4.10.0-35-generic

v4.12-rc5 -> As far as I can tell everything works fine with my setup. The login screen is displayed on the external monitor and has not activated the built in monitor while the laptop is closed. It is using the correct screen resolution of 3840x2160 and the external keyboard continuous to work after login.

4.10.0-35-generic -> Same behaviour as with v4.12-rc1, v4.12-rc2

[Kai-Heng Feng (kaihengfeng)]

There are two separate issues:
1. The original issue, freeze. Your test result:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?

2. Login screen is displayed on the laptop screen but not on the external screen
It's an i915 issue, we should backport the fix after we fix the nouveau freeze issue.

[Hagen Kuehn (hag-k)]

@Kai-Heng

Concerning your question:
v4.12-rc1 with NOMODESET -> Successfully logged in.
v4.12-rc2 with NOMODESET -> Successfully logged in.
v4.12-rc5 without NOMODESET-> Successfully logged in.
Can I say that -rc2 has freeze but -rc5 doesn't freeze?

I would say that neither of those two kernels freeze. However they behave differently depending whether NOMODESET is configured. For example, -rc5 shows a wired behaviour when NOMODESET is used. This is explained further below.

In the light of your question I have run the tests again, but this time without modifying the kernel parameters so they are the ones that come with it by default. (i.e. only "quiet splash").

Short answer (vanilla - no additional kernel parameters set):
v4.12-rc1 -> Successfully logged in but login screen on built in monitor.
v4.12-rc2 -> Successfully logged in but login screen on built in monitor.
v4.12-rc5 -> Successfully logged in as I would expect it to work.
4.10.0-35-generic -> No login possible due to login screen never being shown.

Long answer:
v4.12-rc1 -> Same as v4.12-rc2
v4.12-rc2 -> Booting the laptop with lid closed. It does not show the login screen on the external monitor but found the login screen on the built in monitor after opening the lid. I then successfully logged in by using the external keyboard. After the login the built in monitor got disabled (no user intervention from my side) while the laptop lid was still open. The external monitor is active and displays the desktop with correct resolution. The external keyboard continued to be working after login.
v4.12-rc5 -> Successfully logged in. It correctly used the external monitor only and the keyboard continued to work after login.
4.10.0-35-generic -> The login screen is never displayed. I can see the progress icon circling endlessly. Note, the icon itself continuous to move all the time but nothing else beyond that happens. Furthermore, both screens are active and show the progress icon.

Furthermore, I have then tested v4.12-rc5 with NOMODESET again, with flowing outcome.

v4.12-rc5 with NOMODESET -> Booting laptop with lid closed. The login screen gets displayed on the external screen correctly. I then logged in by using the external keyboard, which was then followed by a black screen (i.e. monitor reported no signal) on the external monitor (note, the laptop was still closed). The laptop does not appear to react to any keystrokes. As of my testing, this black screen would remain there until the laptop lid was opened once. At least in two out of three tests this was the case, whereas with one test I was not able to get to the desktop at all. I have tested it three times by waiting differently long periods and it appears that opening the laptop lid causes the external screen to eventually show the desktop (after 20 to 30 seconds) in two of the three test cases. Note, the built in laptop screen remains black all the way. Furthermore, after the login, the external keyboard stopped working. This might explain that the laptop did not react to my keystrokes since the laptop lid was closed during this period and thus the built in keyboard was not available to me. Another observation is, which is p...

[Kai-Heng Feng (kaihengfeng)]

Let's focus on the freeze (nouveau) first. We can solve the docking output (i915) later.

Can you confirm v4.11 freezes but v4.12-rc1 doesn't?

[Hagen Kuehn (hag-k)]

@Kai-Heng

In answer to your question "Can you confirm v4.11 freezes but v4.12-rc1 doesn't?", I can confirm that 4.11.12 freezes. Kernel log shows "NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]".

Below are the test details along with the corresponding kernel log output.

Kernel version used during this test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.12/
linux-headers-4.11.12-041112_4.11.12-041112.201707210350_all.deb
linux-headers-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb
linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb

Detailed answer:
v4.11.12 -> default kernel settings -> Progress icon rotates endlessly. When toggling to the ttl output I see "NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [kworker/3:1:70]" and many more.
-> See attached file kernel.log.4.11.12.WithDefaultKernelArguments.log

v4.11.12 -> NOMODESET -> Progress icon was displayed and rotated for a while but then the entire computer turned off. -> Not frozen but dead.
-> See attached file kernel.log.4.11.12.nomodeset.log

v4.11.12 -> "blacklist=nouveau modprobe.blacklist=nouveau" -> I could login without problems and the desktop appears to be displayed and working as I would expect.
-> See attached file kernel.log.4.11.12.blacklist.nouveau.log

[Kai-Heng Feng (kaihengfeng)]

Sorry to ask again - so what's the result on v4.12-rc1, without "nomodeset"?

[Hagen Kuehn (hag-k)]

Your question:
"so what's the result on v4.12-rc1, without "nomodeset"?"

Short answer: It does not freeze.

Detailed answer:
With v4.12-rc1, by using the default kernel arguments (i.e. without "nomodeset"), it does not freeze. It shows the login screen on the closed laptop, which you pointed out is related to i915.

The kern.log shows following nouveau related output.

Sep 27 09:37:15 computername kernel: [ 3.239682] nouveau: detected PR support, will not use DSM
Sep 27 09:37:15 computername kernel: [ 3.239698] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
Sep 27 09:37:15 computername kernel: [ 3.239831] nouveau 0000:01:00.0: NVIDIA GP107 (137000a1)
Sep 27 09:37:15 computername kernel: [ 3.245638] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Sep 27 09:37:15 computername kernel: [ 3.248707] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
Sep 27 09:37:15 computername kernel: [ 3.269575] nouveau 0000:01:00.0: bios: version 86.07.3e.00.1c
Sep 27 09:37:15 computername kernel: [ 3.269993] nouveau 0000:01:00.0: Direct firmware load for nvidia/gp107/gr/sw_nonctx.bin failed with error -2
Sep 27 09:37:15 computername kernel: [ 3.269995] nouveau 0000:01:00.0: gr: failed to load gr/sw_nonctx
Sep 27 09:37:15 computername kernel: [ 3.269999] nouveau 0000:01:00.0: gr ctor failed, -2
Sep 27 09:37:15 computername kernel: [ 3.270003] nouveau: probe of 0000:01:00.0 failed with error -2

Please see attached "kernel.log.4.12-rc1WithDefaultKernelArguments.log" for details.

[Kai-Heng Feng (kaihengfeng)]

To find the patch that fixes the issue, we need to bisect the kernel. Here's the first one:
http://people.canonical.com/~khfeng/lp1697556/1/

Please check if this freeze or not.

[Hagen Kuehn (hag-k)]

I have tested with kernel 4.11.0-rc1-lp1697556 with the default kernel with the same hardware setup as previously.

Short answer: It works.

Long answer: The login screen is displayed on built in monitor, while the laptop is closed. The login works. Network issues but they are not relevant to this bug.

Please see attached the "4.11.0-rc1-lp1697556.kern.log" kernel log for details. The relevant nouveau section is copied below.

Oct 3 14:48:49 computername kernel: [ 3.175682] nouveau: detected PR support, will not use DSM
Oct 3 14:48:49 computername kernel: [ 3.175693] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
Oct 3 14:48:49 computername kernel: [ 3.175746] nouveau 0000:01:00.0: unknown chipset (137000a1)
Oct 3 14:48:49 computername kernel: [ 3.175764] nouveau: probe of 0000:01:00.0 failed with error -12

[Kai-Heng Feng (kaihengfeng)]

$ git bisect log
git bisect start 'drivers/gpu/drm/nouveau'
# old: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect old a351e9b9fc24e982ec2f0e76379a49826036da12
# new: [2ea659a9ef488125eb46da6eb571de5eae5c43f6] Linux 4.12-rc1
git bisect new 2ea659a9ef488125eb46da6eb571de5eae5c43f6
# new: [6796b129b0e98162a84e0b6322ac28587556d427] Merge branch 'linux-4.12' of git://github.com/skeggsb/linux into drm-next
git bisect new 6796b129b0e98162a84e0b6322ac28587556d427

Please try the new kernel here:
http://people.canonical.com/~khfeng/lp1697556/2/

[Hagen Kuehn (hag-k)]

I have tested with kernel 4.10.0-lp1697556 http://people.canonical.com/~khfeng/lp1697556/2/ with the default kernel parameters and with the same hardware setup as previously.

Short answer: It works.

Long answer: The login screen is displayed on built in monitor, while the laptop is closed. The login works. I am actually writing this response while using this kernel.

Please see attached 4.10.0-lp1697556.kern.log file for details. The nouveau section of the log is pasted below.

Oct 4 17:19:09 quatlap002 kernel: [ 3.165635] nouveau: detected PR support, will not use DSM
Oct 4 17:19:09 quatlap002 kernel: [ 3.165648] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
Oct 4 17:19:09 quatlap002 kernel: [ 3.165704] nouveau 0000:01:00.0: unknown chipset (137000a1)
Oct 4 17:19:09 quatlap002 kernel: [ 3.165723] nouveau: probe of 0000:01:00.0 failed with error -12

[Kai-Heng Feng (kaihengfeng)]

Again, try this:
http://people.canonical.com/~khfeng/lp1697556/3/

$ git bisect log
git bisect start 'drivers/gpu/drm/nouveau'
# old: [a351e9b9fc24e982ec2f0e76379a49826036da12] Linux 4.11
git bisect old a351e9b9fc24e982ec2f0e76379a49826036da12
# new: [2ea659a9ef488125eb46da6eb571de5eae5c43f6] Linux 4.12-rc1
git bisect new 2ea659a9ef488125eb46da6eb571de5eae5c43f6
# new: [6796b129b0e98162a84e0b6322ac28587556d427] Merge branch 'linux-4.12' of git://github.com/skeggsb/linux into drm-next
git bisect new 6796b129b0e98162a84e0b6322ac28587556d427
# new: [6ac2cc209e0096dabc8e902a8620d45f41b9fc0b] drm/nouveau/falcon: support for EMEM
git bisect new 6ac2cc209e0096dabc8e902a8620d45f41b9fc0b

[Hagen Kuehn (hag-k)]

I have tested with provided kernel at http://people.canonical.com/~khfeng/lp1697556/3/
The test setup was the same as previously.

Short answer: It does not work.

Long answer: I can see the icon circling for a while. While this happens I cannot toggle between the boot text output and the circling icon, by using the ESC button. After a while (guess a minute or so), the screen turns black and displays:

BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)_

Also note that I was not able to find any logs concerning this attempted boot. The kern.log file didn't have a single line concerning this boot attempt.

[Kai-Heng Feng (kaihengfeng)]

Hagen,

That means there are some kernel commits that prevent kernel from booting.
Unless you want to do a bisect in the current bisection, otherwise I would suggest move to 4.13 based Artful (17.10) kernel. The Artful release is imminent.

[Anmar Oueja (anmar)]

I agree with Kai-Heng. 17.04 is getting old and given all the good
work that went into the 17.10 release, I recommend you switch to it
Hagen.

BTW, in 17.10, there is a problem on the XPS 15
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718936) booting
from live CD and general use. You need nouveau.modeset=0 to the kernel
boot options.

On Sat, Oct 14, 2017 at 3:15 AM, Kai-Heng Feng
<email address hidden> wrote:
> Hagen,
>
> That means there are some kernel commits that prevent kernel from booting.
> Unless you want to do a bisect in the current bisection, otherwise I would suggest move to 4.13 based Artful (17.10) kernel. The Artful release is imminent.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1697556
>
> Title:
> Computer freezes after login - 4.10.0-22-generic
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
> Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
> ago. Login worked fine too.
>
> A couple of days later I installed the suggested kernel update
> "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
> freezes right after login (i.e. after pressing enter, the background
> image with the mouse is shown, no responses to any key strokes).
>
> Syslog excerpt:
>
> Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
> Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf intel_lpss_pci intel_pch_thermal
> Jun 12 22:12:48 computername kernel: [ 47.603422] hci_uart btbcm btqca btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid pinctrl_sunrisepoint video wmi pinctrl_intel fjes
> Jun 12 22:12:48 computername kernel: [ 47.603453] CPU: 1 PID: 1672 Comm: Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
> Jun 12...

[Marco Scavazzon (marco-skv)]

Hi Anmar & Kai-Heng,

this issue affects 16.04 LTS too, and right now the only workaround is to run the good old 4.8 (and skip all the 4.10 upgrades).
When do you think 4.13 will be ported in 16.04? Thanks!

[Hagen Kuehn (hag-k)]

@Kai-Heng Feng and @Anmar Queja

I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0 kernel
boot option.

It works perfectly. I can indeed see many improvement. Most and foremost Wayland is working as far as I can see!

The only hiccup I had was with the laptop suspending right after the successful login, when the laptop lid was closed while being connected to the Dell Thunderbolt dock – TB16. In contrast to previous Ubuntu version there is no way of configuring the laptop lid behaviour by using the GUI (via Power configuration).

Below setting made the trick.
vim ~/etc/systemd/logind.conf
---
HandleLidSwitchDocked=ignore
---

In the light of this I believe this addressed by upgrading to 17.10 and thus can be closed.

@Marco Scavazzon I believe you should create a new bug and reference this bug in order to get kernel 4.13.0-16 ported to Ubuntu 16.04 LTS.

@All Ubuntu kernel develops
A great thank you to you all of you for making Ubuntu 17.04 so nicely work with Wayland and with Dell XPS 15 (9560)!!

[Hagen Kuehn (hag-k)]

This is a re-write of my previous response, as I should have reviewed it before submitting. I have simply been too excited! ;-)

@Kai-Heng Feng and @Anmar Queja

I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0 kernel boot option.

It works perfectly. I can indeed see many improvements. Most and foremost Wayland is working as far as I can see!

The only hiccup I had was with the laptop suspending right after a successful login, when the laptop lid was closed while being connected to the Dell Thunderbolt dock – TB16. In contrast to previous Ubuntu version there is no way of configuring the laptop lid closed behaviour by using the GUI (via Power configuration).

Below setting made the trick.
vim ~/etc/systemd/logind.conf
---
HandleLidSwitchDocked=ignore
---

In the light of this I believe this bug is addressed by upgrading to 17.10 and therefore this bug can be closed.

@Marco Scavazzon I believe you should create a new bug and reference this bug in order to get kernel 4.13.0-16 ported to Ubuntu 16.04 LTS.

@All Ubuntu kernel developer
A great thank you to you all for your efforts of making Ubuntu 17.04 so nicely work with Wayland and with Dell XPS 15 (9560)!!

[Anmar Oueja (anmar)]

Hopefully future kernel releases don't need the nouveau.modeset=0
option. But until then, 17.10 is rock solid (been full time on it for
the past 3+ weeks) without issues. Kudos to the Ubuntu and Canonical
teams for doing such a great job.

On Fri, Oct 20, 2017 at 7:15 AM, Hagen Kuehn <email address hidden> wrote:
> This is a re-write of my previous response, as I should have reviewed it
> before submitting. I have simply been too excited! ;-)
>
> @Kai-Heng Feng and @Anmar Queja
>
> I have upgraded to Ubuntu 17.10 and used the suggested nouveau.modeset=0
> kernel boot option.
>
> It works perfectly. I can indeed see many improvements. Most and
> foremost Wayland is working as far as I can see!
>
> The only hiccup I had was with the laptop suspending right after a
> successful login, when the laptop lid was closed while being connected
> to the Dell Thunderbolt dock – TB16. In contrast to previous Ubuntu
> version there is no way of configuring the laptop lid closed behaviour
> by using the GUI (via Power configuration).
>
> Below setting made the trick.
> vim ~/etc/systemd/logind.conf
> ---
> HandleLidSwitchDocked=ignore
> ---
>
> In the light of this I believe this bug is addressed by upgrading to
> 17.10 and therefore this bug can be closed.
>
> @Marco Scavazzon I believe you should create a new bug and reference
> this bug in order to get kernel 4.13.0-16 ported to Ubuntu 16.04 LTS.
>
> @All Ubuntu kernel developer
> A great thank you to you all for your efforts of making Ubuntu 17.04 so nicely work with Wayland and with Dell XPS 15 (9560)!!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1697556
>
> Title:
> Computer freezes after login - 4.10.0-22-generic
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
> Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
> ago. Login worked fine too.
>
> A couple of days later I installed the suggested kernel update
> "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
> freezes right after login (i.e. after pressing enter, the background
> image with the mouse is shown, no responses to any key strokes).
>
> Syslog excerpt:
>
> Jun 12 22:12:48 computername kernel: [ 47.603358] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
> Jun 12 22:12:48 computername kernel: [ 47.603360] Modules linked in: ccm msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd...