On Tue, 03 Oct 2006 17:18:21 PDT, Steven Truong said: > /usr/sbin/kexec -p /boot/vmlinux > --initrd=/boot/initrd-2.6.18-kdump.img --args-linux > --append="root=/dev/sda3 irqpoll init 1" If the /boot/vmlinux is the one you usually use to boot, that won't work. Your usual vmlinux is almost certainly linked to load at the 1M line, and you need a kernel linked to load at the 16M line (as set in crashkernel=). See the CONFIG_PHYSICAL_START config option, and there's other details in Documentation/kdump/kdump.txt - it looks like you have most of it right, except you need to build *TWO* specially configured kernels (your production one with KEXEC support and a few other things, and then the dump kernel with a different PHYSICAL_START and a few settings).
Attachment:
pgpjIPirxxEOo.pgp
Description: PGP signature
- Follow-Ups:
- Re: kexec / kdump kernel panic
- From: "Steven Truong" <[email protected]>
- Re: kexec / kdump kernel panic
- References:
- kexec / kdump kernel panic
- From: "Steven Truong" <[email protected]>
- kexec / kdump kernel panic
- Prev by Date: Re: [patch] clockevents: drivers for i386, fix #2
- Next by Date: Re: Registration Weakness in Linux Kernel's Binary formats
- Previous by thread: kexec / kdump kernel panic
- Next by thread: Re: kexec / kdump kernel panic
- Index(es):