From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 22388DE35D for ; Wed, 7 Jan 2009 08:18:07 +1100 (EST) Subject: Re: Lock-up on PPC64 From: Benjamin Herrenschmidt To: malc In-Reply-To: References: <20081222233223.GA6688@joi> <877i5rh9rm.fsf@linmac.oyster.ru> <20081223234513.GA8730@deepthought> <871vvy77v4.fsf@linmac.oyster.ru> <1230165163.7292.32.camel@pasglop> <1231158516.8367.3.camel@localhost> <1231243373.14860.24.camel@pasglop> Content-Type: text/plain Date: Wed, 07 Jan 2009 08:17:23 +1100 Message-Id: <1231276643.14860.30.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > As you wish :) I've written some ad-hoc stuff in the failing path which > manually triggers sysrq and then sends the klogctl output via network > and here it is: Allright, something's unclear to me. What do you mean by the system goes down then ? The kernel appears to be working at least to a certain extent if you manage to trigger a sysrq from userspace... And from what I see, it looks that all processes are somewhere in schedule. So what is precisely your symptom here ? Cheers, Ben.