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

Bug#413456: linux-image-2.6.18-4-686: Does not boot on machine installed with 2.6.18-3-686



Steve Langasek <vorlon@debian.org> wrote:

> severity 413456 important
> tags 413456 moreinfo unreproducible
> thanks
>
> On Mon, Mar 05, 2007 at 09:03:49AM +0100, Frank Küster wrote:
>> It feels bad to open a RC bug on the kernel at this time, and I've
>> thought about it more than once, but *I* do not see a reason to
>> downgrade the severity.  Feel free to do so if you find one ;-)
>
> Reason: so far there's no evidence of a bug in the kernel, just that your
> initrd is broken and not able to set your LVM up correctly.
>
> And I have 2.6.18-4 booting just fine on an LVM system, so I don't think
> this is a kernel bug unless it's an issue of support for your disk
> controller; in which case that's again not RC, we can't treat support for
> individual pieces of hardware as release-critical.

Well, but it is a regression from 2.6.18-3-686.

>> VFS: Cannot open root device "mapper/riesling-root" or unknown-block(0,0)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
>
> This only establishes that the LVM is not present; you'll have to go farther
> back in the boot messages to find out why.

How can I do that?  Should Shift-PageUp still work after the Kernel panic?

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)



Reply to: