[BUG] usb problems in .38-rc3+

[BUG] usb problems in .38-rc3+

[Ed Tomlinson]

Hi,

My bluetooth usb dongle has stopped working in .38-rc3+

Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and in dmesg

[108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
[108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
[108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[108652.971977] usb 5-1: USB disconnect, address 3
[108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
[108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
[108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
[108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
[108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
[108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
[108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Its been working for years here.

Any ideas on what to try or additional info to gather?

TIA
Ed Tomlinson

Re: [BUG] usb problems in .38-rc3+

[Alan Stern]

On Sat, 5 Feb 2011, Ed Tomlinson wrote:

> Hi,
> 
> My bluetooth usb dongle has stopped working in .38-rc3+
> 
> Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> 
> and in dmesg
> 
> [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [108652.971977] usb 5-1: USB disconnect, address 3
> [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> 
> Its been working for years here.
> 
> Any ideas on what to try or additional info to gather?

Does it still work with earlier kernels or on other computers?

Alan Stern

Re: [BUG] usb problems in .38-rc3+

[Przemo Firszt]

Dnia 2011-02-05, sob o godzinie 15:16 -0500, Alan Stern pisze:
> On Sat, 5 Feb 2011, Ed Tomlinson wrote:
> 
> > Hi,
> > 
> > My bluetooth usb dongle has stopped working in .38-rc3+
> > 
> > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > 
> > and in dmesg
> > 
> > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > [108652.971977] usb 5-1: USB disconnect, address 3
> > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > 
> > Its been working for years here.
> > 
> > Any ideas on what to try or additional info to gather?
> 
> Does it still work with earlier kernels or on other computers?
[przemo@pldmachine ~]$ lsusb
[..]
Bus 003 Device 002: ID 03f0:011d Hewlett-Packard Integrated Bluetooth
Module
[przemo@pldmachine ~]$ uname -a
Linux pldmachine 2.6.38-rc3-00201-g44f2c5c #7 Sat Feb 5 21:42:38 GMT
2011 i686 Intel(R)_Pentium(R)_M_processor_1.86GHz PLD Linux

Works fine for me - tested with a wacom tablet. I have built-in
bluetooth and the dongle. There is something in dmesg:

usb 3-2: new full speed USB device using uhci_hcd and address 2
usb 3-2: New USB device found, idVendor=03f0, idProduct=011d
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: HP integrated Bluetooth module
usb 3-2: Manufacturer: Broadcom
intel8x0_measure_ac97_clock: measured 52706 usecs (2540 samples)
intel8x0: clocking to 48000
Adding 3068376k swap on /dev/sda1.  Priority:-1 extents:1
across:3068376k 
EXT4-fs (sda2): warning: maximal mount count reached, running e2fsck is
recommended
EXT4-fs (sda2): re-mounted. Opts: (null)
input: PS/2 Generic Mouse
as /devices/platform/i8042/serio4/serio5/input/input5
auditd (1883): /proc/1883/oom_adj is deprecated, please
use /proc/1883/oom_score_adj instead.
Bluetooth: L2CAP ver 2.15
Bluetooth: L2CAP socket layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
------------[ cut here ]------------
WARNING: at kernel/printk.c:430 do_syslog+0x347/0x36d()
Hardware name: HP Compaq nc4200 (PV983AW#ABU)  
Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG
(deprecated and denied).
Modules linked in: rfcomm bnep l2cap btusb bluetooth pcmcia ipw2200
snd_intel8x0 snd_ac97_codec libipw cfg80211 ac97_bus snd_pcm rfkill
yenta_socket tpm_infineon sdhci_pci sdhci snd_timer pcmcia_rsrc uhci_hcd
ehci_hcd mmc_core snd lib80211 tg3 pcmcia_core sg psmouse tpm container
ac usbcore fan battery processor thermal evdev soundcore snd_page_alloc
tpm_bios ata_piix libata sd_mod crc_t10dif scsi_mod ext4 mbcache jbd2
crc16 jbd [last unloaded: scsi_wait_scan]
Pid: 1993, comm: syslog-ng Not tainted 2.6.38-rc3-00201-g44f2c5c #7
Call Trace:
 [<c10195f2>] ? warn_slowpath_common+0x6a/0x7d
 [<c1019ce2>] ? do_syslog+0x347/0x36d
 [<c101966b>] ? warn_slowpath_fmt+0x28/0x2c
 [<c1019ce2>] ? do_syslog+0x347/0x36d
 [<c10c82c1>] ? smack_inode_permission+0x3b/0x42
 [<c10b4798>] ? kmsg_release+0x0/0x11
 [<c10b47b9>] ? kmsg_open+0x10/0x12
 [<c10ae32f>] ? proc_reg_open+0x63/0xc4
 [<c10c6674>] ? security_dentry_open+0x47/0x4d
 [<c10ae2cc>] ? proc_reg_open+0x0/0xc4
 [<c107c316>] ? __dentry_open+0xfb/0x1eb
 [<c107cfc8>] ? nameidata_to_filp+0x32/0x3d
 [<c10862f9>] ? finish_open+0x7f/0x11f
 [<c10867c3>] ? do_filp_open+0x16e/0x563
 [<c124a464>] ? do_page_fault+0x378/0x392
 [<c124a451>] ? do_page_fault+0x365/0x392
 [<c108db95>] ? alloc_fd+0x41/0xa5
[<c107d014>] ? do_sys_open+0x41/0xbe
 [<c107d0af>] ? sys_open+0x1e/0x23
 [<c100264c>] ? sysenter_do_call+0x12/0x22
---[ end trace 889c8d9ad011dab5 ]---
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
ADDRCONF(NETDEV_UP): lan: link is not ready
wireless: no IPv6 routers present
ata1.00: configured for UDMA/100
ata1: EH complete
blueman-applet[2631]: segfault at b7896048 ip b778e077 sp bfe08324 error
7 in libpython2.7.so.1.0[b7725000+138000]
lib80211_crypt: registered algorithm 'CCMP'
Intel AES-NI instructions are not detected.
lib80211_crypt: registered algorithm 'TKIP'
EXT4-fs (sda2): re-mounted. Opts: commit=0
hci_cmd_task: hci0 command tx timeout
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
input: WACOM Pen Tablet
as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:1/input6
wacom 0005:056A:0081.0001: input,hidraw0: BLUETOOTH HID v1.00 Mouse
[WACOM Pen Tablet] on 00:1F:81:00:08:30
hci_cmd_task: hci0 command tx timeout
hci_cmd_task: hci0 command tx timeout
hci_cmd_task: hci0 command tx timeout


-- 
Przemo Firszt

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Saturday 05 February 2011 15:16:19 Alan Stern wrote:
> On Sat, 5 Feb 2011, Ed Tomlinson wrote:
> 
> > Hi,
> > 
> > My bluetooth usb dongle has stopped working in .38-rc3+
> > 
> > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > 
> > and in dmesg
> > 
> > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > [108652.971977] usb 5-1: USB disconnect, address 3
> > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > 
> > Its been working for years here.
> > 
> > Any ideas on what to try or additional info to gather?
> 
> Does it still work with earlier kernels or on other computers?

Alan,

yes its working fine with .37 so the hw is ok.  It looks to be a change in .38 that triggered the failure.

Ed

.37 dmesg follows:

[   10.515289] usb 2-4.7: new full speed USB device using ehci_hcd and address 5
[   10.648949] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
[   10.648952] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   10.832380] Bluetooth: Core ver 2.15
[   10.832418] NET: Registered protocol family 31
[   10.832421] Bluetooth: HCI device and connection manager initialized
[   10.832425] Bluetooth: HCI socket layer initialized
[   10.871896] Bluetooth: Generic Bluetooth USB driver ver 0.6
[   10.872246] usbcore: registered new interface driver btusb
[   11.816907] input: ov519 as /devices/pci0000:00/0000:00:12.1/usb4/4-1/input/input6
[   11.817153] gspca: video0 created
[   11.817382] usbcore: registered new interface driver usbserial_generic
[   11.817385] usbserial: USB Serial Driver core
[   11.818128] usbcore: registered new interface driver ov519
[   11.820102] USB Serial support registered for pl2303
[   11.820200] pl2303 5-3:1.0: PL-2303 hack: descriptors matched but endpoints did not
[   11.820234] pl2303 5-3:1.1: pl2303 converter detected
[   11.841717] usb 5-3: pl2303 converter now attached to ttyUSB0
[   11.841742] usbcore: registered new interface driver pl2303
[   11.841745] pl2303: Prolific PL2303 USB to serial adaptor driver
[   28.477896] sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
[   28.477900] cdrom: Uniform CD-ROM driver Revision: 3.20
[   28.478226] sr 6:0:0:0: Attached scsi CD-ROM sr0
[   30.195117] powernow-k8: Found 1 AMD Phenom(tm) II X4 940 Processor (4 cpu cores) (version 2.20.00)
[   30.195167] powernow-k8:    0 : pstate 0 (3000 MHz)
[   30.195169] powernow-k8:    1 : pstate 1 (2300 MHz)
[   30.195172] powernow-k8:    2 : pstate 2 (1800 MHz)
[   30.195174] powernow-k8:    3 : pstate 3 (800 MHz)
[   30.899098] EXT4-fs (sdb3): re-mounted. Opts: (null)
[   31.194619] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null)
[   33.673078] Bluetooth: L2CAP ver 2.15
[   33.673090] Bluetooth: L2CAP socket layer initialized
[   33.727139] Bluetooth: RFCOMM TTY layer initialized
[   33.727168] Bluetooth: RFCOMM socket layer initialized
[   33.727177] Bluetooth: RFCOMM ver 1.11
[   33.814213] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   33.814223] Bluetooth: BNEP filters: protocol multicast
[   33.861898] Bluetooth: SCO (Voice Link) ver 0.6
[   33.861907] Bluetooth: SCO socket layer initialized
[   35.600125] sky2 0000:02:00.0: eth0: enabling interface
[   36.103536] Adding 5986300k swap on /dev/sdc2.  Priority:-1 extents:1 across:5986300k 
[   36.116190] Adding 1020120k swap on /dev/sda2.  Priority:-2 extents:1 across:1020120k 
[   37.355836] NET: Registered protocol family 10
[   37.357093] lo: Disabled Privacy Extensions
[   37.357355] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   38.198205] sky2 0000:02:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both
[   38.203688] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   47.727778] IPv6 over IPv4 tunneling driver
[   47.728551] sit0: Disabled Privacy Extensions
[   47.761803] tun: Universal TUN/TAP device driver, 1.6
[   47.761813] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   48.434301] eth0: no IPv6 routers present
[   48.960936] sixxs: Disabled Privacy Extensions
[   79.568088] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   79.593964] input: Apple Wireless Mouse as /devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4.7/2-4.7:1.0/bluetooth/hci0/hci0:41/input7
[   79.595105] magicmouse 0005:05AC:030D.0004: input,hidraw3: BLUETOOTH HID v0.84 Mouse [Apple Wireless Mouse] on 00:0A:3A:55:07:5A

Re: [BUG] usb problems in .38-rc3+

[Oliver Neukum]

Am Samstag, 5. Februar 2011, 20:17:57 schrieb Ed Tomlinson:
> Hi,
> 
> My bluetooth usb dongle has stopped working in .38-rc3+
> 
> Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> 
> and in dmesg
> 
> [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [108652.971977] usb 5-1: USB disconnect, address 3
> [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> 
> Its been working for years here.
> 
> Any ideas on what to try or additional info to gather?

Please test what happens if you disable runtime power management.

	Regards
		Oliver

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Monday 07 February 2011 04:09:51 Oliver Neukum wrote:
> Am Samstag, 5. Februar 2011, 20:17:57 schrieb Ed Tomlinson:
> > Hi,
> > 
> > My bluetooth usb dongle has stopped working in .38-rc3+
> > 
> > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > 
> > and in dmesg
> > 
> > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > [108652.971977] usb 5-1: USB disconnect, address 3
> > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > 
> > Its been working for years here.
> > 
> > Any ideas on what to try or additional info to gather?
> 
> Please test what happens if you disable runtime power management.

After a pointer from Oliver I booted with usbcore.autosuspend=30000 and verified the device used
the parm via /sys/bus...   Still did not work.  Bisect or are there some other things to try?

Thanks
Ed

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Monday 07 February 2011 19:20:21 Ed Tomlinson wrote:
> On Monday 07 February 2011 04:09:51 Oliver Neukum wrote:
> > Am Samstag, 5. Februar 2011, 20:17:57 schrieb Ed Tomlinson:
> > > Hi,
> > > 
> > > My bluetooth usb dongle has stopped working in .38-rc3+
> > > 
> > > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > > 
> > > and in dmesg
> > > 
> > > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > [108652.971977] usb 5-1: USB disconnect, address 3
> > > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > 
> > > Its been working for years here.
> > > 
> > > Any ideas on what to try or additional info to gather?
> > 
> > Please test what happens if you disable runtime power management.
> 
> After a pointer from Oliver I booted with usbcore.autosuspend=30000 and verified the device used
> the parm via /sys/bus...   Still did not work.  Bisect or are there some other things to try?

I tried bisecting without much luck.  It started with about 4000 commits to check.  It was still bad
when it reached the first 1000 commits post .37.  Then all boots started crashing.  I think its possible
to restrict a bisect to a directory - if so, what dir should I try?

TIA
Ed

Re: [BUG] usb problems in .38-rc3+

[Gadiyar, Anand]

On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> I tried bisecting without much luck.  It started with about 4000 commits to check.  It was still bad
> when it reached the first 1000 commits post .37.  Then all boots started crashing.  I think its possible
> to restrict a bisect to a directory - if so, what dir should I try?
>

Maybe drivers/ or drivers/usb would be enough for a first attempt?
I usually start there.

You could just do:

git bisect start -- [path]

to restrict bisection to commits that touch [path].

- Anand

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Tuesday 08 February 2011 01:46:16 Gadiyar, Anand wrote:
> On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > I tried bisecting without much luck.  It started with about 4000 commits to check.  It was still bad
> > when it reached the first 1000 commits post .37.  Then all boots started crashing.  I think its possible
> > to restrict a bisect to a directory - if so, what dir should I try?
> >
> 
> Maybe drivers/ or drivers/usb would be enough for a first attempt?
> I usually start there.
> 
> You could just do:
> 
> git bisect start -- [path]
> 
> to restrict bisection to commits that touch [path].

This is as far as I can get:

# bad: [100b33c8bd8a3235fd0b7948338d6cbb3db3c63d] Linux 2.6.38-rc4
# good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37
# good: [387c31c7e5c9805b0aef8833d1731a5fe7bdea14] Linux 2.6.37-rc8
# good: [90a8a73c06cc32b609a880d48449d7083327e11a] Linux 2.6.37-rc7
# good: [c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4] Linux 2.6.37-rc1
git bisect start 'v2.6.38-rc4' 'v2.6.37' 'v2.6.37-rc8' 'v2.6.37-rc7' 'v2.6.37-rc1' '--' 'drivers/usb' 'drivers/bluetooth'
# good: [5cdc5bd8b2b1190cb54548c03194b154b4892e2a] Merge branch 'musb-hw' of git://gitorious.org/usb/usb into musb
git bisect good 5cdc5bd8b2b1190cb54548c03194b154b4892e2a
# bad: [f2c565e223af39ed38be5c84b1a37b591b22db83] xHCI: replace dev_dbg() with xhci_dbg()
git bisect bad f2c565e223af39ed38be5c84b1a37b591b22db83
# good: [2af10844eb6ed104f9505bf3a7ba3ceb02264f31] USB: Merge 2.6.37-rc5 into usb-next
git bisect good 2af10844eb6ed104f9505bf3a7ba3ceb02264f31
# bad: [3e5b08cbbf78bedd316904ab0cf3b27119433ee5] Merge branch 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
git bisect bad 3e5b08cbbf78bedd316904ab0cf3b27119433ee5
# good: [1051b9f0f9eab8091fe3bf98320741adf36b4cfa] Merge branch 'for-rmk' of git://git.pengutronix.de/git/imx/linux-2.6 into devel-stable
git bisect good 1051b9f0f9eab8091fe3bf98320741adf36b4cfa

After this the kernel does not build.

Any clues?
Ed

RE: [BUG] usb problems in .38-rc3+

[Anand Gadiyar]

Ed Tomlinson wrote:
> On Tuesday 08 February 2011 01:46:16 Gadiyar, Anand wrote:
> > On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > > I tried bisecting without much luck.  It started with about 4000
commits to check.  It was still bad
> > > when it reached the first 1000 commits post .37.  Then all boots
started crashing.  I think its possible
> > > to restrict a bisect to a directory - if so, what dir should I try?
> > >
> >
> > Maybe drivers/ or drivers/usb would be enough for a first attempt?
> > I usually start there.
> >
> > You could just do:
> >
> > git bisect start -- [path]
> >
> > to restrict bisection to commits that touch [path].
>
> This is as far as I can get:
>
> # bad: [100b33c8bd8a3235fd0b7948338d6cbb3db3c63d] Linux 2.6.38-rc4
> # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37
> # good: [387c31c7e5c9805b0aef8833d1731a5fe7bdea14] Linux 2.6.37-rc8
> # good: [90a8a73c06cc32b609a880d48449d7083327e11a] Linux 2.6.37-rc7
> # good: [c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4] Linux 2.6.37-rc1
> git bisect start 'v2.6.38-rc4' 'v2.6.37' 'v2.6.37-rc8' 'v2.6.37-rc7'
'v2.6.37-rc1' '--' 'drivers/usb' 'drivers/bluetooth'
> # good: [5cdc5bd8b2b1190cb54548c03194b154b4892e2a] Merge branch
'musb-hw' of git://gitorious.org/usb/usb into musb
> git bisect good 5cdc5bd8b2b1190cb54548c03194b154b4892e2a
> # bad: [f2c565e223af39ed38be5c84b1a37b591b22db83] xHCI: replace
dev_dbg() with xhci_dbg()
> git bisect bad f2c565e223af39ed38be5c84b1a37b591b22db83
> # good: [2af10844eb6ed104f9505bf3a7ba3ceb02264f31] USB: Merge 2.6.37-rc5
into usb-next
> git bisect good 2af10844eb6ed104f9505bf3a7ba3ceb02264f31
> # bad: [3e5b08cbbf78bedd316904ab0cf3b27119433ee5] Merge branch
'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> git bisect bad 3e5b08cbbf78bedd316904ab0cf3b27119433ee5
> # good: [1051b9f0f9eab8091fe3bf98320741adf36b4cfa] Merge branch
'for-rmk' of git://git.pengutronix.de/git/imx/linux-2.6 into devel-stable
> git bisect good 1051b9f0f9eab8091fe3bf98320741adf36b4cfa
>
> After this the kernel does not build.
>
> Any clues?

Is it easier to just fix the build break locally and proceed?

I'm afraid I don't know how to skip a step during bisection.
I try narrowing things down manually.

Given that 2.6.37 is fine, can you check if v2.6.38-rc1 works?
If it doesn't work, then this break was caused by something that
went in during the merge window (which I believe is most likely).

You may be able to get somewhere by using snapshots of
linux-next as of particular days. They are available at [1]
as a single patch against a tag from Linus' tree.

Warning: This could be tedious, maybe not much more than a
git-bisect. Maybe easier to try and work it out from the
code.


- Anand

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Wednesday 09 February 2011 01:17:40 Anand Gadiyar wrote:
> Ed Tomlinson wrote:
> > On Tuesday 08 February 2011 01:46:16 Gadiyar, Anand wrote:
> > > On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > > > I tried bisecting without much luck.  It started with about 4000
> commits to check.  It was still bad
> > > > when it reached the first 1000 commits post .37.  Then all boots
> started crashing.  I think its possible
> > > > to restrict a bisect to a directory - if so, what dir should I try?
> > > >
> > >
> > > Maybe drivers/ or drivers/usb would be enough for a first attempt?
> > > I usually start there.
> > >
> > > You could just do:
> > >
> > > git bisect start -- [path]
> > >
> > > to restrict bisection to commits that touch [path].
> >
> > This is as far as I can get:
> >
> > # bad: [100b33c8bd8a3235fd0b7948338d6cbb3db3c63d] Linux 2.6.38-rc4
> > # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37
> > # good: [387c31c7e5c9805b0aef8833d1731a5fe7bdea14] Linux 2.6.37-rc8
> > # good: [90a8a73c06cc32b609a880d48449d7083327e11a] Linux 2.6.37-rc7
> > # good: [c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4] Linux 2.6.37-rc1
> > git bisect start 'v2.6.38-rc4' 'v2.6.37' 'v2.6.37-rc8' 'v2.6.37-rc7'
> 'v2.6.37-rc1' '--' 'drivers/usb' 'drivers/bluetooth'
> > # good: [5cdc5bd8b2b1190cb54548c03194b154b4892e2a] Merge branch
> 'musb-hw' of git://gitorious.org/usb/usb into musb
> > git bisect good 5cdc5bd8b2b1190cb54548c03194b154b4892e2a
> > # bad: [f2c565e223af39ed38be5c84b1a37b591b22db83] xHCI: replace
> dev_dbg() with xhci_dbg()
> > git bisect bad f2c565e223af39ed38be5c84b1a37b591b22db83
> > # good: [2af10844eb6ed104f9505bf3a7ba3ceb02264f31] USB: Merge 2.6.37-rc5
> into usb-next
> > git bisect good 2af10844eb6ed104f9505bf3a7ba3ceb02264f31
> > # bad: [3e5b08cbbf78bedd316904ab0cf3b27119433ee5] Merge branch
> 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> > git bisect bad 3e5b08cbbf78bedd316904ab0cf3b27119433ee5
> > # good: [1051b9f0f9eab8091fe3bf98320741adf36b4cfa] Merge branch
> 'for-rmk' of git://git.pengutronix.de/git/imx/linux-2.6 into devel-stable
> > git bisect good 1051b9f0f9eab8091fe3bf98320741adf36b4cfa
> >
> > After this the kernel does not build.
> >
> > Any clues?
> 
> Is it easier to just fix the build break locally and proceed?
> 
> I'm afraid I don't know how to skip a step during bisection.
> I try narrowing things down manually.
> 
> Given that 2.6.37 is fine, can you check if v2.6.38-rc1 works?
> If it doesn't work, then this break was caused by something that
> went in during the merge window (which I believe is most likely).
> 
> You may be able to get somewhere by using snapshots of
> linux-next as of particular days. They are available at [1]
> as a single patch against a tag from Linus' tree.
> Warning: This could be tedious, maybe not much more than a
> git-bisect. Maybe easier to try and work it out from the
> code.

one interesting point.  Its NOT 

3e5b08cbbf78bedd316904ab0cf3b27119433ee5 Merge branch 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6

Building a kernel with the merge preceeding this one (da40d036fd716f0efb2917076220814b1e927ae1) still has the problem.  

One other symptom I've noticed.  With .37 kde 4.5/6's bluedevil bluetooth control sees the adapter, 
with the failing post .37 kernels it does not.

Thanks,
Ed

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Wednesday 09 February 2011 01:17:40 Anand Gadiyar wrote:
> Ed Tomlinson wrote:
> > On Tuesday 08 February 2011 01:46:16 Gadiyar, Anand wrote:
> > > On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> > > > I tried bisecting without much luck.  It started with about 4000
> commits to check.  It was still bad
> > > > when it reached the first 1000 commits post .37.  Then all boots
> started crashing.  I think its possible
> > > > to restrict a bisect to a directory - if so, what dir should I try?
> > > >
> > >
> > > Maybe drivers/ or drivers/usb would be enough for a first attempt?
> > > I usually start there.
> > >
> > > You could just do:
> > >
> > > git bisect start -- [path]
> > >
> > > to restrict bisection to commits that touch [path].
> >
> > This is as far as I can get:
> >
> > # bad: [100b33c8bd8a3235fd0b7948338d6cbb3db3c63d] Linux 2.6.38-rc4
> > # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37
> > # good: [387c31c7e5c9805b0aef8833d1731a5fe7bdea14] Linux 2.6.37-rc8
> > # good: [90a8a73c06cc32b609a880d48449d7083327e11a] Linux 2.6.37-rc7
> > # good: [c8ddb2713c624f432fa5fe3c7ecffcdda46ea0d4] Linux 2.6.37-rc1
> > git bisect start 'v2.6.38-rc4' 'v2.6.37' 'v2.6.37-rc8' 'v2.6.37-rc7'
> 'v2.6.37-rc1' '--' 'drivers/usb' 'drivers/bluetooth'
> > # good: [5cdc5bd8b2b1190cb54548c03194b154b4892e2a] Merge branch
> 'musb-hw' of git://gitorious.org/usb/usb into musb
> > git bisect good 5cdc5bd8b2b1190cb54548c03194b154b4892e2a
> > # bad: [f2c565e223af39ed38be5c84b1a37b591b22db83] xHCI: replace
> dev_dbg() with xhci_dbg()
> > git bisect bad f2c565e223af39ed38be5c84b1a37b591b22db83
> > # good: [2af10844eb6ed104f9505bf3a7ba3ceb02264f31] USB: Merge 2.6.37-rc5
> into usb-next
> > git bisect good 2af10844eb6ed104f9505bf3a7ba3ceb02264f31
> > # bad: [3e5b08cbbf78bedd316904ab0cf3b27119433ee5] Merge branch
> 'usb-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6
> > git bisect bad 3e5b08cbbf78bedd316904ab0cf3b27119433ee5
> > # good: [1051b9f0f9eab8091fe3bf98320741adf36b4cfa] Merge branch
> 'for-rmk' of git://git.pengutronix.de/git/imx/linux-2.6 into devel-stable
> > git bisect good 1051b9f0f9eab8091fe3bf98320741adf36b4cfa
> >
> > After this the kernel does not build.
> >
> > Any clues?
> 
> Is it easier to just fix the build break locally and proceed?
> 
> I'm afraid I don't know how to skip a step during bisection.
> I try narrowing things down manually.
> 
> Given that 2.6.37 is fine, can you check if v2.6.38-rc1 works?
> If it doesn't work, then this break was caused by something that
> went in during the merge window (which I believe is most likely).
> 
> You may be able to get somewhere by using snapshots of
> linux-next as of particular days. They are available at [1]
> as a single patch against a tag from Linus' tree.
> 
> Warning: This could be tedious, maybe not much more than a
> git-bisect. Maybe easier to try and work it out from the
> code.

I am not having much luck bisecting or using daily snapshots.  They either
do not build or opps during boot....

The latest round of usb fixes (67d019528e5c2693145217cf18a507689980d2a4) from 
Greg did not help 

How else can we track this down?

Ed

Re: [BUG] usb problems in .38-rc3+

[Gustavo F. Padovan]

Hi Ed,

* Ed Tomlinson <edt@aei.ca> [2011-02-05 14:17:57 -0500]:

> Hi,
> 
> My bluetooth usb dongle has stopped working in .38-rc3+
> 
> Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> 
> and in dmesg
> 
> [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> [108652.971977] usb 5-1: USB disconnect, address 3
> [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> 
> Its been working for years here.
> 
> Any ideas on what to try or additional info to gather?

What's the symptom? what do you mean by stopped to work?

Can you provide me output of "hciconfig -a"?

And if possible enable dynamic debug for your kernel, mount the debugfs 
and then

echo -n "module btusb +p" > /sys/kernel/debug/dynamic_debug/control
echo -n "module bluetooth +p" > /sys/kernel/debug/dynamic_debug/control

-- 
Gustavo F. Padovan
http://profusion.mobi

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Wednesday 16 February 2011 09:00:53 Gustavo F. Padovan wrote:
> Hi Ed,
> 
> * Ed Tomlinson <edt@aei.ca> [2011-02-05 14:17:57 -0500]:
> 
> > Hi,
> > 
> > My bluetooth usb dongle has stopped working in .38-rc3+
> > 
> > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > 
> > and in dmesg
> > 
> > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > [108652.971977] usb 5-1: USB disconnect, address 3
> > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > 
> > Its been working for years here.
> > 
> > Any ideas on what to try or additional info to gather?
> 
> What's the symptom? what do you mean by stopped to work?

With .37 kernel my bluetooth apple magicmouse is detected at boot and works as expected & when 
kde 4.6 is active bluedevil sees my bluetooth adaptor.  With .38-rc my bluetooth mouse is not detected
nor does bluedevil see the bluetooth adaptor.

> Can you provide me output of "hciconfig -a"?
This gives nothing when the doogle is not plugged (it runs but prints out nothing).

> And if possible enable dynamic debug for your kernel, mount the debugfs 
> and then
> 
> echo -n "module btusb +p" > /sys/kernel/debug/dynamic_debug/control
> echo -n "module bluetooth +p" > /sys/kernel/debug/dynamic_debug/control

Hey a new debug option to enable!  With it enabled and the system booted with the bluetooth doogle
unpluged here is what happens when it gets plugged (with 38-rc5):

grover ed # hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:0A:3A:55:07:5A  ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING 
        RX bytes:356 acl:0 sco:0 events:13 errors:0
        TX bytes:53 acl:0 sco:0 commands:13 errors:0
        Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DH1 HV1 
        Link policy: 
        Link mode: SLAVE ACCEPT 
        Name: 'grover-0'
        Class: 0x000000
        Service Classes: Unspecified
        Device Class: Miscellaneous, 
        HCI Version: 1.1 (0x1)  Revision: 0x20d
        LMP Version: 1.1 (0x1)  Subversion: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)

and the device works.  So either enabling dynamic debug, something between rc4 and rc5 or booting with the
adaptor unplugged makes things work.  Will do some more checking to figure out which.

Thanks,
Ed 

Re: [BUG] usb problems in .38-rc3+

[Gustavo F. Padovan]

Hi Ed,

* Ed Tomlinson <edt@aei.ca> [2011-02-16 13:38:00 -0500]:

> On Wednesday 16 February 2011 09:00:53 Gustavo F. Padovan wrote:
> > Hi Ed,
> > 
> > * Ed Tomlinson <edt@aei.ca> [2011-02-05 14:17:57 -0500]:
> > 
> > > Hi,
> > > 
> > > My bluetooth usb dongle has stopped working in .38-rc3+
> > > 
> > > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > > 
> > > and in dmesg
> > > 
> > > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > [108652.971977] usb 5-1: USB disconnect, address 3
> > > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > 
> > > Its been working for years here.
> > > 
> > > Any ideas on what to try or additional info to gather?
> > 
> > What's the symptom? what do you mean by stopped to work?
> 
> With .37 kernel my bluetooth apple magicmouse is detected at boot and works as expected & when 
> kde 4.6 is active bluedevil sees my bluetooth adaptor.  With .38-rc my bluetooth mouse is not detected
> nor does bluedevil see the bluetooth adaptor.
> 
> > Can you provide me output of "hciconfig -a"?
> This gives nothing when the doogle is not plugged (it runs but prints out nothing).
> 
> > And if possible enable dynamic debug for your kernel, mount the debugfs 
> > and then
> > 
> > echo -n "module btusb +p" > /sys/kernel/debug/dynamic_debug/control
> > echo -n "module bluetooth +p" > /sys/kernel/debug/dynamic_debug/control
> 
> Hey a new debug option to enable!  With it enabled and the system booted with the bluetooth doogle
> unpluged here is what happens when it gets plugged (with 38-rc5):
> 
> grover ed # hciconfig -a
> hci0:   Type: BR/EDR  Bus: USB
>         BD Address: 00:0A:3A:55:07:5A  ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING 
>         RX bytes:356 acl:0 sco:0 events:13 errors:0
>         TX bytes:53 acl:0 sco:0 commands:13 errors:0
>         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DH1 HV1 
>         Link policy: 
>         Link mode: SLAVE ACCEPT 
>         Name: 'grover-0'
>         Class: 0x000000
>         Service Classes: Unspecified
>         Device Class: Miscellaneous, 
>         HCI Version: 1.1 (0x1)  Revision: 0x20d
>         LMP Version: 1.1 (0x1)  Subversion: 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)
> 
> and the device works.  So either enabling dynamic debug, something between rc4 and rc5 or booting with the
> adaptor unplugged makes things work.  Will do some more checking to figure out which.

Great that it is working now. It might be a usb bug that you had, because we
had no changes in the Bluetooth subsystem between rc4 and rc5.

But does booting with the adapter work as well?

-- 
Gustavo F. Padovan
http://profusion.mobi

Re: [BUG] usb problems in .38-rc3+

[Ed Tomlinson]

On Sunday 20 February 2011 12:09:20 Ed Tomlinson wrote:
> On Wednesday 16 February 2011 13:47:27 Gustavo F. Padovan wrote:
> > Hi Ed,
> > 
> > * Ed Tomlinson <edt@aei.ca> [2011-02-16 13:38:00 -0500]:
> > 
> > > On Wednesday 16 February 2011 09:00:53 Gustavo F. Padovan wrote:
> > > > Hi Ed,
> > > > 
> > > > * Ed Tomlinson <edt@aei.ca> [2011-02-05 14:17:57 -0500]:
> > > > 
> > > > > Hi,
> > > > > 
> > > > > My bluetooth usb dongle has stopped working in .38-rc3+
> > > > > 
> > > > > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > > > > 
> > > > > and in dmesg
> > > > > 
> > > > > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > > > > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > > > > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > > > [108652.971977] usb 5-1: USB disconnect, address 3
> > > > > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > > > > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > > > > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > > > > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > > > > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > > > > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > > > > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > > > 
> > > > > Its been working for years here.
> > > > > 
> > > > > Any ideas on what to try or additional info to gather?
> > > > 
> > > > What's the symptom? what do you mean by stopped to work?
> > > 
> > > With .37 kernel my bluetooth apple magicmouse is detected at boot and works as expected & when 
> > > kde 4.6 is active bluedevil sees my bluetooth adaptor.  With .38-rc my bluetooth mouse is not detected
> > > nor does bluedevil see the bluetooth adaptor.
> > > 
> > > > Can you provide me output of "hciconfig -a"?
> > > This gives nothing when the doogle is not plugged (it runs but prints out nothing).
> > > 
> > > > And if possible enable dynamic debug for your kernel, mount the debugfs 
> > > > and then
> > > > 
> > > > echo -n "module btusb +p" > /sys/kernel/debug/dynamic_debug/control
> > > > echo -n "module bluetooth +p" > /sys/kernel/debug/dynamic_debug/control
> > > 
> > > Hey a new debug option to enable!  With it enabled and the system booted with the bluetooth doogle
> > > unpluged here is what happens when it gets plugged (with 38-rc5):
> > > 
> > > grover ed # hciconfig -a
> > > hci0:   Type: BR/EDR  Bus: USB
> > >         BD Address: 00:0A:3A:55:07:5A  ACL MTU: 192:8  SCO MTU: 64:8
> > >         UP RUNNING 
> > >         RX bytes:356 acl:0 sco:0 events:13 errors:0
> > >         TX bytes:53 acl:0 sco:0 commands:13 errors:0
> > >         Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> > >         Packet type: DM1 DH1 HV1 
> > >         Link policy: 
> > >         Link mode: SLAVE ACCEPT 
> > >         Name: 'grover-0'
> > >         Class: 0x000000
> > >         Service Classes: Unspecified
> > >         Device Class: Miscellaneous, 
> > >         HCI Version: 1.1 (0x1)  Revision: 0x20d
> > >         LMP Version: 1.1 (0x1)  Subversion: 0x20d
> > >         Manufacturer: Cambridge Silicon Radio (10)
> > > 
> > > and the device works.  So either enabling dynamic debug, something between rc4 and rc5 or booting with the
> > > adaptor unplugged makes things work.  Will do some more checking to figure out which.
> > 
> > Great that it is working now. It might be a usb bug that you had, because we
> > had no changes in the Bluetooth subsystem between rc4 and rc5.
> > 
> > But does booting with the adapter work as well?
> 
> I have not been able to get it to work a second time no mater what combo I try - some sort of race I would guess:
> 
> Plugged at boot			fails
> Plugged after boot			fails
> Plugged after, btusb traced	fails
> Plugged after, bluetooth traced	fails
> Plugged after, both traced	fails

Gustavo,

I've figured out how to make things work though I am not sure why it fixes things.  

If I power on my bluetooth devices after running an 'hciconifg -a' they work.  

I can leave the adapter plugged at boot or plug it after.  The important thing seems to
be running the hciconfig before attempting to connect devices.  From the manpage
hciconfig -a should just be a query.  Instead it seems to initialize something and
makes things work here.  

Any idea why?
Ed