From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Stephen Hemminger <shemminger@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Crash with SMP on post 2.6.15 -git kernel
Date: Wed, 11 Jan 2006 19:33:38 +0530 [thread overview]
Message-ID: <20060111140338.GF4990@in.ibm.com> (raw)
In-Reply-To: <200601111450.07996.ak@suse.de>
On Wed, Jan 11, 2006 at 02:50:07PM +0100, Andi Kleen wrote:
> On Wednesday 11 January 2006 14:42, Vivek Goyal wrote:
>
> > While testing this I ran into another problem with same symtoms. If
> > I compile my kernel for physical location greater than or equal to
> > 16MB then only BP boots and applicatoin processors don't come up. I had
> > noticed this problem in i386 and posted a patch. Here is the similar patch
> > for x86_64.
> >
> > Though the symtoms are same but this does not seem to be related to the
> > problem which Stephen is facing as he seems to be compiling the kernel
> > for 1MB location only.
>
> I don't think that's Stephen's problem.
You are right. This patch is for a entirely different problem. I posted the
patch in the context of this thread because on the surface problem symtoms
are same.
This patch is required to boot SMP kernel from non-default physical
locations as in case of kdump.
Can you please include this patch.
Thanks
Vivek
next prev parent reply other threads:[~2006-01-11 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 0:54 Crash with SMP on post 2.6.15 -git kernel Stephen Hemminger
2006-01-11 1:27 ` Andi Kleen
2006-01-11 2:49 ` Stephen Hemminger
2006-01-11 9:32 ` Vivek Goyal
2006-01-11 11:12 ` Andi Kleen
2006-01-11 13:42 ` Vivek Goyal
2006-01-11 13:50 ` Andi Kleen
2006-01-11 14:03 ` Vivek Goyal [this message]
2006-01-12 0:05 ` Stephen Hemminger
2006-01-12 0:12 ` Andi Kleen
2006-01-11 22:57 ` Stephen Hemminger
2006-01-11 23:36 ` Andi Kleen
2006-01-11 23:44 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060111140338.GF4990@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox