Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264163AbUAEMVW (ORCPT ); Mon, 5 Jan 2004 07:21:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264256AbUAEMVW (ORCPT ); Mon, 5 Jan 2004 07:21:22 -0500 Received: from shadow02.cubit.at ([80.78.231.91]:44776 "EHLO skeletor.netshadow.at") by vger.kernel.org with ESMTP id S264163AbUAEMVR (ORCPT ); Mon, 5 Jan 2004 07:21:17 -0500 Subject: Re: Kernel panic.. in 3.0 Enterprise Linux From: Andreas Unterkircher Reply-To: unki@netshadow.at To: neel vanan Cc: linux-kernel@vger.kernel.org In-Reply-To: <20040105115610.49148.qmail@web9505.mail.yahoo.com> References: <20040105115610.49148.qmail@web9505.mail.yahoo.com> Content-Type: text/plain Message-Id: <1073305274.811.48.camel@kuecken> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 05 Jan 2004 13:21:15 +0100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2770 Lines: 84 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: > > > 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/ > - 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/