Ubuntu
linux package

ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44

Bug #1813745 reported by Stéphane Guillard
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up.

The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard.

4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver:

[ 47.320244] ------------[ cut here ]------------
[ 47.320245] Unknown pixelformat 0x00000000
[ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev]
[ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp
[ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone
[ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint
[ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu
[ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018
[ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev]
[ 47.320350] RSP: 0018:ffffa8cc4530bc30 EFLAGS: 00010282
[ 47.320351] RAX: 0000000000000000 RBX: ffffa8cc4530bd68 RCX: 0000000000000006
[ 47.320352] RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff8c8d6e496490
[ 47.320352] RBP: ffffa8cc4530bc40 R08: 0000000000000001 R09: 00000000000004c7
[ 47.320353] R10: ffff8c8d5abe2d00 R11: 0000000000000000 R12: ffff8c8cda86c500
[ 47.320353] R13: ffffffffc11bc900 R14: ffff8c8d5abe2d80 R15: ffff8c8cda86c500
[ 47.320354] FS: 00007f9ad4ff9700(0000) GS:ffff8c8d6e480000(0000) knlGS:0000000000000000
[ 47.320355] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 47.320355] CR2: 00007ff9f0083905 CR3: 000000043fd80006 CR4: 00000000003606e0
[ 47.320356] Call Trace:
[ 47.320360] v4l_enum_fmt+0x74/0x110 [videodev]
[ 47.320362] __video_do_ioctl+0x370/0x380 [videodev]
[ 47.320364] ? terminate_walk+0x8e/0xf0
[ 47.320366] ? aa_path_perm+0xe2/0x130
[ 47.320367] ? aa_path_perm+0xf6/0x130
[ 47.320370] video_usercopy+0x24d/0x640 [videodev]
[ 47.320372] ? video_ioctl2+0x20/0x20 [videodev]
[ 47.320374] video_ioctl2+0x15/0x20 [videodev]
[ 47.320376] v4l2_ioctl+0xc8/0xf0 [videodev]
[ 47.320378] do_vfs_ioctl+0xa8/0x630
[ 47.320380] ? kmem_cache_free+0x1b3/0x1e0
[ 47.320381] ? putname+0x4c/0x60
[ 47.320382] ? do_sys_open+0x13e/0x2c0
[ 47.320383] SyS_ioctl+0x79/0x90
[ 47.320385] do_syscall_64+0x73/0x130
[ 47.320388] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 47.320389] RIP: 0033:0x7f9b28b15f47
[ 47.320389] RSP: 002b:00007f9ad4ff8318 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 47.320390] RAX: ffffffffffffffda RBX: 00007f9ad4ff8340 RCX: 00007f9b28b15f47
[ 47.320391] RDX: 00007f9ad4ff8500 RSI: 00000000c0405602 RDI: 000000000000006f
[ 47.320391] RBP: 0000000080685600 R08: 00007f9aa00007c8 R09: 00007f9aa000b700
[ 47.320392] R10: 00007f9aa00033ba R11: 0000000000000246 R12: 00007f9ad4ff8348
[ 47.320392] R13: 00007f9ad4ff8400 R14: 000000000000006f R15: 00007f9ad4ff8498
[ 47.320393] Code: 30 0f 84 b4 01 00 00 3d 4a 4c 32 30 0f 84 97 01 00 00 3d 4d 33 31 30 0f 84 7a 01 00 00 89 c6 48 c7 c7 d7 d2 17 c1 e8 9f 37 12 f3 <0f> 0b 80 7b 0c 00 0f 85 e2 f3 ff ff 8b 43 2c 48 c7 c1 7e c6 17
[ 47.320411] ---[ end trace 346dbacffbe49497 ]---

Additional information:

$ cat /proc/version_signature
Ubuntu 4.15.0-43.46-generic 4.15.18

$ sudo lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02)
39:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02)
6e:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0116
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stephane 3144 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=fd05e430-a59c-44f8-ba34-cf4fb4dc24ab
InstallationDate: Installed on 2018-08-28 (153 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
MachineType: Dell Inc. XPS 13 9370
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=08a9b4cf-cf80-4612-b403-ce3be56ec699 ro locale=fr_FR
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic N/A
 linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-28 (153 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 11/04/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.3
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.sys.vendor: Dell Inc.

See original description
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1813745

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Stéphane Guillard (sg2) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Stéphane Guillard (sg2) wrote : CRDA.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : IwConfig.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : Lspci.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : Lsusb.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : ProcModules.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : PulseList.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : RfKill.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : UdevDb.txt

apport information

Revision history for this message
Stéphane Guillard (sg2) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Stéphane Guillard (sg2) wrote :

Note that all apport attachments above were done running 4.15.0-43 kernel and not the problematic 4.15.0-44, with which I cannot boot to login.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test this kernel:
https://people.canonical.com/~khfeng/lp1813663/

This commit is reverted in the test kernel:
"drm/i915/dp: Send DPCD ON for MST before phy_up"

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Should be the same as LP: #1813663.

Revision history for this message
Stéphane Guillard (sg2) wrote :

What is the procedure to test this kernel? (I normally get & install kernels through Ubuntu software update, and have never installed one from the shell)

Also, in case of GUI hang during boot (as is the case with 4-15-0-44), is there a way to reboot the machine without thrashing the root filesystem?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Download the .deb files to an empty directory, then open terminal,
$ cd $(the directory)
$ sudo dpkg -i *deb

Then reboot.

> Also, in case of GUI hang during boot (as is the case with 4-15-0-44), is there a way to reboot the machine without thrashing the root filesystem?

Use magic key [1]. Press Alt + PrintScreen without releasing, then press 'S' 'U' 'B' or 'S' 'U' 'O'.

[1] https://en.wikipedia.org/wiki/Magic_SysRq_key

Revision history for this message
Martin Büchler (mbm0811) wrote :

If you see the grub menu on boot, just select an older kernel... but:

The update to 4.15.0-44 additionally broke my grub config, with the effect, that I could not even select an older kernel from grub menu, since the update has set it to 'hidden'. I had to revert manually in /etc/default/grub:

- GRUB_TIMEOUT_STYLE=hidden
+ GRUB_TIMEOUT_STYLE=menu

followed by a 'sudo grub-update'.

Revision history for this message
Stéphane Guillard (sg2) wrote :

Same

Revision history for this message
Stéphane Guillard (sg2) wrote : Re: [Bug 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44

Done.

This fixes the issue, I can safely boot and login to desktop using
4.15.0-45.

Cordialement,
--
Stéphane GUILLARD

Le 29/01/2019 à 12:16, Kai-Heng Feng a écrit :
> Download the .deb files to an empty directory, then open terminal,
> $ cd $(the directory)
> $ sudo dpkg -i *deb
>
> Then reboot.
>
>> Also, in case of GUI hang during boot (as is the case with 4-15-0-44),
> is there a way to reboot the machine without thrashing the root
> filesystem?
>
> Use magic key [1]. Press Alt + PrintScreen without releasing, then press
> 'S' 'U' 'B' or 'S' 'U' 'O'.
>
> [1] https://en.wikipedia.org/wiki/Magic_SysRq_key
>

Revision history for this message
Stéphane Guillard (sg2) wrote :

I installed the 4.15.0-45 test kernel at https://people.canonical.com/~khfeng/lp1813663/

This fixes the issue, I can safely boot and login.

Thank you Kai-Heng.

Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

Per previous comments, I'm going to duplicate this report against bug 1813663. Thank you!

Revision history for this message
Tomas Jonsson (tomas-jonsson) wrote :

I can also confirm that the test kernel located at https://people.canonical.com/~khfeng/lp1813663/ fixed my issues as well.

Revision history for this message
TJ (tj) wrote :

Upstream commit ID is be1c63c8017bb00a4

Revision history for this message
Stéphane Guillard (sg2) wrote :

Kai,

Your test kernel fixes my issue, but the official -45 released today
still crashes at boot.

So the official -45 kernel does not include your fix, or includes it
with other breaking changes.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you attach `dpkg -l | grep linux`? Maybe some packages are not correctly installed.

Revision history for this message
Stéphane Guillard (sg2) wrote :

Hi Kai,

I (the original bug reporter) have the same issue on my Dell 9370:

- 4.15.0-43 boots fine

- 4.15.0-44 hangs at or before login GUI

- your 4.0.15-45 test kernel boots fine

- the official 4.0.15-45 signed kernel made available on software update
the day after your test kernel hangs at or before GUI

So I have reverted to 4.15.0-43; the bug is in fact not fixed in the
official 4.0.15-45. What is probably misleading is that my bug was made
a duplicate of another bug related to boot problems with second screen
or dock stations; which in fact turns out to be a different problem,
appearently fixed by the official -45 kernel.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Is it possible to boot under -45, reboot to -43, then attach output of `journalctl -b -1 -k`?

Revision history for this message
Rodney (hp35) wrote :

4.15.0-45 does not fix my problem. The boot continues to hang when gnome tries to start. I cannot "Ctrl-Alt-F1 (or any F?)", but I can ssh from another computer to this affected computer. Log files don't show anything remarkable to me, but I wouldn't know what was remarkable in all of the verbiage. The boot process was working fine in the week of Jan 28 2019 through, oh say Jan 31.

The only way I can boot is tell grub to boot to 4.15.0-45-generic (recovery mode). The system comes up, but my display is affected. I have:

Acer Aspire R15
Processor: Intel Core I5-7200 CPU @ 2.50Gz x 4
Graphics: Intel HD Graphics (620 (KabyLake GT2) x86/MMX/SSE2
OS type: 32-bit

but when booted in recovery mode, it shows:
Graphics: llvmpipe (llvm 6.0, 256 bits)

uname -a shows:

Linux AcerAspireR15 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:27:25 UTC 2019 i686 i686 i686 GNU/Linux

This is a newly installed system so I cannot revert back to a 4.15.0-43 monitor (I reinstalled when I encountered this problem).

Wanted to let yall know that the 4.15.0-45 update did not fix the problem for every computer. And, I don't know how to install one of the kernels at "https://people.canonical.com/~khfeng/lp1813663/", and wouldn't know which one to install anyway.

Revision history for this message
Stéphane Guillard (sg2) wrote :

Download the .deb files to an empty directory, then open terminal,
$ cd $(the directory)
$ sudo dpkg -i *deb

Revision history for this message
Rodney (hp35) wrote :

Stephane Guilard:

I think that comment was for me -- if so, thanks:

I was able to get 4.15.0-43 installed (another way). That didn't help. It seems something else has happened that they haven't found. I have another computer "Samsung NP300E5C Notebook" that has the "43" and "45" kernels installed on it, on Jan 16 and Feb 2. No "44" on it, and it probably never did. It works fine.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.