From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Soete Subject: Re: [parisc-linux] c3k panics Date: Sun, 29 May 2005 10:32:16 +0000 Message-ID: <42999A30.6070602@tiscali.be> References: <200505290141.j4T1ffhI006449@hiauly1.hia.nrc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: parisc-linux@lists.parisc-linux.org To: John David Anglin Return-Path: In-Reply-To: <200505290141.j4T1ffhI006449@hiauly1.hia.nrc.ca> List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: parisc-linux-bounces@lists.parisc-linux.org John David Anglin wrote: > I can panic my c3750 very consistently running the binutils testsuite > (cvs source as of 20050526). mmm the experimental debian bintuils-2.16 seems to works fine for me (kernel 2.6.8.1-pa11 32bit on a b180). > I've tried many of the default kernels > to see if I could isolate when the problem was introduced. The last > kernel that seems unaffected is 2.6.8.1-pa11. The problem is present > in 2.6.12-rc5-pa0 and 2.6.11-pa4. > I observe the same differences of behaviour. Btw, that looks like the pb I encountered many times when I tried CONFIG_DEBUG_SLAB=y? As I tried to explain in detail () there is a big pb with this option. Unfortunately, I am not a C programer and so lake of deep knowledges to suggest a proper fix :-( If it's your case too, can you try without this option. (or give a try to this patch attempt: . it's not perfect but it helps me anyway :-) ). > The sad part is that panic is also broken and no error messages are > produced when the fault occurs. Before adding panic=180 to the command > line, pressing TOC just yielded a register dump for panic itself. That's > not too useful. In my testing, the last working panic dump was with > 2.6.9-pa1 which faulted with a HPMC during boot. > The same for me, it seems that the pb appears during 2.6.9 developement; as far as I can test, it seems that the pb appears between 2.6.9-rc2-pa2 and pa5; For my part I already tried to revert only this pa5 (just to be sure) but it doesn't help :-) So still have to revert few thing (but it would be hard like fixup stuff) to try to isolate the pb? Ah still a question: is it the same pb for 32bit and 64bit twin kernel? Thanks, Joel _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/mailman/listinfo/parisc-linux