Kernel panic...

Kernel panic...

[neel vanan]

Hi,
currently i am compiling kernel 2.6.0-test11, After
making kernel image and installing new module when i
boot with new kernel image i am getting this error:

 Red Hat nash version 3.4.42 starting
 Loading sd_mod.ko module
 Loading aic79xx.ko module
 scsi0: Adaptec AIC79xx PCI-X SCSI HBA DRIVER, Rev
1.3.9
        .....................................
 scsi0:A:0:0: Tagged Queing enabled, Depth 32
 scsi device sda: drive cache: write back
 /dev/scsi/host0/bus0/target0/lun0: unknown partition
table
 Attached scsi disk sda at scsi0, channel0, id0, lun0
 mounting /proc file system
 creating block devices
 creating Root devices
 Mounting root filesystem
 mount : erro 6 mounting ext3
 pivotroot : pivot_root (/sysroot, /sysroot/initrd)
failed:2
 umount /initrd/proc failed :2
 Mounting devfs on /dev
 freeing unused kernel memory : 464k freed
 Kernel panic: no init found. Try passing init= option
to kernel
After then blinking cursor.

#Entries in grub.conf is:
 title Red Hat Linux (2.6.0)
 root (hd0,0)
 kernel /vmlinux2.6.0 ro root=/dev/sda3
 initrd /initrd-2.6.0.img
 #
also i had tried append="hdc=ide-scsi root=LABEL=/"
and append="hdc=ide-scsi root=/dev/sda3"

 <content of /etc/fstab>
 LABEL=/      /          ext3    defaults        1 1
 LABEL=/boot  /boot      ext3    defaults        1 2
 none         /dev/pts   devpts  gid=5,mode=620  0 0
 none         /proc      proc    defaults        0 0
 none         /dev/shm   tmpfs   defaults        0 0
 /dev/sda2    swap       swap    defaults        0 0
 /dev/cdrom   /mnt/cdrom udf,iso9660
noauto,owner,kudzu,ro 0 0
 /dev/fd0     /mnt/floppy auto  noauto,owner,kudzu 0 0

Please let me know where i am wrong.

Thanks.

Neel


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

Re: Kernel panic...

[William Lee Irwin III]

On Fri, Dec 05, 2003 at 01:34:35AM -0800, neel vanan wrote:
>  Mounting root filesystem
>  mount : erro 6 mounting ext3
>  pivotroot : pivot_root (/sysroot, /sysroot/initrd)
> failed:2
>  umount /initrd/proc failed :2
>  Mounting devfs on /dev
>  freeing unused kernel memory : 464k freed
>  Kernel panic: no init found. Try passing init= option
> to kernel
> After then blinking cursor.

Could you post your .config?


-- wli

Re: Kernel panic...

[William Lee Irwin III]

On Fri, Dec 05, 2003 at 01:34:35AM -0800, neel vanan wrote:
>>  Mounting root filesystem
>>  mount : erro 6 mounting ext3
>>  pivotroot : pivot_root (/sysroot, /sysroot/initrd)
>> failed:2
>>  umount /initrd/proc failed :2
>>  Mounting devfs on /dev
>>  freeing unused kernel memory : 464k freed
>>  Kernel panic: no init found. Try passing init= option
>> to kernel
>> After then blinking cursor.

On Fri, Dec 05, 2003 at 06:19:28AM -0800, William Lee Irwin III wrote:
> Could you post your .config?

Okay, the first thing to try is removing devfs from the equation if
possible. Your mount is getting back -ENXIO, suggesting whatever device
you're trying to mount doesn't exist according to the kernel. devfs
does device management internally to the kernel, so it's a likely culprit.

It would also be helpful to find the command-line arguments issued to
mount(8) when it's failing, as well as more information about the
contents of your initrd. Can you boot without an initrd?


-- wli

acpi related error.....

[neel vanan]

Hi list,
Currently i am working on RedHat9.0 kernel 2.4.20-8, i
am compiling kernel 2.6.0-test11 with NUMA and SMP
enabled. I had selected summit though i am having
non-summit box. When i am trying to make bzImage in
the last i get this message:
drivers/built-in.o(.init.text+0x30cf): In function
`acpi_parse_slit':
: undefined reference to `acpi_numa_slit_init'
drivers/built-in.o(.init.text+0x30f0): In function
`acpi_parse_processor_affinity':
: undefined reference to
`acpi_numa_processor_affinity_init'
drivers/built-in.o(.init.text+0x3110): In function
`acpi_parse_memory_affinity':
: undefined reference to
`acpi_numa_memory_affinity_init'
drivers/built-in.o(.init.text+0x3199): In function
`acpi_numa_init':
: undefined reference to `acpi_numa_arch_fixup'
make: *** [.tmp_vmlinux1] Error 1
How can i compile this without commenting these lines.

