[Bug 1007928] Re: LZMA data is corrupt trigger to kernel panic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1007928

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1007928

Title:
  LZMA data is corrupt trigger to kernel panic

Status in “casper” package in Ubuntu:
  New

Bug description:
  Release of Ubuntu: 12.04 amd64 build 20120602
  Package Version:
  Expected Results: 
  Actual Results: kernel panic just before plymouth.
  disabling plymouth don't solve.
  The errors:
  -LZMA data is corrupt
  -VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
  -Please append a correct "root=" bot option; here are the available partitions:
  -Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
  -Pid: 1, comm: swapper/0 not tainted 3.4.0-3-generic #8-Ubuntu
  -Call Trace:
  -[<ffffffff8166d16b>] panic+0xba/0x1c6
  -[<ffffffff81cf6033>] mount_block_root+0x1d6/0x287
  -[<ffffffff81cf627d>] mount_root+0x57/0x5b
  -[<ffffffff81cf63ee>] prepare_namespace+0x16d/0x1a6
  -[<ffffffff81079480>] ? release_tgcred.isra.4+0x30/0x30
  -[<ffffffff81cf5d99>] kernel_init+0x1ba/0x1bf
  -[<ffffffff81cf5bdf<] ? start_kernel+0x3ce/0x3ce
  -[<ffffffff81683320<] ? gs_change+0x13/0x13

  Thanks
  Fabio

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