[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#706355: linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting



Control: severity -1 important
Control: tag -1 moreinfo

On Mon, 2013-04-29 at 00:36 +0530, S. Roy wrote:
> Package: src:linux
> Version: 3.2.41-2
> Severity: grave
> Justification: renders package unusable
> 
> ----------
> I have upgraded today from Squeeze to Debian-7.0.
> However, while booting in the last 3 occasions, the machine hanged twice
> with kernel Panic.
> 
> In both the occasions, the kernel waited unusually long to load the
> initrd, and then complained about it and then asked to touch any
> key to continue. Once I touched something, it panicked.
> 
> What surprises me is that if it is a initrd problem, why did it boot in
> 2 other occasions ?
> Moreover, I have been using 'vmlinuz-3.2.0-0.bpo.2-amd64' taken from backport
> while using Squeeze, and the machine never hanged in the last 6 months.
> 
> The messages were captured with a camera and I am writing down most of
> it as was visible in the last screen.
> -----------
> No filesystem could mount root. tried:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0, 0)
[...]

This panic is expected if the root filesystem could not be mounted.  So
the question is, why did that fail?  Is the root device a simple
partition or logical volume?  Is the physical device attached by SATA,
USB, or other means?

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: