From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tony Mantler <nicoya@apia.dhs.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Fwd: CPU features
Date: Mon, 2 Apr 2001 00:40:34 +0200 [thread overview]
Message-ID: <20010401224034.32550@smtp.wanadoo.fr> (raw)
In-Reply-To: <v04003a02b6ed59f245ee@[24.70.162.12]>
>I just booted with the second CPU wedged (that is to say, bootx from MacOS
>9) with the same kernel to see what it would do with only 1 cpu, and it
>still stops at the same place, so I'm guessing the problem should be
>reproducable on a single-cpu system running an SMP kernel, if that helps
>any.
Well, I booted succesfully the Pismo (which doesn't use the lost_interrupts
stuff) with an SMP kernel. So either this is broken, or something else
related to powersurge is broken.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-01 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 9:16 Fwd: CPU features Benjamin Herrenschmidt
2001-03-31 15:05 ` Kaoru Fukui
2001-03-31 15:35 ` Kaoru Fukui
2001-03-31 17:14 ` Benjamin Herrenschmidt
2001-04-01 12:30 ` Kaoru Fukui
2001-04-01 15:03 ` Benjamin Herrenschmidt
[not found] ` <20010401150348.13545@smtp.wanadoo.fr>
2001-04-01 15:22 ` Kaoru Fukui
2001-04-01 17:04 ` Benjamin Herrenschmidt
2001-04-01 18:32 ` Tony Mantler
2001-04-01 20:09 ` Benjamin Herrenschmidt
2001-04-01 21:45 ` Tony Mantler
2001-04-01 22:07 ` Benjamin Herrenschmidt
2001-04-01 22:24 ` Tony Mantler
2001-04-01 22:40 ` Benjamin Herrenschmidt [this message]
2001-04-01 19:11 ` Kaoru Fukui
2001-04-01 20:11 ` Benjamin Herrenschmidt
2001-04-02 18:46 ` Dan Malek
2001-04-02 21:58 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 15:46 Holger Bettag
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=20010401224034.32550@smtp.wanadoo.fr \
--to=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 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).