Messages in this thread Patch in this message | | | Date | Fri, 13 Apr 2001 16:16:58 -0400 (EDT) | From | Rod Stewart <> | Subject | Re: 8139too: defunct threads |
| |
On Thu, 12 Apr 2001, Andrew Morton wrote: > 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?
I found the difference which causes this. If I build my kernel with IP_PNP (IP: kernel level autoconfiguration) support I get a defunt thread for each 8139too device. If I don't build with IP_PNP support I don't get any, defunct ethernet threads.
This make any sense? Here is the relevant diff from a working config to a bad one: [root@stewart-nw34 conf]# diff -u config-p5-good config-p6-bad --- config-p5-good Fri Apr 13 16:07:10 2001 +++ config-p6-bad Fri Apr 13 16:12:21 2001 @@ -173,7 +173,9 @@ # CONFIG_IP_ROUTE_TOS is not set # CONFIG_IP_ROUTE_VERBOSE is not set # CONFIG_IP_ROUTE_LARGE_TABLES is not set -# CONFIG_IP_PNP is not set +CONFIG_IP_PNP=y +# CONFIG_IP_PNP_BOOTP is not set +# CONFIG_IP_PNP_RARP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m # CONFIG_NET_IPGRE_BROADCAST is not set
Thanks, -Rms
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |