public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Matthew Harrell  <mharrell-dated-1054584482.d18b3b@bittwiddlers.com>
Cc: Gregory Maxwell <greg@xiph.org>,
	Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Orinoco_cs module won't unload in 2.5.70
Date: Thu, 29 May 2003 11:59:09 +1000	[thread overview]
Message-ID: <20030529015909.GA2058@zax> (raw)
In-Reply-To: <20030528200755.GA1460@bittwiddlers.com>

On Wed, May 28, 2003 at 04:08:01PM -0400, Matthew Harrell wrote:
> 
> Nothing useful.  I've got this problem in a 2.5.65 kernel also.  Really is
> annoyying since the machine will not soft reboot because it thinks that
> device is still in use.  I have to physically power it off every time I 
> want to reboot it change any major pcmcia settings

Yes, it's a driver bug - one of a number that I've fixed recently.
I'll retransmit the patch to Linus today.

> > Kernel 2.5.70 (and 2.5.69-mm8 before it) on my Dell Latitude C840 is
> > unable to unload the orinoco_cs driver.
> > 
> > I get the following message over and over again while the rmmod hangs:
> > unregister_netdevice: waiting for eth1 to become free. Usage count = 1
> > 
> > Even after ifconfig downing the interface..
> > 
> > This is quite annoying because the driver doesn't survive suspend and I
> > can't cleanly shutdown. :)
> > 
> > Suggestions?
> 

-- 
David Gibson			| For every complex problem there is a
david@gibson.dropbear.id.au	| solution which is simple, neat and
				| wrong.
http://www.ozlabs.org/people/dgibson

      reply	other threads:[~2003-05-29  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 15:41 Orinoco_cs module won't unload in 2.5.70 Gregory Maxwell
2003-05-28 20:08 ` Matthew Harrell
2003-05-29  1:59   ` David Gibson [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=20030529015909.GA2058@zax \
    --to=david@gibson.dropbear.id.au \
    --cc=greg@xiph.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharrell-dated-1054584482.d18b3b@bittwiddlers.com \
    /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