mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Mike Waychison <mikew@google.com>
Cc: YhLu <YhLu@tyan.com>, Peter Buckingham <peter@pantasys.com>,
	linux-kernel@vger.kernel.org,
	"'discuss@x86-64.org'" <discuss@x86-64.org>
Subject: Re: [discuss] Re: 2.6.13-rc2 with dual way dual core ck804 MB
Date: Thu, 11 Aug 2005 01:26:15 +0200	[thread overview]
Message-ID: <20050810232614.GC27628@wotan.suse.de> (raw)
In-Reply-To: <42FA8A4B.4090408@google.com>

On Wed, Aug 10, 2005 at 04:14:19PM -0700, Mike Waychison wrote:
> YhLu wrote:
> >andi,
> >
> >please refer the patch, it will move cpu_set(, cpu_callin_map) from
> >smi_callin to start_secondary.
> 
> 
> This patch fixes an apparent race / lockup on our 2-way dual cores (when 
> applied against 2.6.12.3).  The machine was locking up after 
> "Initializing CPU#2".

The real solution for this issue is the smp_call_function_single patch from Eric
that I reposted yesterday. Yh's patch just changed the timing slightly.


-Andi

  reply	other threads:[~2005-08-10 23:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  0:56 YhLu
2005-08-10 23:14 ` Mike Waychison
2005-08-10 23:26   ` Andi Kleen [this message]
2005-08-10 23:42     ` [discuss] " yhlu
2005-08-11  0:04       ` Andi Kleen
2005-08-11  0:17         ` yhlu
2005-08-11  0:23           ` yhlu
2005-08-11  0:28             ` Andi Kleen
2005-08-11  0:43               ` yhlu
2005-08-11  0:51                 ` Andi Kleen
2005-08-12  6:59                   ` yhlu
2005-08-12  7:04                     ` yhlu
2005-08-12 13:07                     ` Andi Kleen
2005-08-12 16:18                       ` yhlu
2005-08-12 16:41                         ` Andi Kleen
2005-08-12 17:36                           ` yhlu
2005-08-10 23:49     ` Mike Waychison
2005-08-10 23:31   ` Peter Buckingham

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=20050810232614.GC27628@wotan.suse.de \
    --to=ak@suse.de \
    --cc=YhLu@tyan.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=peter@pantasys.com \
    /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

Powered by JetHome