From: Johan Hedberg <johan.hedberg@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth disabled with current 2.6.38-rc4
Date: Tue, 15 Feb 2011 10:52:45 -0300 [thread overview]
Message-ID: <20110215135245.GA11561@jh-x301> (raw)
In-Reply-To: <1A8743E5-65EA-4625-82FD-658C9722629F@gmail.com>
Hi Justin,
On Sun, Feb 13, 2011, Justin Mattock wrote:
> maybe I missed something, but my bluetooth is just not functioning with
> 2.6.38-rc4(works with 2.6.37-rc4)
>
> I've done a bisect on this, but was pointed to:
> c0e45c1ca3162acb2e77b3d9e152ce6e7b6fa3f5
> but doesn't look correct to me
>
> here is what I am seeing with the bluetooth-applet etc..:
>
> working correctly:
> http://www.flickr.com/photos/44066293@N08/5443727238/
>
> not working:
> http://www.flickr.com/photos/44066293@N08/5443124859/
>
> my /var/log/daemon.log shows:
>
> Feb 13 17:12:22 Linux-2 acpid: 1 client rule loaded
> Feb 13 17:12:23 Linux-2 bluetoothd[1950]: HCI dev 0 registered
> Feb 13 17:12:23 Linux-2 bluetoothd[1950]: Listening for HCI events
> on hci0
> Feb 13 17:12:23 Linux-2 bluetoothd[1950]: HCI dev 0 up
> Feb 13 17:12:23 Linux-2 bluetoothd[1950]: Unable to find matching
> adapter
>
> I can try at another bisect, but might take some time.. let me know
> if there is something I can test
> or do.
Are you sure this is a kernel problem? There was a similar issue with
BlueZ 4.86 or 4.87 which was already fixed. Could you try with 4.88?
Johan
next prev parent reply other threads:[~2011-02-15 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 1:30 bluetooth disabled with current 2.6.38-rc4 Justin Mattock
2011-02-15 13:52 ` Johan Hedberg [this message]
2011-02-15 16:20 ` Justin Mattock
2011-02-16 3:26 ` Justin Mattock
2011-02-16 13:34 ` Gustavo F. Padovan
2011-02-16 15:34 ` Justin Mattock
2011-02-16 19:35 ` Gustavo F. Padovan
2011-02-17 5:19 ` Justin Mattock
2011-02-18 19:09 ` Justin Mattock
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=20110215135245.GA11561@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=justinmattock@gmail.com \
--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