From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test5 vs. Ethernet cards
Date: Sun, 14 Sep 2003 12:51:29 +0900 [thread overview]
Message-ID: <1b7201c37a73$844b7030$2dee4ca5@DIAMONDLX60> (raw)
When trying to do a shutdown or reboot while an Ethernet card is present,
2.6.0-test5 continues to have problems which earlier 2.6.0-test versions
had, which can be solved by booting 2.4.19.
Shutdown messages appear on the text console as follows:
[...]
Shutting down PCMCIA unregister_netdevice: waiting for eth0 to become free.
Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
[...]
The only way to shut down at this point is to turn off the power.
An alternative workaround is to manually type "ifconfig eth0 down" before
trying to shut down or reboot. This takes a certain amount of activation of
human memory at the moment just before shutting down, and I have not been up
to the task. Since this step was not necessary under 2.4.19, it is easier
to boot 2.4.19 instead.
Command "/etc/rc.d/pcmcia restart" suffers the same as a shutdown or reboot.
Again similarly, in 2.4.19 it works.
next reply other threads:[~2003-09-14 3:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 3:51 Norman Diamond [this message]
2003-09-14 8:17 ` Russell King
2003-09-14 10:45 ` Norman Diamond
2003-09-14 23:07 ` Russell King
2003-09-16 16:49 ` Greg KH
2003-09-16 17:20 ` Russell King
2003-09-17 14:27 ` Norman Diamond
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='1b7201c37a73$844b7030$2dee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--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
all inboxes | Powered by JetHome®