From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 SMP under 2.6?
Date: Sat, 03 Sep 2005 16:21:15 +0000 [thread overview]
Message-ID: <4319CD7B.1070502@mc.net> (raw)
In-Reply-To: <5460e33305090209002d742242@mail.gmail.com>
Christian Joensson wrote:
> I'd just like to ask what the status is of sparc32 and SMP under the 2.6 kernel?
>
Not much progress here. I've only ported my SMP patch up to 2.6.12.
Supersparc seems to be as stable under SMP as UP, but hypersparcs keep
giving me problems.
I've tried an experiment of setting the cache mode to write-through on
hypersparc and now it crashes early on. Maybe someone might have some
insight into what's happening:
Starting CPU 2 at f01e0960
Unable to handle kernel NULL pointer dereference
tsk->{mm,active_mm}->context = ffffffff
tsk->{mm,active_mm}->pgd = fc000000
\|/ ____ \|/
"@'/ ,. \`@"
/_| \__/ |_\
\__U_/
swapper(0): Oops [#1]
PSR: 1e900fc5 PC: f0182b48 NPC: f0182b4c Y: 00000000 Not tainted
PC: <schedule+0x240/0x398>
%G: f1302000 f05f61b4 0000008c 0000000c 0001312c 00000001 fbf14000
000003a
%O: f05f58a0 f018ba38 00000000 00002000 00000000 ffff8b0f fbf15ec8
f0182a00
RPC: <schedule+0xf8/0x398>
%L: 1e0000c6 00000002 0000006c f071c7c0 f05f5d54 f05f58a0 0098963a
4c285180
%I: 00000004 f01a91d0 0000005b 000b7000 0c845880 f071c8e8 fbf15f38
f00188f4
Caller[f00188f4]: cpu_idle+0x20/0x38
Caller[f001f05c]: smp_do_cpu_idle+0x0/0x10
Caller[00000000]: start+0xfffc000/0x10
Instruction DUMP: 82050001 c4006018 a400bfe0 <c204a018> 80a06063
2480001f c024a048 c204a048 80a06000
Kernel panic - not syncing: Attempted to kill the idle task!
<0>Press Stop-A (L1-A) to return to the boot prom
prev parent reply other threads:[~2005-09-03 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 16:00 sparc32 SMP under 2.6? Christian Joensson
2005-09-03 16:21 ` Bob Breuer [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=4319CD7B.1070502@mc.net \
--to=breuerr@mc.net \
--cc=sparclinux@vger.kernel.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.