From: David Daney <ddaney@caviumnetworks.com>
To: Andreas Barth <aba@not.so.argh.org>
Cc: Peter 'p2' De Schrijver <p2@debian.org>, linux-mips@linux-mips.org
Subject: Re: movidis x16 hard lockup using 2.6.33
Date: Mon, 29 Mar 2010 09:54:02 -0700 [thread overview]
Message-ID: <4BB0DB2A.9080405@caviumnetworks.com> (raw)
In-Reply-To: <20100327230744.GG27216@mails.so.argh.org>
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.
David Daney
next prev parent reply other threads:[~2010-03-29 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 18:41 movidis x16 hard lockup using 2.6.33 Peter 'p2' De Schrijver
2010-03-26 18:57 ` David Daney
2010-03-26 19:05 ` Peter 'p2' De Schrijver
2010-03-27 23:07 ` Andreas Barth
2010-03-29 16:54 ` David Daney [this message]
2010-03-29 22:02 ` Andreas Barth
2010-03-29 22:13 ` David Daney
2010-03-29 22:23 ` Andreas Barth
2010-04-02 13:32 ` Andreas Barth
2010-04-03 15:43 ` Peter 'p2' De Schrijver
2010-04-15 18:43 ` irqbalance on movidis crashes the machine (was: movidis x16 hard lockup using 2.6.33) Andreas Barth
2010-04-15 20:35 ` Andreas Barth
2010-04-25 13:54 ` Andreas Barth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB0DB2A.9080405@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=aba@not.so.argh.org \
--cc=linux-mips@linux-mips.org \
--cc=p2@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox