From: Adrian Cox <adrian@humboldt.co.uk>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: SMP in 32-bit arch/powerpc
Date: Wed, 02 Aug 2006 09:25:45 +0100 [thread overview]
Message-ID: <1154507145.24203.0.camel@localhost.localdomain> (raw)
Is anybody else having problems with 32-bit SMP support in arch/powerpc?
I'm using 2.6.17 as my current base, because I've not yet merged the
latest mpic changes.
I'm currently bringing up a dual-7448 board, and when I build the kernel
with CONFIG_SMP, the bootmem allocator corrupts the device tree. The
strange thing is, this still happens when I don't start the second CPU.
Kernels built without CONFIG_SMP run flawlessly on the same hardware.
--
Adrian Cox <adrian@humboldt.co.uk>
next reply other threads:[~2006-08-02 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 8:25 Adrian Cox [this message]
2006-08-02 9:08 ` SMP in 32-bit arch/powerpc Michael Ellerman
2006-08-02 9:27 ` Zhang Wei-r63237
2006-08-02 13:32 ` Kumar Gala
2006-08-02 19:36 ` Adrian Cox
2006-08-02 14:42 ` Jon Loeliger
2006-08-16 23:12 ` Benjamin Herrenschmidt
2006-08-17 7:19 ` Adrian Cox
2006-08-17 7:45 ` Benjamin Herrenschmidt
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=1154507145.24203.0.camel@localhost.localdomain \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-dev@ozlabs.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).