From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Aaron Tokhy <atokhy@gmail.com>
Subject: Re: [PROBLEM] Soft lockup on Linux 2.6.27, 2 patches, Cell/PPC64
Date: Wed, 15 Oct 2008 15:49:54 +1100 [thread overview]
Message-ID: <1224046194.8157.428.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.64.0810141130340.16020@vixen.sonytel.be>
On Tue, 2008-10-14 at 11:32 +0200, Geert Uytterhoeven wrote:
>
> which points again to smp_call_function_single...
Yup, it doesn't bring more information. At this stage, your 'other' CPU
is stuck with interrupts disabled. Hard to tell what's happening without
some HW assist. Do you have ways to trigger a non-maskable interrupt
such as a 0x100 ? That would allow to catch the other guy in xmon and
see what it was doing...
It could be something in the ps3vram driver causing the kernel to
lockup.... Now the question is whether the kernel is stuffed with
something like a deadlock with interrupts off, or is it a HW problem
causing a CPU to lockup on an access to the vram ?
I'm afraid only you guys have tools that would allow to debug that
sort of problem.
Cheers,
Ben.
next prev parent reply other threads:[~2008-10-15 4:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 4:32 [PROBLEM] Soft lockup on Linux 2.6.27, 2 patches, Cell/PPC64 Aaron Tokhy
2008-10-13 7:58 ` Geert Uytterhoeven
2008-10-14 9:32 ` Geert Uytterhoeven
2008-10-15 4:49 ` Benjamin Herrenschmidt [this message]
2008-10-15 9:25 ` Geert Uytterhoeven
2008-10-15 9:28 ` Benjamin Herrenschmidt
2008-10-15 9:46 ` Geert Uytterhoeven
2008-10-15 11:37 ` Benjamin Herrenschmidt
2008-10-15 11:46 ` Geert Uytterhoeven
2008-10-15 11:49 ` Benjamin Herrenschmidt
2008-10-15 12:05 ` Geert Uytterhoeven
2008-10-15 20:53 ` 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=1224046194.8157.428.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=atokhy@gmail.com \
--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).