kernel-packages team mailing list archive

[annnomius <annnomius@xxxxxxxxx>]

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

** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1326216

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

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326216/+subscriptions