Kernel panic - not syncing:Fatal exception in interrupt

Bug #1475941 reported by Fibonacci
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

I've just installed Kubuntu 15.04 and was able to boot into it once and update the kernel. Since then, everytime I try to boot into it I get the following error message:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

There might be other error messages before but I cannot see them as they pass too fast, and the only messages I see are those shown in the attached picture.

After some trial and error, I've discovered that this bug occurs when booting with the quiet option. When I remove it, the kernel boots fine most of the time (not everytime, but it's a definite improvement).

What's happening and how do I prevent it?

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-22-generic 3.19.0-22.22
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: fibonacci 1816 F.... pulseaudio
 /dev/snd/pcmC0D0p: fibonacci 1816 F...m pulseaudio
 /dev/snd/controlC0: fibonacci 1816 F.... pulseaudio
CurrentDesktop: KDE
Date: Sat Jul 18 20:28:31 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7e89a62d-4e77-40fc-89ba-42c3b1e76fc0
InstallationDate: Installed on 2015-07-13 (5 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-22-generic root=UUID=0e051a2e-be67-40a6-8d32-29d4de69aca1 ro rootflags=subvol=@ splash
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-22-generic N/A
 linux-backports-modules-3.19.0-22-generic N/A
 linux-firmware 1.143.1
RfKill:

SourcePackage: linux
UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-206
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-206:cvn:ct3:cvr:

Revision history for this message
Fibonacci (fibonacci-prower) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Kernel panic - not syncing (clean 15.10 install)

The 15.10 kernel has been rebased to v4.0. Can you get the system to boot, then apply the latest updates and see if this bug still exists?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Revision history for this message
Fibonacci (fibonacci-prower) wrote :

If you mean 15.04 then yes, it still exists.

Revision history for this message
Erik Zoltan (erikzoltan) wrote :

I have a 64-bit System76 computer and this problem also affects me. My kernel is 3.19.0-22-generic. I am using factory-installed Ubuntu 15.04, but I've been running updates regularly.

I can still boot my original 3.19.0-21-generic kernel just fine, and do my work on that kernel without any problems.

Revision history for this message
Erik Zoltan (erikzoltan) wrote :

Correction: on further review my problem seems to be slightly different, and I will log it separately.

Revision history for this message
penalvch (penalvch) wrote : Re: Kernel panic - not syncing

Fibonacci, are you able to boot into a prior kernel version via GRUB that doesn't demonstrate this problem?

tags: added: latest-bios-0160
summary: - Kernel panic - not syncing (clean 15.10 install)
+ Kernel panic - not syncing
description: updated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Fibonacci (fibonacci-prower) wrote :

Not at all. This is a clean install so the earliest kernel version is 3.19.0-15 which has this bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Fibonacci (fibonacci-prower) wrote :

I've installed kernel 3.19.0-25, and now it's not enough to remove the quiet option even in 3.19.0-22. I have to manually edit the grub menu entry at boot time (writing it on grub.cfg doesn't work) and replace the following lines:

                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7 0e051a2e-be67-40a6-8d32-29d4de69aca1
                else
                  search --no-floppy --fs-uuid --set=root 0e051a2e-be67-40a6-8d32-29d4de69aca1
                fi

with this:

                  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos7 --hint-efi=hd0,msdos7 --hint-baremetal=ahci0,msdos7 0e051a2e-be67-40a6-8d32-29d4de69aca1

That is true also for the newest kernel – if I don't do that, I get the kernel panic message I described before.

Revision history for this message
Erik Zoltan (erikzoltan) wrote :

I am attaching a screen shot of my problem because it looks so similar and I haven't had any luck in solving it. I can still boot with the Linux 3.19.0-21-generic kernel from the Grub menu. However the more recent versions (22 through 25) are not booting. I am not sure how to tell for certain but it looks more and more like the same kind of problem.

Simon (makadas-class19d)
summary: - Kernel panic - not syncing
+ Kernel panic - not syncing:Fatal exception in interrupt
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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