From: Robert Kuebel <kuebelr@email.uc.edu>
To: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: 8139too termination
Date: Mon, 29 Oct 2001 18:10:29 -0500 [thread overview]
Message-ID: <20011029181029.A320@cartman> (raw)
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.
next reply other threads:[~2001-10-29 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 23:10 Robert Kuebel [this message]
2001-10-29 23:27 ` 8139too termination Andrew Morton
2001-10-30 0:08 ` Robert Kuebel
[not found] ` <3BDDF4B0.194E132F@zip.com.au>
2001-10-30 0:58 ` Robert Kuebel
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=20011029181029.A320@cartman \
--to=kuebelr@email.uc.edu \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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