From: Andrew Morton <andrewm@uow.edu.au>
To: Rod Stewart <stewart@dystopia.lab43.org>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: 8139too: defunct threads
Date: Thu, 12 Apr 2001 13:38:48 -0700 [thread overview]
Message-ID: <3AD61258.4E8567D8@uow.edu.au> (raw)
In-Reply-To: <3AD5F9FE.9A49374D@uow.edu.au> <Pine.LNX.4.33.0104121530470.31525-100000@dystopia.lab43.org>
Rod Stewart wrote:
>
> On Thu, 12 Apr 2001, Andrew Morton wrote:
> > Rod Stewart wrote:
> > >
> > > Hello,
> > >
> > > Using the 8139too driver, 0.9.15c, we have noticed that we get a defunct
> > > thread for each device we have; if the driver is built into the kernel.
> > > If the driver is built as a module, no defunct threads appear.
> >
> > What is the parent PID for the defunct tasks? zero?
>
> According to ps, 1
Ah. Of course. All (or most) kernel initialisation is
done by PID 1. Search for "kernel_thread" in init/main.c
So it seems that in your setup, process 1 is not reaping
children, which is why this hasn't been reported before.
Is there something unusual about your setup?
next prev parent reply other threads:[~2001-04-12 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 17:58 8139too: defunct threads Rod Stewart
2001-04-12 18:54 ` Andrew Morton
2001-04-12 19:32 ` Alan Cox
2001-04-12 20:18 ` Andrew Morton
2001-04-12 21:15 ` Alan Cox
2001-04-12 19:37 ` Rod Stewart
2001-04-12 20:38 ` Andrew Morton [this message]
2001-04-12 21:23 ` Rod Stewart
2001-04-12 21:30 ` Andrew Morton
2001-04-12 21:33 ` Rod Stewart
2001-04-13 20:16 ` Rod Stewart
2001-04-12 22:19 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-14 14:00 Manfred Spraul
2001-04-14 16:21 ` Rod Stewart
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=3AD61258.4E8567D8@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stewart@dystopia.lab43.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