linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Unterkircher <unki@netshadow.at>
To: neel vanan <neelvanan@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic.. in 3.0 Enterprise Linux
Date: Mon, 05 Jan 2004 13:21:15 +0100	[thread overview]
Message-ID: <1073305274.811.48.camel@kuecken> (raw)
In-Reply-To: <20040105115610.49148.qmail@web9505.mail.yahoo.com>

have you rebuild your initrd? you have written you
have compile in all needed things - so do you still
need the initrd? if not - try to remove the line...

andreas

Am Mon, den 05.01.2004 schrieb neel vanan um 12:56:
> Hi all,
> 
> The kernel I have working is version 2.4.21-4.EL and I
> can still boot up to that. I compiled a 2.6.0 version
> and installed it in exactly the same way that the old
> version is, just appending 2.6.0 to the end of the
> file. so when I reboot I get a boot screen that shows:
> 
> Red Hat Enterprise Linux AS (2.4.21-4.ELsmp)
> Red Hat Enterprise Linux As-up (2.4.21-4.EL)
> Red Hat linux (2.6.0)
> 
> Enterprise linux still boots up fine but when I try
> and boot up Red Hat linux (2.6.0) I get some ouput and
> then a kernel panic with this message:
> 
> <snip>
> Software Suspend has malfunctioning SMP support.
> Disabled :(
> ACPI: (supports S0 S1 S4 S5)
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (-1 !=32768) 4194304
> VFS cannot open root device "LABEL=/" or unknown block
> (0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> I am running Linux Enterprise Edition version 3.0 on
> my server. It has 2 Xeon processors and 1 U360 scsi
> HD. The whole reason behind my compiling a kernel is
> trying to get support for high memory (this 
> machine has 4 gigs of ram) and multi-processor
> support.
> 
> I'm pretty sure I selected all scsi and driver support
> because when i run the same kernel with RedHat Linux
> 9.0 in same machine it works fine. Everything is
> compiled in and not as modules.
> 
> This is snip of my grub.conf file:
> # grub.conf generated by anaconda
> #
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm
> title RedHat Enterprise Linux AS (2.4.21-4.ELsmp)
> 	root (hd0,0)
> 	kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/
> 	initrd /initrd-2.4.21-4.EL.img
> title RedHat Linux (2.6.0)
> 	root (hd0,0)
> 	kernel /linux-2.6.0 ro root=LABEL=/
> 	initrd /initrd-2.6.0.img
> 
> Any help would be greatly appreciated! Thanks in
> advance,
> 
> Neel 
> 
> 
> __________________________________
> Do you Yahoo!?
> Find out what made the Top Yahoo! Searches of 2003
> http://search.yahoo.com/top2003
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  parent reply	other threads:[~2004-01-05 12:21 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
2004-01-05 12:21         ` Andreas Unterkircher [this message]
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=1073305274.811.48.camel@kuecken \
    --to=unki@netshadow.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelvanan@yahoo.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).