public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Russell Neches <russell@ccs.neu.edu>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem with kernel-2.6.5
Date: Fri, 23 Apr 2004 09:29:35 +0200	[thread overview]
Message-ID: <1082705375.23959.93.camel@pegasus> (raw)
In-Reply-To: <20040423071748.GC6531@heliopause.vort.org>

Hi Russel,

> I also get a crash when removing USB Bluetooth keys, but I've had that
> problem with all 2.6 kernels. 
> 
> You can see the first insert and remove events, which did not cause a
> crash, followed the oops. I figured I'd post to coroborate the issue Tim
> is having. 

actually I hope that the upcoming 2.6.6-rc3 will fix all of these
problems. If not, then ask the USB guys for a patch.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-04-23  7:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  3:27 [Bluez-users] Problem with kernel-2.6.5 Timothy Murphy
2004-04-21 12:32 ` Marcel Holtmann
2004-04-21 19:44   ` Nicholas A. Preyss
2004-04-21 19:22     ` Marcel Holtmann
2004-04-21 20:48   ` Timothy Murphy
2004-04-21 13:09 ` Nicholas A. Preyss
2004-04-23  7:17 ` Russell Neches
2004-04-23  7:23   ` Russell Neches
2004-04-23  7:29   ` Marcel Holtmann [this message]
2004-04-23 19:47     ` Russell Neches

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=1082705375.23959.93.camel@pegasus \
    --to=marcel@holtmann.org \
    --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