From: Anton Blanchard <anton@samba.org>
To: "David Laight" <David.Laight@ACULAB.COM>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/4] powerpc: Enable lockup and hung task detectors in pseriesand ppc64 defeconfigs
Date: Wed, 20 Jul 2011 09:46:40 +1000 [thread overview]
Message-ID: <20110720094640.5c2145a5@kryten> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8ADE3@saturn3.aculab.com>
Hi David,
> > As a result of changes to Kconfig files, we no longer enable
> > the lockup and hung task detectors. Both are very light weight
> > and provide useful information in the event of a hang, so
> > reenable them.
> ...
> > +CONFIG_LOCKUP_DETECTOR=y
> > +CONFIG_DETECT_HUNG_TASK=y
>
> Is one of thise responsible for generating a kernel stack traceback
> when a process has been sleeping uninterruptably for a 'long' time?
>
> We have a kernel subsystem that has several 'worker' threads,
> these always sleep uninterruptable (they are shut down by explicit
> request) and, at times, can be idle for long periods.
>
> Perhaps it should be possible to disable the check either on
> a per-process of per sleep basis?
I don't see any runtime options other than disabling it completely via:
/proc/sys/kernel/hung_task_timeout_secs
Anton
prev parent reply other threads:[~2011-07-19 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 23:13 [PATCH 0/4] Some defconfig updates Anton Blanchard
2011-07-06 23:13 ` [PATCH 1/4] powerpc: Sync pseries and ppc64 defconfigs Anton Blanchard
2011-07-06 23:13 ` [PATCH 2/4] powerpc: Disable IRQs off tracer in ppc64 defconfig Anton Blanchard
2011-07-06 23:13 ` [PATCH 3/4] powerpc: Add mpt2sas driver to pseries and " Anton Blanchard
2011-07-06 23:13 ` [PATCH 4/4] powerpc: Enable lockup and hung task detectors in pseries and ppc64 defeconfigs Anton Blanchard
2011-07-07 7:46 ` [PATCH 4/4] powerpc: Enable lockup and hung task detectors in pseriesand " David Laight
2011-07-19 23:46 ` Anton Blanchard [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=20110720094640.5c2145a5@kryten \
--to=anton@samba.org \
--cc=David.Laight@ACULAB.COM \
--cc=linuxppc-dev@ozlabs.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).