That all those kernels are working now was a bit suspicious to me. I did upgrade yesterday my system which also involved an issue: The vboxdrv (VirtualBox) kernel module couldn't be loaded anymore because of a format error or such. Since a downgrade from version 5.2.14 to version 5.2.12 of VirtualBox did not solve the issue and it looked like that the upgrade also made GCC 8 a default my guess was that the compilation of the vboxdrv kernel module with GCC 8 caused this incompatibility either due to a GCC bug or my kernel being too old. I also noticed that my boot time was some seconds faster due to vboxdrv not being loaded at boot.
To make sure this issue is not related to the kernel panic at boot I tested the mainline kernel 4.18 RC5 again but it didn't panic now on boot. On testing then linux-image-4.17.0-5-generic from the Ubuntu repository it did also boot without a kernel panic and after 8 months of being haunted by kernel panics at boot I have finally an up-to-date working kernel again (also vboxdrv is being loaded successfully and VirtualBox works). My guess is that kernel versions after linux-image-4.13.0-15-generic with virtualbox-dkms being installed and its vboxdrv compiled via GCC 7.3.0 caused this issue. I'm not sure which of the 3 candidates is to blame here but the combination of linux-image-4.17.0-5-generic with virtualbox-dkms with its vboxdrv compiled via GCC 8.1.0 works fine so it appears there is no remaining issue (at least for cosmic except somebody compiles vboxdrv with GCC 7 as I guess the kernel does panic then again). -- 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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F.... pulseaudio /dev/snd/controlC0: sworddragon 1521 F.... pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+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
