From: george anzinger <george@mvista.com>
To: Philippe Troin <phil@fifi.org>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, Amol Lad <dal_loma@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: kill task in TASK_UNINTERRUPTIBLE
Date: Wed, 08 May 2002 16:27:11 -0700 [thread overview]
Message-ID: <3CD9B44F.4A023A70@mvista.com> (raw)
In-Reply-To: <20020508140124.79124.qmail@web12408.mail.yahoo.com> <200205081519.g48FJEX24062@Port.imtp.ilyichevsk.odessa.ua> <87znzawpk9.fsf@ceramic.fifi.org>
Philippe Troin wrote:
>
> Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> writes:
>
> > On 8 May 2002 12:01, Amol Lad wrote:
> > > Hi,
> > > Is there any way i can kill a task in
> > > TASK_UNINTERRUPTIBLE state ?
> >
> > No. Everytime you see hung task in this state
> > you see kernel bug.
> >
> > Somebody correct me if I am wrong.
>
> Except for processes accessing NFS files while the NFS server is down:
> they will be stuck in TASK_UNINTERRUPTIBLE until the NFS server comes
> back up again.
A REALLY good argument for puting timeouts on your NSF mounts! Don't
leave home without them.
-g
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-05-08 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 14:01 kill task in TASK_UNINTERRUPTIBLE Amol Lad
2002-05-08 20:23 ` Denis Vlasenko
2002-05-08 16:43 ` Robert Love
2002-05-08 16:51 ` Philippe Troin
2002-05-08 23:27 ` george anzinger [this message]
2002-05-08 23:49 ` Roman Zippel
2002-05-10 20:47 ` Jan Hudec
2002-05-09 15:18 ` Denis Vlasenko
2002-05-09 17:39 ` Andrew Theurer
2002-05-08 18:33 ` Alan Cox
2002-05-09 9:47 ` David Woodhouse
2002-05-09 15:21 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2002-05-09 18:00 Kerl, John
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=3CD9B44F.4A023A70@mvista.com \
--to=george@mvista.com \
--cc=dal_loma@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@fifi.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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