From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: ERIC NORTHUP <eric.northup@jhu.edu>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 4way smp on ppc32
Date: Wed, 31 Mar 2004 18:05:50 +1000 [thread overview]
Message-ID: <1080720349.1435.11.camel@gaston> (raw)
In-Reply-To: <7eb2247ee728.7ee7287eb224@jhumail.jhu.edu>
On Wed, 2004-03-31 at 11:57, ERIC NORTHUP wrote:
> Hi all,
>
> I have been trying to get my 4-processor Daystar GenesisMP system to run Linux in smp mode,
> without success. The system works reliably with a uniprocessor kernel.
> But it oopses on boot with an smp kernel. I have attached a boot log from a
> serial console for a 2.6 kernel, but I get similar messages with other
> kernels I've tried. Although the log is from 2.6.4, I've tried 2.6.5-pre3 which
> included some ppc32 fixes, though they didn't fix this problem.
> I've also tried different gcc versions.
>
> I don't understand why only 2 of the 4 cpus would respond to the smp_call_function().
> Any suggestions for where to start looking? I am not subscribed to linuxppc-dev,
> so please CC me on replies. Thanks,
Interesting... Apparently, all the CPUs are coming in, but interrupts
don't get properly delivered to the "other" CPUs...
I'll have a look, that setup should work. Did you try a 2.4 kernel ?
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-31 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 1:57 4way smp on ppc32 ERIC NORTHUP
2004-03-31 8:05 ` Benjamin Herrenschmidt [this message]
2004-03-31 8:17 ` Benjamin Herrenschmidt
2004-03-31 17:56 ` Mark Guertin
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 0:59 ERIC NORTHUP
2004-04-05 21:39 ` Mark Guertin
2004-04-06 3:37 ERIC NORTHUP
2004-04-06 5:53 ` Benjamin Herrenschmidt
[not found] ` <000001c41b9e$8ca8c530$d100000a@sbs2003.local>
2004-04-07 14:54 ` Mark Guertin
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=1080720349.1435.11.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eric.northup@jhu.edu \
--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).