From: Russell King <rmk@arm.linux.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: rol@as2917.net, cfriesen@nortelnetworks.com, paulus@samba.org,
linux-kernel@vger.kernel.org, linux-ppp@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: [BUG]: problem when shutting down ppp connection since 2.5.70
Date: Mon, 30 Jun 2003 09:23:37 +0100 [thread overview]
Message-ID: <20030630092337.B32593@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030630.010337.74723316.davem@redhat.com>; from davem@redhat.com on Mon, Jun 30, 2003 at 01:03:37AM -0700
On Mon, Jun 30, 2003 at 01:03:37AM -0700, David S. Miller wrote:
> From: Russell King <rmk@arm.linux.org.uk>
> Date: Mon, 30 Jun 2003 09:05:07 +0100
>
> People with PCMCIA cards have been reporting the same thing. It sounds
> like something's up with the netdev layer, and it has persisted until
> 2.5.73 thus far.
>
> If there are bugs in pcmcia drivers, they are _really_ going to show
> now. The change is that 'rmmod' is allowed even if the device is
> "up". We don't grab/drop module reference counts when the device is
> brought up/down. We simply "down" up net devices at
> unregister_netdevice() time.
>
> So if a device is racey, it's going to be "really" racey now.
>
> If people mention which devices give the problems (with current
> kernels, we've fixed a lot of bugs as of late) the drivers can
> be audited for register/unregister bugs.
The thread I replied to is about pppoe devices, so it isn't limited to
PCMCIA, although that seems to be the most popular subset which causes
the problem.
Chris Friesen <cfriesen@nortelnetworks.com> wrote:
> Summary:
> On 2.5.70 and later kernels, shutting down a pppoe connection causes
> pppd to hang and results in a usage count stuck at 1.
John M Flinchbaugh <glynis@butterfly.hjsoft.com> wrote:
> i still see it with both my 3c574_cs and my orinoco_cs in 2.5.73.
bvermeul@blackstar.nl wrote:
> I'm having some problems with 2.5.71 (latest bk yesterday I believe).
> All works well (pcmcia works as advertised, with one tiny blip on
> the horizon), except when I want to reboot, when I get the following
> message:
>
> unregister_netdevice: waiting for eth1 to become free. Usage count = 1
>
> The net device is an Orinoco mini-pci card (eg, cardbus minipci interface
> with built-in orinoco card), and it is down.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-06-30 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 2:35 [BUG]: problem when shutting down ppp connection since 2.5.70 Chris Friesen
2003-06-30 6:07 ` Paul Rolland
2003-06-30 8:05 ` Russell King
2003-06-30 8:03 ` David S. Miller
2003-06-30 8:23 ` Russell King [this message]
2003-06-30 8:42 ` Paul Rolland
2003-06-30 11:18 ` Paul Mackerras
2003-06-30 11:36 ` Paul Mackerras
2003-06-30 14:02 ` Chris Friesen
2003-06-30 15:37 ` Stephen Hemminger
2003-06-30 16:41 ` Chris Friesen
2003-07-01 2:26 ` Chris Friesen
2003-07-03 5:17 ` Chris Friesen
2003-07-06 9:43 ` Paul Rolland
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=20030630092337.B32593@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cfriesen@nortelnetworks.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rol@as2917.net \
/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