From: Brad Midgley <bmidgley@xmission.com>
To: Russell Neches <russell@ccs.neu.edu>, bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] crash on remove
Date: Wed, 10 Mar 2004 17:41:53 -0700 [thread overview]
Message-ID: <404FB5D1.5030104@xmission.com> (raw)
In-Reply-To: <20040310223504.GA3398@omocha.vort.org>
Russell
>>safely remove a usb adapter is to stop the bluetooth daemons, force
>>remove hci_usb (there always seems to be one reference pinning it down
>>that I can't find), then unplug the adapter.
>
>
> Do you have to do a force remove, or will it unload cleanly?
>
> What do you mean by a "reference"? Does it claim to be in use when you
> you rmmod it?
yes, i enabled force remove because the module shows up as in use. i
think it's unsafe, but how much worse can it be than crashing the kernel?
i am compiling the modules without SCO support right now to see if that
helps.
brad
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-03-11 0:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:21 [Bluez-users] crash on remove Russell Neches
2004-03-10 21:12 ` Brad Midgley
2004-03-10 22:35 ` Russell Neches
2004-03-10 22:46 ` Simone Gotti
2004-03-10 23:41 ` Russell Neches
2004-03-11 0:11 ` Simone Gotti
2004-03-11 0:38 ` Russell Neches
2004-03-11 0:41 ` Brad Midgley [this message]
2004-03-11 2:47 ` Russell Neches
2004-03-11 9:32 ` Matthias Thomae
2004-03-13 15:26 ` Simone Gotti
2004-03-15 13:21 ` [Bluez-devel] " Dirk Husemann
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=404FB5D1.5030104@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=russell@ccs.neu.edu \
/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