Ubuntu
linux package

Kernel panic - not syncing: VFS: Unable to mount root fs

Bug #1380881 reported by Nikolay Turpitko on 2014-10-14

14

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	High	Unassigned

Bug Description

I've recently updated to the kernel 3.13.0-37 from the main repository and got this issue again (I had similar issue before with 3.11.0-15, see Bug #1265971). I tried to update to 3.13.0-38 from ppa:canonical-kernel-team/ppa, but the issue remains.

I'm not sure, but suspect that it's related to my SanDisk SSD U100 drive, another my notebook upgraded without any problem.

I'm reportin this bug booting from the previous kernel, so automatically gathered kernel version info isn't actual.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-36-generic 3.13.0-36.63
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: nick 1961 F.... pulseaudio
Date: Tue Oct 14 10:19:38 2014
InstallationDate: Installed on 2013-04-27 (534 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. N76VJ
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=6aa7ef52-c41f-4856-950a-bef3ba7b78e5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.13.0-36-generic N/A
linux-backports-modules-3.13.0-36-generic N/A
linux-firmware 1.127.7
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-19 (177 days ago)
dmi.bios.date: 07/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N76VJ.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N76VJ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN76VJ.203:bd07/09/2013:svnASUSTeKCOMPUTERINC.:pnN76VJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N76VJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Tags:

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#1

BSOD of 3.13.0-37 in recovery mode Edit (2.6 MiB, image/jpeg)
AlsaInfo.txt Edit (30.8 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (94.6 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (286 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (10.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (595 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.8 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (15.2 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (189 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (175.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (395.7 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (23.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#2

BSOD 3.13.0-38 Edit (2.6 MiB, image/jpeg)

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#3

BSOD 3.13.0-38 in recovery mode Edit (2.7 MiB, image/jpeg)

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#4

lshw output Edit (19.1 KiB, text/plain)

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#5

/etc/mtab content Edit (1.6 KiB, text/plain)

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-14:

#6

/etc/fstab content Edit (990 bytes, text/plain)

Revision history for this message

Brad Figg (brad-figg) wrote on 2014-10-14: Status changed to Confirmed

#7

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-18:

#8

This kernel works: /~kernel-ppa/mainline/v3.13.11.9-trusty

$ uname -a
$ Linux tnl-N76VJ 3.13.11-03131109-generic #201410141735 SMP Tue Oct 14 21:37:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Joseph Salisbury (jsalisbury) on 2014-10-21

Changed in linux (Ubuntu):
importance:	Undecided → High
tags:	added: kernel-da-key regression-update

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-10-21:

#9

It's good that 3.13.11.9 fixes the issue. That version will make it into Trusty through the normal stable update process. Can you also test the latest kernel in -proposed, which is -38? It currently has the 3.13.11.8 upstream kernel.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-22:

#10

Strangely for me, when I re-installed kernel packages from -proposed above the same versions from ppa:canonical-kernel-team/ppa, they do work (I rebooted system several times hot and cold):

$ uname -a
Linux tnl-N76VJ 3.13.0-38-generic #65-Ubuntu SMP Thu Oct 9 11:36:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Results from ppa were BSOD screenshots attached in comments #2 and #3.

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2014-10-22:

#11

That may indicate that the fix for this has already made it's way into the -proposed repository.

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-30:

#12

BSOD - 3.13.0-39-generic #66 Edit (1.1 MiB, image/jpeg)

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-30:

#13

The same issue again with new kernel from repository (3.13.0-39-generic #66-Ubuntu). See attachment above.

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2014-10-30:

#14

This one works: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc2-vivid/

uname -a
Linux tnl-N76VJ 3.18.0-031800rc2-generic #201410281737 SMP Tue Oct 28 21:38:57 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Please provide me with a list of kernels I should try, if you think it may help.

Revision history for this message

Kevin Zhang (whitehat2k9) wrote on 2015-02-13:

#15

Just encountered this bug for the first time on latest kernel 3.13.0-45-generic; booting 3.13.0-44-generic works. System is running as a guest inside VMWare Workstation 11.

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2015-02-14:

#16

Well, just for information, 3.13.0-45-generic works fine for me (and 3.13.0-44 wasn't):
uname -a
Linux tnl-N76VJ 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Fibonacci (fibonacci-prower) wrote on 2015-07-19:

#17

Does this bug still affect any of you?

If so, what happens if you remove the quiet option from GRUB?

Revision history for this message

Nikolay Turpitko (nikolay-w) wrote on 2015-07-20:

#18

No, I've updated several times since then, all updates went smooth.
I'm on 3.13.0-57-generic now and it also works fine.
Probably, it's safe to close this bug.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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