Thanks.


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

Re: acpi related error.....

[William Lee Irwin III]

On Sat, Dec 13, 2003 at 03:57:33AM -0800, neel vanan wrote:
> Currently i am working on RedHat9.0 kernel 2.4.20-8, i
> am compiling kernel 2.6.0-test11 with NUMA and SMP
> enabled. I had selected summit though i am having
> non-summit box. When i am trying to make bzImage in
> the last i get this message:
> drivers/built-in.o(.init.text+0x30cf): In function
> `acpi_parse_slit':
> : undefined reference to `acpi_numa_slit_init'
> drivers/built-in.o(.init.text+0x30f0): In function
> `acpi_parse_processor_affinity':
> : undefined reference to
> `acpi_numa_processor_affinity_init'

You are likely enabling CONFIG_NUMA on a PC subarch or trying to build
CONFIG_X86_SUMMIT without CONFIG_ACPI; this is ridiculous as PC means
non-NUMA and Summit means ACPI. I'm not sure how you selected this
combination.

Best to turn off CONFIG_NUMA unless you have an x440, x445, or NUMA-Q.


-- wli

Kernel panic.. in 3.0 Enterprise Linux

[neel vanan]

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

Re: Kernel panic.. in 3.0 Enterprise Linux

[Christophe Saout]

Am Mo, den 05.01.2004 schrieb neel vanan um 12:56:

> 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)

LABEL= is a RedHat extension. Please use the normal root options that is
described in the Grub or kernel documentation.

Re: Kernel panic.. in 3.0 Enterprise Linux

[Rik van Riel]

On Mon, 5 Jan 2004, Christophe Saout wrote:
> Am Mo, den 05.01.2004 schrieb neel vanan um 12:56:
> 
> > 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)
> 
> 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.

If you do not want to use an initrd, you need to use the
normal root options instead, something like root=/dev/hda3

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

Re: Kernel panic.. in 3.0 Enterprise Linux

[Christophe Saout]

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.

Re: Kernel panic.. in 3.0 Enterprise Linux

[Andreas Unterkircher]

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/
> 

Re: Kernel panic.. in 3.0 Enterprise Linux

[Arjan van de Ven]

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

On Mon, 2004-01-05 at 12:56, neel vanan wrote:
> 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)

RHEL3 isn't quite 2.6 ready btw; you need to update quite a few packages
to get it working right.

Also if you use mount-by-label you do need to create an initrd (with a
2.6 capable mkinitrd)...


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Kernel panic.. in 3.0 Enterprise Linux

[Kresimir Sparavec]

On Mon, Jan 05, 2004 at 01:24:38PM +0100, Arjan van de Ven wrote:
> On Mon, 2004-01-05 at 12:56, neel vanan wrote:
> > 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)
> 
> RHEL3 isn't quite 2.6 ready btw; you need to update quite a few packages
> to get it working right.

could you please summarize which ones? i upgraded modutils and modified
rc.sysinit for usb support. the rest works unmodified (except NVIDIA
proprietary kernel driver which does not have 2.6.x support yet, but XFree86
driver works fine for me) as far as i can tell. i got exactly 0 (zero)
kernel panics up to now. compared with 2.4.0 few years ago, 2.6.0 works
like charm

> 
> Also if you use mount-by-label you do need to create an initrd (with a
> 2.6 capable mkinitrd)...
> 

Re: Kernel panic.. in 3.0 Enterprise Linux

[Lukas Postupa]

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

Kresimir Sparavec wrote:
> the rest works unmodified (except NVIDIA
> proprietary kernel driver which does not have 2.6.x support yet, but XFree86
> driver works fine for me) 

Take a look at http://www.minion.de/ .

Lukas

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

2.6.0 works with 3.0 Enterprise Linux or not...

[neel vanan]

Hi All,
I had posted my problem in mailing list i didn't get
proper response.
I would like to know whether 2.6.0 works properly with
Enterprise Linux 3.0 or or not. For me it works fine
with RedHat Linux9.0 but same kernel didn't boot with
EL 3.0. Arjan had replied that i have to upgrade some
packages but how many that is mystery. If i have to
upgrade than how many packages i should upgrade. I
have already upgraded mkinitrd and modutils still it
gives this error while booting:

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 had also tried root=/dev/sda2 and also root=0802.
But still it is not booting.

Help needed urgently, Thanks in advance.

Neel.

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus