From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 SMP debugging advice needed
Date: Sat, 24 Mar 2007 10:55:26 +0000 [thread overview]
Message-ID: <4605039E.20800@systella.fr> (raw)
In-Reply-To: <460449B6.7010308@earthlink.net>
Hello,
Robert Reif a écrit :
> I'm trying to get a git rc4 SMP kernel working on an ss20 and am running
> into a few problems.
I have built the same kernel with some debug information about
deadlocks and spinlocks. This kernel works fine with one SuperSPARC but
not with one HyperSPARC (cache aliasing management mistake). With dual
SuperSPARC (SM71), kernel randomly hangs with spinlock bug. Sometimes,
it can boot, sometimes not, and I don't know how debug this kernel. When
it completely boots, I can see some deadlocks (for example, run "make
-j2" to build a kernel randomly stops with cc in D state), some randomly
oops (syscall_to_hard) when pipe syscall is executed.
> An SMP kernel boots and runs fine using debian etch and a single
> CPU. However I do get this in kern.log:
>
> Mar 23 10:59:53 ss20 kernel: Kernel command line: root=/dev/sda2 ro
> Mar 23 10:59:53 ss20 kernel: PID hash table entries: 1024 (order: 10,
> 4096 bytes)
> Mar 23 10:59:53 ss20 kernel: start_kernel(): bug: interrupts were
> enabled early
> Mar 23 10:59:53 ss20 kernel: Console: colour dummy device 80x25
>
> It looks like something similar was fixed a while back on sparc64 but
> I don't know if this is related. I'm recompiling a kernel with more
> debugging turned on to see what happens.
>
> I get a hang when booting the same kernel with 2 CPUs at:
>
> Begin: Loading essential drivers... ...
>
> Nothing interesting before that.
>
> Any advice on how to approach fixing these issues? I can test patches.
I can test too. If someones has some idea about this trouble or a
method to debug this kernel, he is welcome ;-)
Regards,
JKB
next prev parent reply other threads:[~2007-03-24 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 21:42 sparc32 SMP debugging advice needed Robert Reif
2007-03-24 10:55 ` BERTRAND Joël [this message]
2007-03-24 16:34 ` Tom "spot" Callaway
2007-03-24 16:53 ` Jiri Gaisler
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=4605039E.20800@systella.fr \
--to=joel.bertrand@systella.fr \
--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.