Kernel panic at boot

Bug #1780466 reported by Sworddragon on 2018-07-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned
Bionic
High
Unassigned
Cosmic
High
Unassigned

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.

description: updated

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 1780466

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: cosmic

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc5

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
tags: added: kernel-key
Sworddragon (sworddragon) wrote :

At the current time kernel.ubuntu.com has no https availability (it times out) and downloading those packages over http is very insecure. I hope https becomes available soon so I can test this kernel.

Sworddragon (sworddragon) wrote :

Edit: I checked the uncompromisedness via GPG - as I do not want to risk waiting a very long time until the https issue is solved. The kernel still panics at boot and claims this time about a tick-broadcast.c:652.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu Cosmic):
status: Triaged → Confirmed
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the last kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

4.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
4.14-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4/
4.14 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

Changed in linux (Ubuntu Bionic):
status: New → Confirmed
importance: Undecided → High
Sworddragon (sworddragon) wrote :

I have tested all those 4 kernels (amd64; generic) but none of them causes a kernel panic at boot.

Sworddragon (sworddragon) wrote :

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).

Joseph Salisbury (jsalisbury) wrote :

I'll mark this bug as incomplete for now. Just move it back to confirmed if the panic starts happening again.

Changed in linux (Ubuntu Cosmic):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Bionic):
status: Confirmed → Incomplete
tags: added: kernel-da-key
removed: kernel-key
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Bionic):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Cosmic):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers