Linux bluetooth development
 help / color / mirror / Atom feed
From: Russell Neches <russell@ccs.neu.edu>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] crash on remove
Date: Wed, 10 Mar 2004 13:21:58 -0500	[thread overview]
Message-ID: <20040310182158.GA9279@naginata.ccs.neu.edu> (raw)


Sorry if this is mildly off-topic...

Every time I remove a bluetooth USB key from my desktop machine, I get
a hard lock. I've tried this with a Belkin key and D-Link key (not the
one with the Broadcom chipset). I don't even see a kernel panic in
text mode. However, my laptop (running exactly the same kernel
version) works fine on remove. So far, this only seems to happen with
bluetooth USB keys. I've tried a number of other USB devices on my
desktop, and they all remove cleanly (even after several such cycles).  
 
The desktop (where the problems are occuring) has an A-Bit motherboard
with all Via components, and has both a USB 1.1 and 2.0 controller
(I'm pretty sure I'm plugging the key into one of the 1.1 ports). 

The laptop is a Toshiba Libretto L5 with ALI components (USB 1.1). 

I'm running kernel 2.6.3 with no patches applied on both systems. 

This is most likely a module unloading bug triggered by the hotplug
event, but I figured I'd ask here first, as it is bluetooth related.
If anyone else has a similar hardware combination, would you mind
attempting to remove the key a couple of times? (occasionally the
desktop will only freeze after the second unload)

Does anyone have any strategies for extracting some debugging
information? I've not played with SysReq or tracebacks, so I'm not
sure if they'd help in this case.

Thanks,

Russell



-------------------------------------------------------
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

             reply	other threads:[~2004-03-10 18:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 18:21 Russell Neches [this message]
2004-03-10 21:12 ` [Bluez-users] crash on remove 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   ` [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=20040310182158.GA9279@naginata.ccs.neu.edu \
    --to=russell@ccs.neu.edu \
    --cc=bluez-users@lists.sourceforge.net \
    /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