Messages in this thread | | | Date | Mon, 29 Oct 2001 18:10:29 -0500 | Subject | 8139too termination | From | Robert Kuebel <> |
| |
hi,
i have been getting this message at shutdown ...
"eth1: unable to signal thread"
it turns out that 8139too's kernel thread gets killed at shutdown (or reboot) when SIGTERM is sent to all processes. then the network shutdown script comes along and takes down the interface. the driver complains ...
"eth1: unable to signal thread"
because the thread has already terminated. the driver currently does not block any signals.
my question is, should 8139too really not block any signals (and allow itself to be killed by them)? isn't it a bad thing to allow a kernel thread to be killed accidentally like this?
give me some feedback. i would be happy to write a fix.
also, please cc me on replies. i can only handle the digest form of lkml.
thanks. rob.
- 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/
| |