Re: kexec / kdump kernel panic

On 10/4/06, Steven Truong <[email protected]> wrote:

Hi, Valdis.  No, I actually used 2 different kernels for this:  one
for system kernel and the other for captured/crash kernel.

<snip >

CONFIG_PHYSICAL_START=0x1000000

<snip>

CONFIG_PHYSICAL_START=0x1000000

if both cases you have the same CONFIG_PHYSICAL_START?  I thought the
kexec kernel needed to start at a diffrent location then the original
kernel?

Thanks,
Keith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • kexec / kdump kernel panic
    • From: "Steven Truong" <[email protected]>
  • Re: kexec / kdump kernel panic
    • From: [email protected]
  • Re: kexec / kdump kernel panic
    • From: "Steven Truong" <[email protected]>

• Prev by Date: Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
• Next by Date: Re: wpa supplicant/ipw3945, ESSID last char missing
• Previous by thread: Re: kexec / kdump kernel panic
• Next by thread: Re: kexec / kdump kernel panic
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]