From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: How to debug hard lockup issue
Date: Thu, 2 Aug 2012 10:34:13 +0200 [thread overview]
Message-ID: <20120802083413.GH10670@pengutronix.de> (raw)
In-Reply-To: <CAF1ivSZ=mHqPOks9vdWhb--gKduWpM6UM77-mMj=1gAf8P6MUA@mail.gmail.com>
On Thu, Aug 02, 2012 at 03:59:36PM +0800, Lin Ming wrote:
> On Thu, Aug 2, 2012 at 3:15 PM, Uwe Kleine-K?nig
> <u.kleine-koenig@pengutronix.de> wrote:
> > Hello,
> >
> > On Thu, Aug 02, 2012 at 11:03:31AM +0800, Lin Ming wrote:
> >> I encountered a hard lockup on a armv5 board with 2.6.32 kernel.
> >> There is no any message output since it is hard lockup.
> >>
> >> I tried watchdog, but watchdog can only reset the board. I still can't
> >> get any info.
> >>
> >> The hard lockup is possibly because kernel blocked/looped with
> >> interrupts disabled.
> >>
> >> Is there any non-maskable interrupt I can use to dump the kernel stack?
> >> Or any other hint?
> > Try enabling various debug options. The following come to (my) mind:
> >
> > CONFIG_DETECT_HUNG_TASK
> > CONFIG_PROVE_LOCKING
> > CONFIG_DEBUG_ATOMIC_SLEEP
> > CONFIG_MAGIC_SYSRQ
>
> These debug options are already enabled.
> But it doesn't help.
then if you don't have a hardware debugger handy you can try
https://lkml.org/lkml/2012/5/26/83
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2012-08-02 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 3:03 How to debug hard lockup issue Lin Ming
2012-08-02 7:15 ` Uwe Kleine-König
2012-08-02 7:59 ` Lin Ming
2012-08-02 8:34 ` Uwe Kleine-König [this message]
2012-08-02 9:30 ` Lin Ming
2012-08-02 9:40 ` Jassi Brar
2012-08-03 1:23 ` Lin Ming
2012-08-02 8:28 ` Jassi Brar
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=20120802083413.GH10670@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).