A few days ago, I let update-manager upgrade my kernel from 4.18.0-13 to 4.18.0-14. Since then, my system is unable to boot. It freezes after printing
fb: switching to inteldrmfb from VESA VGA
but before it gets around to asking me the passphrase for my encrypted main partition. (At first I thought it was a problem with cryptsetup because it never got to that prompt, but now I'm pretty sure it's something to do with changing video mode.)
However, if I use the grub menu to select the older 4.18.0-13, the system boots just fine. It looks very much like a bug introduced between 4.18.0-13 and 4.18.0-14.
Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel modesetting does not happen, and the system boots just fine. (Except for the 1980s-style low-res video, that is.) This seems like good evidence that it's a problem with setting the video mode.
I'll test with some mainline builds, but I want to get this bug report opened before I start rebooting.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.10
HibernationDevice: RESUME=UUID=fb24f9f1-0e89-4ef6-a88a-fb9fc5d776c7
InstallationDate: Installed on 2018-09-05 (155 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IwConfig:
enp2s0 no wireless extensions.
lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/lubuntu--vg-root ro
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.18.0-14-generic N/A
linux-backports-modules-4.18.0-14-generic N/A
linux-firmware 1.175.1
RfKill:
Tags: cosmic
Uname: Linux 4.18.0-14-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2019-01-23 (16 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7H55-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
Results with mainline kernels:
* linux-image-
* linux-image-
One other interesting factoid: after the failed modeset, the system isn't _completely_ dead. I can type in my passphrase for my encrypted partition, and after another 10-12 s (the usual delay) the system is ping'able and ssh'able. So stuff is up and running. But here's what does not work:
* software reboot from console (Ctrl-Alt-F1, then Ctrl-Alt-Del)
* "sudo reboot" from ssh session
* "sudo poweroff" from ssh session
The only ways I can regain control are the PC reset button or hardware power off.