Re: [Mkdump-devel] mkdump patched kernel won't boot

[Fernando L. V. C. <fer...@in...>]

Hi Jeong-Sang,

Thank you for the prompt reply.

On Thu, 2006-02-16 at 18:36 +0900, Jeong-Sang Ohn wrote:
>         > But after patching the kernel with the mkdump
>         > patch(minik-patch-2.6.9-1.2), the
>         > kernel won't boot. (Also tried to boot with this kernel stand-alone, 
>         > but it
>         > won't boot either.)Cannot see anything printing. And after a few secs,
>         > the
>         > system reboots.
I have a hunch that what is happening is something like this:

  - The second kernel boots normally but nothing is sent to the serial
console because it is not configured properly. (see below)
  - The second kernel is not able to find the specified dump device (see
below) and, consequently, reboots the machine (this is the default
behavior when the device is not found).

>        it looks like this (load is complete & haven't wrote '2' to /proc/mkexec/stats yet):
>        [root@255_63_63_DPSA root]# cat /proc/mkexec/mem 
>        16
This is a valid value.

>        [root@255_63_63_DPSA root]# cat /proc/mkexec/dumpdev
>        0x2100002
Are you sure this is a correct values? Could you show the output of ls
-l /dev/your_dump_device?

>        [root@255_63_63_DPSA root]# cat /proc/mkexec/parameter
>        console=console=ttyS1,115200n8 lpj=2392060 no-hlt
>        mkdump_reboot=halt dump_delay=0 
Regarding the console settings, you want either
"console=tty0 console=ttyS1,115200n8"
or
"console=ttyS1,115200n8".

"console=console=ttyS1,115200n8" seems to be invalid.

>        [root@255_63_63_DPSA root]# cat /proc/mkexec/path
>        /boot/vmlinux.bin
I assume this was copied from "arch/i386/boot/compressed/vmlinux.bin".
Correct?

>        [root@255_63_63_DPSA root]# cat /proc/mkexec/stats
>        1
This looks good.

Could you make the aforementioned changes and try again? 
Thanks in advance.

Regards,

Fernando