public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Stuart Pook <linux-bluetooth4@pook.es>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump
Date: Sun, 5 Apr 2009 20:22:12 +0300	[thread overview]
Message-ID: <20090405172212.GB6612@jh-x301> (raw)
In-Reply-To: <49D8E48A.2060807@pook.es>

On Sun, Apr 05, 2009, Stuart Pook wrote:
> here I am replying to myself
>
> On 05/04/09 14:02, Stuart Pook wrote:
>> I tried it again with bluez 4.34 and now a simple "hcitool scan" makes 
>> bluetoothd core dump.
>
> I have just noticed that I've been getting kernel errors with all this
> plugging and unplugging of Bluetooth adapters.

I don't know about the kernel, but there's a known bug with 4.34 that can make
bluetoothd crash when unpluging/repluging adapters. This was fixed in git
already several days ago with commit 457056310229911e820357470ee8fb30c82516da
("Fix org.bluez.Audio unregistration") so you might want to try if it helps.

Johan

  reply	other threads:[~2009-04-05 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05 12:02 bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Stuart Pook
2009-04-05 17:04 ` Stuart Pook
2009-04-05 17:22   ` Johan Hedberg [this message]
2009-04-19 19:19     ` bluez git + Linksys USBBT100 + 2.6.30-rc2 -> Segmentation fault Stuart Pook
2009-04-19 20:05       ` Johan Hedberg
2009-04-19 21:12         ` Stuart Pook
2009-04-19 21:38           ` Johan Hedberg
2009-04-19 22:05             ` Stuart Pook
2009-04-20 17:45             ` Stuart Pook
2009-04-05 17:19 ` bluez 4.34 + Linksys USBBT100 + hcitool scan -> core dump Johan Hedberg
2009-04-06 21:20   ` Stuart Pook

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=20090405172212.GB6612@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth4@pook.es \
    --cc=linux-bluetooth@vger.kernel.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