All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Buckingham <peter@pantasys.com>
To: Mike Waychison <mikew@google.com>
Cc: YhLu <YhLu@tyan.com>,
	linux-kernel@vger.kernel.org,
	"'discuss@x86-64.org'" <discuss@x86-64.org>
Subject: Re: 2.6.13-rc2 with dual way dual core ck804 MB
Date: Wed, 10 Aug 2005 16:31:49 -0700	[thread overview]
Message-ID: <42FA8E65.7060008@pantasys.com> (raw)
In-Reply-To: <42FA8A4B.4090408@google.com>

Mike Waychison wrote:
> 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 better ways is to use the patch from Eric that Andi posted to stable 
yesterday:

	http://x86-64.org/lists/discuss/msg06943.html

peter

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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  0:56 2.6.13-rc2 with dual way dual core ck804 MB YhLu
2005-08-10 23:14 ` Mike Waychison
2005-08-10 23:26   ` [discuss] " Andi Kleen
2005-08-10 23:42     ` 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-07 17:50 YhLu
2005-07-06 22:25 YhLu

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=42FA8E65.7060008@pantasys.com \
    --to=peter@pantasys.com \
    --cc=YhLu@tyan.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.