From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Russell King" <rmk@arm.linux.org.uk>, "Greg KH" <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test5 vs. Ethernet cards
Date: Wed, 17 Sep 2003 23:27:55 +0900 [thread overview]
Message-ID: <0d5201c37d28$02128d80$63ee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20030916182059.D20141@flint.arm.linux.org.uk
"Russell King" wrote:
> On Tue, Sep 16, 2003 at 09:49:41AM -0700, Greg KH wrote:
> > On Sun, Sep 14, 2003 at 09:17:02AM +0100, Russell King wrote:
> > > On Sun, Sep 14, 2003 at 12:51:29PM +0900, Norman Diamond wrote:
> > > > 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
> > > > [...]
> > > > The only way to shut down at this point is to turn off the power.
> > >
> > > IIRC the problem is your hotplug scripts. Maybe the hotplug folk can
> > > tell you the minimum version for 2.6.
> >
> > The last release version is the best for 2.6, but this doesn't look
> > like a hotplug script issue at all.
>
> Hmm, ok. However, in the past when people have upgraded their hotplug
> scripts, the problem goes away.
It will be a while before I have time to try it, sorry. SuSE 8.2 is
partially installed on that machine now and one day next weekend will
probably finish just that.
> Whatever, it's certainly not a PCMCIA issue either, so I'm at a loss what
> to do about these reports.
> I can only think that the right answer is to bat them all at the netdev
> list, since it is a network device issue.
Stephen Hemminger sent private e-mail guessing that IPV6 bugs might be the
cause. I did select a number of IPV6 options when building
2.6.0-test[1..5]. Sorry I don't remember if my 2.4.19 included any IPV6
support, and I'm not planning to try a regression test to that one. I'll
try to find time some weekend to experiment with 2.6.0-test5 and
2.4.20-SuSE8.2 with and without IPV6.
I don't have access to IPV6 at present but figure I will someday, and if I
ever have time to experiment with it then the experimentation time will not
be wasted. Most of the world (except for North America) will not be able to
survive without IPV6.
prev parent reply other threads:[~2003-09-17 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 3:51 2.6.0-test5 vs. Ethernet cards Norman Diamond
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 [this message]
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='0d5201c37d28$02128d80$63ee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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