From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jongman.heo@samsung.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: How to debug system freeze (not detected by kernel debug options)
Date: Fri, 9 Nov 2012 11:08:07 +0000 [thread overview]
Message-ID: <20121109110807.3e09fcfc@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <574089.21861352427573311.JavaMail.weblogic@epml01>
On Fri, 09 Nov 2012 02:19:33 +0000 (GMT)
Jongman Heo <jongman.heo@samsung.com> wrote:
>
> Dear kernel hackers,
>
> I have a problem in SMP environment, in x86 platform (Intel Atom based embedded system)
>
> In UP, there is no issue, but in SMP, system freezed in tens of minutes (or shorter), if I perform IO test with flash memory and HDD simultaneously (using dd).
>
> I enabled relevant kernel debug options, like LOCKDEP, DETECT_SOFTLOCKUP, DETECT_HUNG_TASK, along with "nmi_watchdog=1".
> (Yeah, this is somewhat old kernel, 2.6.35.14).
>
> But no debug message is shown. (I had checked that NMI interrupt count correctly increase.).
>
> Do you have any thoughts what can cause system freeze without being detected by LOCKDEP, watchdog, and other options.
Hardware problems, firmware bugs, PATA controller hangs, some
classes of PCI device hang, certain cases where for some reason the crash
is so bad the kernel can't get the message out even though it has detected
the failure.
A good starting point is probably "can you make two identical systems do
it". If you've got a pair of boards which fed the same software set and
have the same flash and hdd crash in the same way its unlikely to be a
faulty board.
You may find it useful to make the NMI timeout handler trigger a directly
detectable event via an I/O port if your platform has a buzzer or LED
directly I/O mapped somewhere.
Failing that the fastest approach may be to use hardware debugging aids
if you have access to them for that platform.
Alan
prev parent reply other threads:[~2012-11-09 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 2:19 How to debug system freeze (not detected by kernel debug options) Jongman Heo
2012-11-09 11:08 ` Alan Cox [this message]
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=20121109110807.3e09fcfc@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jongman.heo@samsung.com \
--cc=linux-kernel@vger.kernel.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