All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: undertow <undertow@dexcom.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible bug
Date: Tue, 1 Oct 2002 18:37:43 +0200	[thread overview]
Message-ID: <20021001163743.GA275@DervishD> (raw)
In-Reply-To: <1033487088.2369.6.camel@aenima>

    Hi Eduardo :)

> Im spannish user of linux, I have detected an error on my distro
> and I ask to local average users and told me that prob. is a kernel
> bug.

    I'm spanish, too ;)) But let's go to the matter: probably the PID
you're trying to 'kill -9' is stuck in 'D' state (or any other
uninterruptible state), so it's not a kernel bug ;) If this is not
the case, you may have hit a kernel bug.

> but I read that a kill -)
> command MUST finnish the running task

    AFAIK this is not exact ;) The 'SIGKILL' signal (that is, 9),
cannot be trapped and so its action cannot be changed. Moreover, it
is unblockable, so it's always 'fatal' ;))) it is always *sent*. This
doesn't mean that the process will die. If the process is in any
uninterruptible state, it won't be interrupted!. You will have to
wait until the process is woken up and then it will die.

    The more probable state, in my experience, is the 'D' state,
which if I remember well, is something like 'disk sleep', waiting for
disk i/o, etc...

> Normaly the freeze task
> is edonkey or overnet.

    Oh... The eDonkey client... AFAIK, this is closed source, so any
problem related to this client is difficult (if not impossible) to
catch...

    Raúl

  reply	other threads:[~2002-10-01 16:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 15:44 possible bug undertow
2002-10-01 16:37 ` DervishD [this message]
2002-10-03  1:29   ` Denis Vlasenko
2002-10-02 22:38     ` DervishD
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 19:40 Possible Bug Angelo
2009-12-08 13:18 Possible bug ml-raid
2009-12-09  1:57 ` Neil Brown
2009-12-09  9:39   ` ml-raid
2011-07-23 20:25 Reuben Thomas
2012-07-21  7:09 Ariel Norberto Bellino
2012-07-24 12:01 ` Thomas Renninger
2012-07-24 12:07   ` Jukka Ruohonen
2012-07-25  4:23     ` Ariel Norberto Bellino
2016-03-31 12:34 Possible Bug Roger H Newell
2016-03-31 14:37 ` Valdis.Kletnieks at vt.edu
     [not found]   ` <56FD5089.5070302@canonical.com>
2016-03-31 17:52     ` Valdis.Kletnieks at vt.edu
2016-03-31 18:16       ` Roger H Newell
2016-03-31 19:23         ` Valdis.Kletnieks at vt.edu
2016-03-31 20:22           ` Roger H Newell
     [not found]             ` <56FDD8D9.9010408@gmail.com>
2016-04-01 13:00               ` Roger H Newell
     [not found] ` <56FD38C4.8030201@gmail.com>
2016-03-31 15:08   ` Roger H Newell
     [not found]     ` <56FD4C35.5040301@gmail.com>
2016-03-31 16:25       ` Roger H Newell
2016-03-31 17:22         ` Valdis.Kletnieks at vt.edu
2016-03-31 16:30     ` Carlo Caione
     [not found]       ` <56FD5358.5010101@gmail.com>
2016-03-31 17:29         ` Roger H Newell
2016-03-31 18:42           ` Valdis.Kletnieks at vt.edu
2016-05-06 19:48 Possible bug David Kiarie
     [not found] ` <5d645be8-fbd0-0454-af00-baf34a2816a0@iommu.org>
     [not found]   ` <5d645be8-fbd0-0454-af00-baf34a2816a0-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-05-07  8:33     ` David Kiarie

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=20021001163743.GA275@DervishD \
    --to=raul@pleyades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=undertow@dexcom.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.