ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3

[Alexander Sack]

Hi,

as summary says, today I got an upgrade to gke which broke my 18.04 oem install (dell xps 13)...

After upgrade i had

ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem
ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04 amd64 Signed kernel image GKE

and had to use advanced boot options to get back to a usable setup...

maybe useful:

dpkg -l linux* | grep ^ii
ii linux-base 4.5ubuntu1.2 all Linux image base package
ii linux-firmware 1.173.19 all Firmware for Linux kernel drivers
ii linux-headers-4.15.0-1030-oem 4.15.0-1030.35 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii linux-headers-4.15.0-1091-oem 4.15.0-1091.101 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii linux-headers-4.15.0-1093-oem 4.15.0-1093.103 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii linux-headers-oem 4.15.0.1093.96 amd64 OEM Linux kernel headers
ii linux-image-4.15.0-1030-oem 4.15.0-1030.35 amd64 Signed kernel image oem
ii linux-image-4.15.0-1091-oem 4.15.0-1091.101 amd64 Signed kernel image oem
ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem
ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Signed kernel image GKE
ii linux-image-oem 4.15.0.1093.96 amd64 OEM Linux kernel image
ii linux-libc-dev:amd64 4.15.0-112.113 amd64 Linux Kernel Headers for development
ii linux-libc-dev:i386 4.15.0-112.113 i386 Linux Kernel Headers for development
ii linux-modules-4.15.0-1030-oem 4.15.0-1030.35 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii linux-modules-4.15.0-1091-oem 4.15.0-1091.101 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii linux-modules-4.15.0-1093-oem 4.15.0-1093.103 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP
ii linux-oem 4.15.0.1093.96 amd64 Complete OEM Linux kernel and headers
ii linux-oem-headers-4.15.0-1030 4.15.0-1030.35 all Header files related to Linux kernel version 4.15.0
ii linux-oem-headers-4.15.0-1090 4.15.0-1090.100 all Header files related to Linux kernel version 4.15.0
ii linux-oem-headers-4.15.0-1091 4.15.0-1091.101 all Header files related to Linux kernel version 4.15.0
ii linux-oem-headers-4.15.0-1093 4.15.0-1093.103 all Header files related to Linux kernel version 4.15.0
ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1889080

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.

[Anthony Wong (anthonywong)]

Your system should be using the 4.15 oem kernel and it's not expected to switch to the gke kernel. Did the 5.3 gke kernel mysteriously pushed to you after system upgrade?

[Alexander Sack (asac)]

well obviously it is not supposed to go for gke kernel, but what i am reporting is that my dell xps13 with ubuntu preinstall automatically got this kernel pushed ... same for a coworker who got the same laptop... so yes this bug report is about someone/something wrongfully pusing the gke kernel to my laptop...

[Alexander Sack (asac)]

and no i wont file the log files you asked for as my system is already changed again etc.

i am just here after colin king asked me to file a bug ... so the ubuntu kernel team can check and maybe fix the source of the problem.

[Andy Whitcroft (apw)]

Does this system have wireguard or zfs tooling installed?

[Colin Ian King (colin-king)]

https://twitter.com/asacasa/status/1287692205029765121

[Colin Ian King (colin-king)]

Hi Alexander, in your tweet you mentioned it was "most likely a user mistake though". Can we deduce that this is a genuine issue on upgrade or was because of changes you made that caused this issue?

[Colin Ian King (colin-king)]

(see https://twitter.com/asacasa/status/1287746641815113730 )