@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 probably i915 related too, that the external keyboard only worked after the USB dongle was removed and re-connected to the docking station. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
