From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Debugging hung tasks?
Date: Fri, 22 Apr 2011 16:09:29 -0700 [thread overview]
Message-ID: <4DB20AA9.4080801@candelatech.com> (raw)
I am testing lots of NFS traffic against an over-loaded and slow file server.
I enabled the hung-task detection logic, and it's hitting after 180
seconds.
First: Is there any valid reason to have funky NFS cause a hung task?
Second: Why doesn't the hung-task panic logic print the stack trace of
the hung task?
Is this an option that can be enabled?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2011-04-22 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 23:09 Ben Greear [this message]
2011-04-23 3:55 ` Debugging hung tasks? Randy Dunlap
2011-04-25 17:38 ` Ben Greear
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=4DB20AA9.4080801@candelatech.com \
--to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.