mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems with PCMCIA/Orinoco
Date: Tue, 17 Jun 2003 12:25:45 +0200	[thread overview]
Message-ID: <20030617102545.GB6353@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0306171159470.1854-100000@blackstar.nl>

[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]

On Tue, 2003-06-17 12:01:40 +0200, bvermeul@blackstar.nl <bvermeul@blackstar.nl>
wrote in message <Pine.LNX.4.44.0306171159470.1854-100000@blackstar.nl>:
> On Tue, 17 Jun 2003, Russell King wrote:
> > On Tue, Jun 17, 2003 at 11:29:00AM +0200, 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.
> > > 
> > > I'm not sure what causes this, and it's started somewhere in 2.5.70 bk.
> > 
> > I believe this is a netdevice problem and isn't anything to do with
> > PCMCIA or Cardbus.  If the net people would like to confirm this, it'd
> > be most helpful.
> 
> I'm also using a RTL8139 cardbus card, and that does not show this 
> particular problem (works great actually).
> So I'm not so sure it is a netdevice problem. It may be a orinoco
> problem, but I'm not entirely sure what's causing it.
> Just wanted to see if anyone's noticed it as well, and if a fix was
> out there.

I'm not sure, but for what I *see* (using a PCMCIA NE2000 clone with my
Laptop) this problem occures by this:

- Insert your card (after "/etc/init.d/pcmcia-cs start" is done, that
  card will be recognized and configured).
- shutdown your laptop. This involves "/etc/init.d/pcmcia-cs stop".
- _Later on_ (after the card should already have gone away because
  you've just stopped the pcmcia subsystem), "/etc/init.d/networking
  stop" tried to "ifconfig ethX down" the card - Bang.

The cardbus/hotplug stuff might be different here. I think this is
solely a problem of the pure PCMCIA stuff...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-17 10:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-17  9:29 bvermeul
2003-06-17  9:55 ` Russell King
2003-06-17 10:01   ` bvermeul
2003-06-17 10:25     ` Jan-Benedict Glaw [this message]
2003-06-17 13:19     ` John M Flinchbaugh
2003-06-17 15:52     ` David S. Miller
2003-06-17 15:52     ` David S. Miller
2003-06-23  9:38 ` Russell King
2003-06-23 13:37   ` Jan-Benedict Glaw
2003-06-23 17:27     ` Jan-Benedict Glaw
2003-06-24  0:59   ` John M Flinchbaugh
2003-06-24  9:50     ` Bas Vermeulen

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=20030617102545.GB6353@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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®