From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lars Brinkhoff <lars.spam@nocrew.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Success? Both CPUs running (Was: Bogus interrupt -1)
Date: Sat, 12 May 2001 20:25:35 +0200 [thread overview]
Message-ID: <20010512182535.6170@smtp.wanadoo.fr> (raw)
In-Reply-To: <85y9s2sa6y.fsf_-_@junk.nocrew.org>
>>
>> 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. Not very complicated.
>
>It seems to me there was a bug in benh 2.4.4-pre1. I'm now running bk
>2.4.5-pre1, and I have never seen a CPU hang.
Can you tell me how my current 2.4.4 goes ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-12 18:25 UTC|newest]
Thread overview: 8+ 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
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 [this message]
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=20010512182535.6170@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=lars.spam@nocrew.org \
--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).