mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar@gmail.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: Hui Zhu <teawater@gmail.com>,
	linux-kernel@vger.kernel.org,
	Bluettooth Linux <linux-bluetooth@vger.kernel.org>
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+
Date: Wed, 27 Apr 2011 10:55:22 +0800	[thread overview]
Message-ID: <BANLkTim-49ZdSLnyjs_kjLxuvyCe=oUdGA@mail.gmail.com> (raw)
In-Reply-To: <201104240952.14848.edt@aei.ca>

On Sun, Apr 24, 2011 at 9:52 PM, Ed Tomlinson <edt@aei.ca> wrote:
> On Tuesday 19 April 2011 11:34:30 Hui Zhu wrote:
>> Do you part is OK?
>>
>> I think it will be very easy to reproduce.
>>
>> Thanks,
>> Hui
>>
>> On Tue, Apr 19, 2011 at 15:46, Dave Young <hidave.darkstar@gmail.com> wrote:
>> > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <teawater@gmail.com> wrote:
>> >> Cannot connect to any outside devices through bluetooth.
>> >>
>> >> And I think this is not a bug of low level driver.  Because both my
>> >> laptop and a usb bluetooth card cannot work.
>> >
>> > Hi, please explain the "cannot work" in detail,
>> > Firstly check dmesg and hciconfig to see if there's anything wrong.
>
> I am also seeing problems with bluetooth in .39-rc4+
>
> [54511.033258] usb 2-4.4: USB disconnect, device number 5
> [54513.920060] usb 2-4.3: new full speed USB device number 6 using ehci_hcd
> [54514.063057] usb 2-4.3: New USB device found, idVendor=0a12, idProduct=0001
> [54514.070281] usb 2-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> grover ~ # hciconfig -a
> hci0:   Type: BR/EDR  Bus: USB
>        BD Address: 00:0A:3A:55:07:5A  ACL MTU: 192:8  SCO MTU: 64:8
>        DOWN
>        RX bytes:718 acl:0 sco:0 events:25 errors:0
>        TX bytes:108 acl:0 sco:0 commands:24 errors:0
>        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>        Link policy: CONFIG_BT_HCIBTUSB=m
>        Link mode: SLAVE ACCEPT
>
> grover ~ # hciconfig hci0 up
> Can't init device hci0: Invalid argument (22)
>
> The same error happens If I just try a hciconfig hci0 up after boot (without replugging the adaptor).

I did not see your problem, my usb dongle usbid is 0a12:0001 as well,
maybe bisect is the way to go.

>
> CONFIG_BT_HCIBTSDIO=m
> CONFIG_BT_HCIUART=m
> CONFIG_BT_HCIUART_H4=y
> CONFIG_BT_HCIUART_BCSP=y
> # CONFIG_BT_HCIUART_ATH3K is not set
> CONFIG_BT_HCIUART_LL=y
> CONFIG_BT_HCIBCM203X=m
> CONFIG_BT_HCIBPA10X=m
> CONFIG_BT_HCIBFUSB=m
> CONFIG_BT_HCIVHCI=m
>
> and bluez-4.91 is installed
>
> Ideas?
> Ed Tomlinson
>



-- 
Regards
dave

  parent reply	other threads:[~2011-04-27  2:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19  2:53 Hui Zhu
2011-04-19  3:05 ` Wanlong Gao
2011-04-19  5:11   ` Hui Zhu
2011-04-19  7:26     ` wanlong gao
2011-05-05 12:44   ` Milan Oravec
2011-04-19  7:46 ` Dave Young
2011-04-19 15:34   ` Hui Zhu
2011-04-24 13:52     ` Ed Tomlinson
2011-04-26 16:13       ` Gustavo F. Padovan
2011-04-27 10:57         ` Ed Tomlinson
2011-04-27  2:55       ` Dave Young [this message]
2011-04-27 11:00         ` Ed Tomlinson
2011-04-30 10:14 ` Milan Oravec

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='BANLkTim-49ZdSLnyjs_kjLxuvyCe=oUdGA@mail.gmail.com' \
    --to=hidave.darkstar@gmail.com \
    --cc=edt@aei.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teawater@gmail.com \
    /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

all inboxes | Powered by JetHome®