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

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

Well, at least things are improving. When I started the previous thread
about this back in March (subject: crash on remove, I think), the
machine would completely lock, and I'd never see a panic or an oops.
Now, I get an oops, and the machine keeps running. So, I guess that's
progress!

In any event, that's my desktop (VIA chipset). The solution, for the
time being, is simply not to remove the Bluetooth key.  Everything has
always worked fine on my laptop (ALi chipset). You know the old joke:

	Patient:	Doctor! It hurts when I do this!
	
	* Patient does something
	
	Doctor:		Well, don't do that!

Russell

      reply	other threads:[~2004-04-23 19:47 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
2004-04-23 19:47     ` Russell Neches [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=20040423194749.GA8699@omocha.vort.org \
    --to=russell@ccs.neu.edu \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.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