linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xiyou.wangcong@gmail.com (Cong Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: In many cases softlockup can not be reported after disabling IRQ for long time
Date: Wed, 01 Feb 2012 18:51:33 +0800	[thread overview]
Message-ID: <4F291935.2030205@gmail.com> (raw)
In-Reply-To: <CAOwKts_dTvc4LiCZUXN9oYzty1pkDEn_VQwPKY=EoVzk0n6tFA@mail.gmail.com>

(Please don't top-reply.)

On 02/01/2012 10:18 AM, TAO HU wrote:
> Hi, Don
>
> Thanks for your feedback!
>
> Unfortunately, the hardlockup depends on NMI which is not available on
> ARM (Cortex-A9) per my understanding.
> Our system uses OMAP4430. Any more suggestions?

When there is no NMI, touch_nmi_watchdog() actually touches softlockup 
watchdog:

#if defined(ARCH_HAS_NMI_WATCHDOG) || defined(CONFIG_HARDLOCKUP_DETECTOR)
#include <asm/nmi.h>
extern void touch_nmi_watchdog(void);
#else
static inline void touch_nmi_watchdog(void)
{
         touch_softlockup_watchdog();
}
#endif

so you need to check if other places calling touch_nmi_watchdog() 
especially on ARM.

  reply	other threads:[~2012-02-01 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOwKts8zS1rYA+Y4k-vb8YAaR=aFd1BwryhhWWnWLQyrYrNqyA@mail.gmail.com>
     [not found] ` <20120131154748.GA5650@redhat.com>
2012-02-01  2:18   ` In many cases softlockup can not be reported after disabling IRQ for long time TAO HU
2012-02-01 10:51     ` Cong Wang [this message]
2012-02-01 14:58     ` Don Zickus
2012-02-02  8:17       ` TAO HU
2012-02-02  8:43         ` Russell King - ARM Linux
     [not found]           ` <CAOwKts--CDpmiMunfYKrYsnWovmQhAC7Vp0P-9MeNVy6vx-Wvw@mail.gmail.com>
2012-02-04 12:22             ` Russell King - ARM Linux
2012-02-02 15:58         ` Don Zickus
2012-02-02 16:22           ` Russell King - ARM Linux

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=4F291935.2030205@gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).