From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: malc@pulsesoft.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lock-up on PPC64
Date: Thu, 25 Dec 2008 11:32:43 +1100 [thread overview]
Message-ID: <1230165163.7292.32.camel@pasglop> (raw)
In-Reply-To: <871vvy77v4.fsf@linmac.oyster.ru>
On Wed, 2008-12-24 at 03:08 +0300, malc@pulsesoft.com wrote:
> Ken Moffat <zarniwhoop@ntlworld.com> writes:
>
> > On Tue, Dec 23, 2008 at 06:04:45AM +0300, malc@pulsesoft.com wrote:
> >>
> >> I don't know where to get PPC64 capable memtest, even if it exists the
> >> probability of two different machines exhibiting almost the same
> >> behaviour is rather slim. Netconsole doesn't catch anything. In fact
> >> i just had slightly different situation where after ssh connection was
> >> killed i was able to reconnect and look at dmesg there - nothing.
> >>
> > If you wanted to, you could get memtester from
> > http://pyropus.ca/software/memtester/ - not as convenient as
> > memtest86 etc (it's just a userspace task, so it can't test all the
> > memory), but it did work on ppc64 last time I tried it (nearly 2
> > years ago).
> >
>
> Thanks for the reference, but i'm sure, now more than ever, that bad
> memory has nothing to do with it, all signs are there that kernel is
> confused by the way signals are (mis)used by Mono.
It shouldn't be but I agree with you, it smells bad. Can you report that
again on the linuxppc-dev@ozlabs.org mailing list ? Along with
instructions to d/l, install & run the minimum repro-case ? I'll try to
give it a go on different ppc64 machines as soon as I'm over my upcoming
xmas hangover :-) If it appears to be ps3 specific, we can work with
Geoff Levand (PS3 maintainer for Sony) to try to identify the root cause
and fix it.
Cheers,
Ben.
next prev parent reply other threads:[~2008-12-25 0:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 18:18 Lock-up on PPC64 malc
2008-12-22 22:25 ` Marcin Slusarz
2008-12-22 23:32 ` Marcin Slusarz
2008-12-23 3:04 ` malc
2008-12-23 23:45 ` Ken Moffat
2008-12-24 0:08 ` malc
2008-12-25 0:32 ` Benjamin Herrenschmidt [this message]
2008-12-28 0:45 ` malc
2009-01-05 12:28 ` Michael Ellerman
2009-01-05 16:34 ` malc
2009-01-06 12:02 ` Benjamin Herrenschmidt
2009-01-06 17:35 ` malc
2009-01-06 21:17 ` Benjamin Herrenschmidt
2009-01-06 22:23 ` malc
2009-02-22 8:35 ` malc
2009-02-22 22:42 ` Benjamin Herrenschmidt
2009-01-06 12:05 ` Benjamin Herrenschmidt
2009-01-05 15:46 ` Arnd Bergmann
2009-02-23 16:36 ` Geoff Levand
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=1230165163.7292.32.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malc@pulsesoft.com \
/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