To: linux-kernel@vger.kernel.org
From: malc@pulsesoft.com
Subject: Re: Lock-up on PPC64
Date: Wed, 24 Dec 2008 03:08:15 +0300
Message-ID: <871vvy77v4.fsf@linmac.oyster.ru>
References: <Pine.LNX.4.64.0812212058550.2164@linmac.oyster.ru> <20081222233223.GA6688@joi> <877i5rh9rm.fsf@linmac.oyster.ru> <20081223234513.GA8730@deepthought>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.20 (linux)
Cancel-Lock: sha1:dXh9BCioYbF1DeTC2+vFXObS3V0=
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1211
Lines: 23

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.

-- 
mailto:av1474@comtv.ru

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/