2.6.32 Kernel panic - not syncing: Attempted to kill init! Rebooting in 180 seconds..

[Américo Wang]

On Fri, Dec 18, 2009 at 3:38 PM, Zhiyong Wu <zwu.kernel at gmail.com> wrote
> On Fri, Dec 18, 2009 at 3:12 PM, Américo Wang <xiyou.wangcong at gmail.com> wrote:
>> On Fri, Dec 18, 2009 at 12:08 PM, Zhiyong Wu <zwu.kernel at gmail.com> wrote:
>>> HI,
>>>
>>> linux-2.6.32 is compiled on a p6 machine with RH5.4 OS and KVM option is enable.
>>>
>>> When rebooting this machine, a crash takes place such as:
>>>

<snip>

>>> command line: ro console=hvc0 rhgb quiet root=LABEL=/
>>> memory layout at init:
>>>  memory_limit : 0000000000000000 (16 MB aligned)
>>>  alloc_bottom : 00000000019b0000
>>>  alloc_top    : 0000000008000000
>>>  alloc_top_hi : 0000000008000000
>>>  rmo_top      : 0000000008000000
>>>  ram_top      : 0000000008000000
>>> instantiating rtas at 0x0000000006e10000... done
>>> boot cpu hw idx 0000000000000000
>>> copying OF device tree...
>>> Building dt strings...
>>> Building dt structure...
>>> Device tree strings 0x0000000001bc0000 -> 0x0000000001bc15bb
>>> Device tree struct  0x0000000001bd0000 -> 0x0000000001bf0000
>>> Calling quiesce...
>>> returning from prom_init
>>> Red Hat nash version 5.1.19.6 starting
>>> ibmvscsi 30000002: fast_fail not supported in server
>>> sd 0:0:1:0: [sda] Assuming drive cache: write through
>>> sd 0:0:1:0: [sda] Assuming drive cache: write through
>>> sd 0:0:1:0: [sda] Assuming drive cache: write through
>>> insmod: error inserting '/lib/dm-region-hash.ko': -1 File exists
>>> mount: could not find filesystem '/dev/root'
>>> setuproot: moving /dev failed: No such file or directory
>>> setuproot: error mounting /proc: No such file or directory
>>> setuproot: error mounting /sys: No such file or directory
>>> switchroot: mount failed: No such file or directory
>>> Kernel panic - not syncing: Attempted to kill init!
>>> Rebooting in 180 seconds..[disconnect]
>>>
>>> Can anyone give me a warm hand?
>>
>> Probably this is not a problem of kernel, maybe it's
>> a problem of your initial ramdisk, or something wrong with
>> your root filesystem.
>>
>> Does changing "root=LABEL=/" to "root=/dev/XXX" help?
>> Where "/dev/XXX" is your root filesystem.
>>
>
> It does'nt still work based on your method.

Hmm, so I would guess it's a problem in your initial ramdisk.

So you can boot RH5 native kernel with the same boot options
but only this one not??

Or maybe the udev your are using doesn't work with 2.6.32?
Only another guess...

But anyway, checking your 'mkinitrd' would help.