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 0CA37DDDF0 for ; Mon, 23 Feb 2009 09:43:34 +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> <1231276643.14860.30.camel@pasglop> Content-Type: text/plain Date: Mon, 23 Feb 2009 09:42:45 +1100 Message-Id: <1235342565.8805.216.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: , On Sun, 2009-02-22 at 11:35 +0300, malc wrote: > After writing valgrind tool that was simulating Cell XER.SO syscall > (mis)behaviour (pre ab598b6680f1e74c267d1547ee352f3e1e530f89 that is) > and banging my had against the wall for a while trying to figure out > which of the failing syscalls was responsible, i've tried to be simple > and after only ~30 minutes came up with this, rather short, piece of > code that knocks pre XER.SO patched kernels out cold: > > gcc -o xer -x assembler /dev/stdin -nostdlib < .globl _start > _start: > addis 0,0,0x8000 > mtxer 0 > addi 0,0,1 > sc Allright, but the XER patch fixes it... interesting. Oh well, I'll try to figure out at some stage where we get something wrong in those old kernels. Cheers, Ben.