Kernel panic (kernel 3.13.0-27-generic) on ASUS UX31A

[annnomius]

Kernel version 3.13.0-27-generic causes a kernel panic on bootup.
This does not occur with the prior kernel: 3.13.0-24-generic, nor does it occur with recent mainline: 3.15.0-031500rc8-generic_3.15.0-031500rc8.201406012235_amd64

Since this is a panic, I cannot run ubuntu-bug, uname, etc. However, the output of lspci is attached.

The panic message (painstakingly hand-copied):
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 3.13.0-27-generic #50-Ubuntu
Hardware name: ASUSTeK COMPUTER INC. UX31A/UX31A, BIOS UX31A.216 11/21/2012
0000000000008001 ffff880118f1bdf0 ffffffff817199c4 ffffffff81a3b5d0
ffff880118f1be68 ffffffff81712bc5 ffffffff00000010 ffff880118f1be78
ffff880118f1be18 ffffffff817136e6 ffff880118f1be88 00000000000000cc
Call trace:
<ffffffff817199c4> dump_stack+0x45/0x56
<ffffffff81712bc5> panic+0xc8/0x1d7
<ffffffff817136e6> ? printk+0x67/0x69
<ffffffff81d3646a> mount_block_root+0x225/0x2b0
<ffffffff81d36692> mount_root+0x53/0x56
<ffffffff81d36801> prepare_namespace+0x16c/0x1a4
<ffffffff81d3616e> kernel_init_freeable+0x1f3/0x200
<ffffffff81d358e5> ? do_early_param+0x88/0x88
<ffffffff81707ea0> ? rest_init+0x80/0x80
<ffffffff81707eae> kernel_init+0xe/0x130
<ffffffff8172a2fc> ret_from_fork+0x7c/0xb0
<ffffffff81707ea0> ? rest_init+0x80/0x80

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1326216

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.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.13.11.2-trusty/

[Joseph Salisbury (jsalisbury)]

If the bug still exists in 3.13.11.2, we can either perform a "Reverse" bisect to find the commit that fixes this in upstream 3.15 or we can perform a bisect to find the commit that introduced this in 3.13.

[roemer2201 (roemer2201)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-24-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
CurrentDmesg: [ 39.240977] init: plymouth-upstart-bridge main process ended, respawning
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-26 (39 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
IwConfig:
 tun0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
Package: linux (not installed)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8282ba3f-5f41-45e6-b9ef-4295c61b70e9 ro
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.2
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 04/14/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LF94510J.86A.0278.2010.0414.2000
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D945GCLF2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE46416-103
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0278.2010.0414.2000:bd04/14/2010:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF2:rvrAAE46416-103:cvn:ct3:cvr:

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

apport information

[roemer2201 (roemer2201)]

I was able to boot an older kernel and then I ran:

sudo apport-collect 1326216

I hope the flood of files to this bug is not too big. I had not known this command, until I found this page.

[roemer2201 (roemer2201)]

I'd like to add that this happens to me on the Intel D945GCLF2 mainboard with a preinstalled intel atom cpu.

[annnomius (annnomius)]

Marking as confirmed per jsalisbury's instructions.
The bug does NOT exist in 3.13.11.2, specifically linux-image-3.13.11-03131102-generic_3.13.11-03131102.201405081435_amd64

I suppose it would be possible to do a bisect, but doesn't the backtrace provide enough information to debug this?

::ann

[Joseph Salisbury (jsalisbury)]

That is good news that this is fixed in upstream 3.13.11.2. That means this bug will be fixed in Trusty when it gets the 3.13.11.2 updates in the next kernel release.

[penalvch (penalvch)]

annnomius, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise if this is reproducible?

roemer2201, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[annnomius (annnomius)]

I loaded the daily-live cdimage "utopic-desktop-amd64.iso" (dated May 20) on a USB stick, and booted with that.
since the kernel version on that is 3.13.0-24-generic, there was of course no problem with booting. the problem is with the next kernel in line, 3.13.0-27.

so long as the utopic team stays on 3.13.0-24, you should be fine :-)

[penalvch (penalvch)]

annomius, there would be a contradiction between the kernel you found in the live environment, and the one that is supposed to be there as per https://launchpad.net/ubuntu/+source/linux .

Despite this, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[annnomius (annnomius)]

Christopher,

not sure why you say there is a contradiction--the live kernel I found on the iso was 3.13.0-24, and the linux-image listed on the page you provided is also 3.13.0-24. again, if utopic avoids 3.13.0-27, they should be fine.

regarding reverse bisect--it looks like this may not be necessary, because there was apparently a recent update to the kernel--my system now has 3.13.0-29 on it, and that does NOT panic.

so: 3.13.0-24 is fine, 3.13.0-29 is fine, but 3.13.0-27 is bad. this, along with the panic backtrace, should hopefully be sufficient for the ubuntu developers to identify the bad code, and ensure it does not appear in any future ubuntu releases.

::ann

[penalvch (penalvch)]

annnomius, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326216/comments/25 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.