linux-kernel - Re: kexec / kdump kernel panic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a762e240610041537n6a2ffd1cja3c18ce99b714b0f@mail.gmail.com>
Date:	Wed, 4 Oct 2006 15:37:36 -0700
From:	"Keith Mannthey" <kmannth@...il.com>
To:	"Steven Truong" <midair77@...il.com>
Cc:	"Valdis.Kletnieks@...edu" <Valdis.Kletnieks@...edu>,
	linux-kernel@...r.kernel.org
Subject: Re: kexec / kdump kernel panic

On 10/4/06, Steven Truong <midair77@...il.com> 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/