From: Dirk Husemann <hud@zurich.ibm.com>
To: bluez-devel@lists.sourceforge.net
Cc: Brad Midgley <bmidgley@xmission.com>,
Russell Neches <russell@ccs.neu.edu>,
bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-devel] Re: [Bluez-users] crash on remove
Date: Mon, 15 Mar 2004 14:21:54 +0100 [thread overview]
Message-ID: <200403151421.58685.hud@zurich.ibm.com> (raw)
In-Reply-To: <404F84BC.4020406@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Wednesday 10 March 2004 22.12, Brad Midgley (BM) wrote:
> Russell
>
> > Every time I remove a bluetooth USB key from my desktop machine, I get
> > a hard lock.
same thing here. haven't tried the forced usb_hci removal...
--
Dr Dirk Husemann, Mobile Computing, IBM Research, Zurich Research Lab
hud@zurich.ibm.com --- http://www.zurich.ibm.com/~hud/
PGP key: http://www.zurich.ibm.com/~hud/contact/PGP
PGP Fingerprint: 983C 48E7 0A78 A313 401C C4AD 3C0A 278E 6431 A149
Email only authentic if signed with PGP key.
Attached to this email is an electronic signature attachment. You can
ignore it if your email program does not know how to verify such a
signature. If you'd like to learn more about this topic, www.gnupg.org
is a good starting point.
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-03-15 13:21 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
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 ` Dirk Husemann [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=200403151421.58685.hud@zurich.ibm.com \
--to=hud@zurich.ibm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-users@lists.sourceforge.net \
--cc=bmidgley@xmission.com \
--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