public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maciej <maciej@killer-robot.net>
To: linux-kernel@vger.kernel.org
Subject: orinoco_cs module removal problem
Date: Wed, 4 Jun 2003 12:51:21 -0500	[thread overview]
Message-ID: <20030604175121.GA1709@apathy.black-flower> (raw)

I just switched from 2.5.68 to 2.5.70, and I'm having trouble removing
the orinoco_cs module on the fly. After bringing the interface down,
doing an "rmmod orinoco_cs" causes the rmmod process to lock up, and
subseqeunt invocations of lsmod and 'cat /proc/modules' to do the same.
I get a bunch of messages like the following in the kernel log:

"unregister_netdevice: waiting for eth2 to become free. Usage count = 1

However, eth2, the orinoco device, no longer exists (it's not listed
in /proc/net/dev).

                             	 Maciej Babinski

             reply	other threads:[~2003-06-04 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 17:51 Maciej [this message]
2003-06-04 18:25 ` orinoco_cs module removal problem John M Flinchbaugh
2003-06-05  3:17 ` David Gibson

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=20030604175121.GA1709@apathy.black-flower \
    --to=maciej@killer-robot.net \
    --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