linux-mips
[Top] [All Lists]

Re: movidis x16 hard lockup using 2.6.33

To: David Daney <ddaney@caviumnetworks.com>
Subject: Re: movidis x16 hard lockup using 2.6.33
From: Andreas Barth <aba@not.so.argh.org>
Date: Tue, 30 Mar 2010 00:02:23 +0200
Cc: Peter 'p2' De Schrijver <p2@debian.org>, linux-mips@linux-mips.org
In-reply-to: <4BB0DB2A.9080405@caviumnetworks.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20100326184132.GU2437@apfelkorn> <4BAD03A5.9070701@caviumnetworks.com> <20100327230744.GG27216@mails.so.argh.org> <4BB0DB2A.9080405@caviumnetworks.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
* David Daney (ddaney@caviumnetworks.com) [100329 18:54]:
> On 03/27/2010 04:07 PM, Andreas Barth wrote:
>> * David Daney (ddaney@caviumnetworks.com) [100326 19:57]:
>>> Also you could try running with the attached patch.  It is not the best
>>> watchdog, but it will print the register state for each core when things
>>> get stuck.  Occasionally that is enough to see where the problem is.
>>
>> Thanks.
>>
>> As our logging has only limited buffer size, I'd be happy about an
>> variant of the patch which doesn't reboot but just let the machine
>> hang after the third occurence.
>>
>> Any chances for it?

> You could just sit in a loop kicking the watchdog timer after you get to  
> the NMI handler.  That should prevent a reset, but still print the  
> machine state.

I need to admit that I'm totally unable to make code from that
statement.


Could you (or someone else) give me a hand? Also please note that it
usually takes a few hours to crash the machine, and I didn't see
anything in the normal syslog.


Andi

<Prev in Thread] Current Thread [Next in Thread>