All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars.spam@nocrew.org>
To: Tony Mantler <nicoya@apia.dhs.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Bogus interrupt -1
Date: 23 Apr 2001 14:24:39 +0200	[thread overview]
Message-ID: <85wv8bhkhk.fsf@junk.nocrew.org> (raw)
In-Reply-To: <v04003a02b709cb418690@[24.70.162.12]>


Tony Mantler <nicoya@apia.dhs.org> writes:
> At 4:52 AM -0500 4/23/2001, Lars Brinkhoff wrote:
> > However, it still seems like one CPU hangs after some time.
>
> A friend of mine is having trouble with one CPU hanging in his dual
> G4 under MacOS X. The symptoms are pretty much (from what he's told
> me): The system runs for a while, then one of the CPUs goes off into
> la-la land never to return again.

The same thing happens to me, as far as I can tell.  Usually after a
few hours of operation.

> You may want to check to make sure you don't have a hardware
> problem.

Any idea how?  I ran the "Apple Hardware Test" CD without any failure
indications.

--
http://lars.nocrew.org/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-23 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 16:32 Bogus interrupt -1 Lars Brinkhoff
2001-04-20 17:13 ` Benjamin Herrenschmidt
2001-04-23  9:52   ` Lars Brinkhoff
2001-04-23 12:18     ` Tony Mantler
2001-04-23 12:24       ` Lars Brinkhoff [this message]
2001-04-23 12:47         ` Tony Mantler
2001-05-12 18:18       ` Success? Both CPUs running (Was: Bogus interrupt -1) Lars Brinkhoff
2001-05-12 18:25         ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2001-01-20 10:17 Bogus interrupt -1 Jiri Masik
2001-01-18 23:01 Michel Dänzer
2001-01-19  9:50 ` Benjamin Herrenschmidt
2001-01-20  2:23   ` Michel Dänzer

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=85wv8bhkhk.fsf@junk.nocrew.org \
    --to=lars.spam@nocrew.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=nicoya@apia.dhs.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 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.