Kernel panic during boot 3.11.0-15-generic

[Nikolay Turpitko]

I've updated to 3.11.0-15-generic via aptitude and tried to reboot. During boot I've got a kernel panic with messages:
uncompression error
UFS: cannot open root device "..." or unknown-block(0,0): error -6
Please append a correct "root=" boot option

Previous version (3.11.0-14-generic) works on the same notebook, with the same BIOS settings. I can boot into it using corresponding GRAB option. Actually, I reported this bug using "ubuntu-bug linux" when loaded into previous version.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nick 2190 F.... pulseaudio
 /dev/snd/pcmC0D0p: nick 2190 F...m pulseaudio
Date: Sat Jan 4 12:47:07 2014
InstallationDate: Installed on 2013-04-27 (251 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. N76VJ
MarkForUpload: True
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=6aa7ef52-c41f-4856-950a-bef3ba7b78e5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-23 (73 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.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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

v3.11.8: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.8-saucy/
v3.11.9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.9-saucy/
v3.11.10: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10-saucy/

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

Thanks in advance!

[Nikolay Turpitko (nikolay-w)]

All 3 kernels work like a charm.

[Nikolay Turpitko (nikolay-w)]

Kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.1-saucy/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.2-saucy/
work as well.

[Joseph Salisbury (jsalisbury)]

Thanks for testing, that might indicate an Ubuntu specific SAUCE patch that introduced this bug. However, I don't see anything specific that stands out in the changelog. Can you give the latest kernel in proposed a test:

https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/5318479

[Nikolay Turpitko (nikolay-w)]

sudo add-apt-repository ppa:canonical-kernel-team/ppa
sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot now

nick@tnl-N76VJ:~$ uname -r
3.11.0-16-generic

Probably not exactly the build you pointed to, but latest for the moment from ppa, does work.

So, it seems that I'll get working stock kernel with next stable release?

[Joseph Salisbury (jsalisbury)]

That is good news. Yes, the fix will be coming in the next stable release.