linux-kernel - Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Apr 2011 07:00:28 -0400
From:	Ed Tomlinson <edt@....ca>
To:	Dave Young <hidave.darkstar@...il.com>
Cc:	Hui Zhu <teawater@...il.com>, linux-kernel@...r.kernel.org,
	Bluettooth Linux <linux-bluetooth@...r.kernel.org>
Subject: Re: [BUG] bluetooth doesn't work from 2.6.39-rc1+ to 2.6.39-rc3+

On Tuesday 26 April 2011 22:55:22 Dave Young wrote:
> On Sun, Apr 24, 2011 at 9:52 PM, Ed Tomlinson <edt@....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@...il.com> wrote:
> >> > On Tue, Apr 19, 2011 at 10:53 AM, Hui Zhu <teawater@...il.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.

I can try but this bug was introduced during the .38 to rc1 window.  I've not had much luck
bisecting through pre rc1...

Is there any good way to trace what is giving the 'Invalid argument 22'?  

Ed
 
> >
> > 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
> >
> 
> 
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/