From: Christophe Saout <christophe@saout.de>
To: Rik van Riel <riel@redhat.com>
Cc: neel vanan <neelvanan@yahoo.com>,
William Lee Irwin III <wli@holomorphy.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel panic.. in 3.0 Enterprise Linux
Date: Mon, 05 Jan 2004 13:33:41 +0100 [thread overview]
Message-ID: <1073306020.5755.5.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0401050722520.23604-100000@chimarrao.boston.redhat.com>
Am Mo, den 05.01.2004 schrieb Rik van Riel um 13:23:
> On Mon, 5 Jan 2004, Christophe Saout wrote:
> >
> > LABEL= is a RedHat extension. Please use the normal root options that is
> > described in the Grub or kernel documentation.
>
> It's not even a Red Hat extension. The LABEL= stuff is
> done entirely in userspace, on the initrd.
I was misinformed then. Thanks.
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (-1 !=32768) 4194304
> VFS cannot open root device "LABEL=/" or unknown block (0,0)
His initrd can't be correctly loaded. It seems the initrd is larger than
4MiB but he didn't increase the maximum size in the kernel
configuration.
next prev parent reply other threads:[~2004-01-05 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S263478AbTLEJ0s/20031205092648Z+878@vger.kernel.org>
2003-12-05 9:34 ` Kernel panic neel vanan
2003-12-05 14:19 ` William Lee Irwin III
2003-12-06 5:47 ` William Lee Irwin III
2003-12-13 11:57 ` acpi related error neel vanan
2003-12-13 12:03 ` William Lee Irwin III
2004-01-05 11:56 ` Kernel panic.. in 3.0 Enterprise Linux neel vanan
2004-01-05 12:08 ` Christophe Saout
2004-01-05 12:23 ` Rik van Riel
2004-01-05 12:33 ` Christophe Saout [this message]
2004-01-05 12:21 ` Andreas Unterkircher
2004-01-05 12:24 ` Arjan van de Ven
2004-01-05 12:43 ` Kresimir Sparavec
2004-01-06 21:18 ` Lukas Postupa
2004-01-07 7:56 ` 2.6.0 works with 3.0 Enterprise Linux or not neel vanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1073306020.5755.5.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neelvanan@yahoo.com \
--cc=riel@redhat.com \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).