From: benh@kernel.crashing.org
To: Christopher Murtagh <christopher.murtagh@mcgill.ca>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: SMP/HIGHMEM/7450 status ?
Date: Thu, 6 Jun 2002 19:45:30 +0200 [thread overview]
Message-ID: <20020606174530.22442@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206061251190.20358-100000@blues.wcg.mcgill.ca>
>
>On Thu, 6 Jun 2002 benh@kernel.crashing.org wrote:
>>Xserve uses 7455 (like newer dual G4s), which doesn't seem to exhibit
>>the problem.
>
> Damn... does this mean that the 7450 machines are lemons (wouldn't
>surprise me if the answer was a resounding 'yes')?
I can't say for sure. It seems we are hitting a CPU bug, but after
studying the errata and trying all sort of ways to "catch" the dead
CPU when the lockup happen, I had to give up.
It seems even tweaking the CPU reset line won't get it back from the
deadlock situation (I'm tweaking it using the firewire controller
tapping Apple's KeyLargo ASIC GPIO registers, this works fine when
the CPU isn't locked up in this state).
> herrenschmidt.wcg.mcgill.ca
hehe, nice ;) though I wouldn't like having to type that name every
day to telnet to the box ;)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-06 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 15:51 SMP/HIGHMEM/7450 status ? Christopher Murtagh
2002-06-06 5:37 ` benh
2002-06-06 16:29 ` Christopher Murtagh
2002-06-06 6:08 ` benh
2002-06-06 17:09 ` Christopher Murtagh
2002-06-06 17:45 ` benh [this message]
2002-06-06 19:40 ` Christopher Murtagh
2002-06-07 8:23 ` Geert Uytterhoeven
2002-06-06 19:51 ` Timothy A. Seufert
2002-06-06 19:46 ` Benjamin Herrenschmidt
2002-06-08 23:10 ` Christopher Murtagh
2002-06-09 0:41 ` Dan Burcaw
2002-06-06 16:05 ` Kevin B. Hendricks
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=20020606174530.22442@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=christopher.murtagh@mcgill.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).