Sponsor new upstream version (4.33) into Jaunty

I built is successfully, and I tested it and worked fine for me.

Diffstat

debdiff

by the way, anyone can test the latest bluez, I've packaged it in my ppa (https://edge.launchpad.net/~bmillemathias/+archive/ppa).

On my side I still need to check if audio streaming to my audio gateway still work.
I'd be interested if someone can confirm there is no other regression between 4.32 and 4.33 (like headset, network, ...).

thanks

Release ack, once someone can confirm that this version still works with standard use cases like headsets.

Martin,

there was no feedback, so what should we do?
Do you know some people from Canonical/ubuntu with bluetooth devices that can test there is no regressions between 4.32. and 4.33?

I tried the package on the PPA, but I still see a crash

There's this in my dmesg:
[ 2161.285054] bluetoothd[6351]: segfault at 7 ip b7d7adc3 sp bfbdbd98 error 4 in libc-2.9.so[b7d0b000+15c000]

Can't really tell if it's the same thing as Bug #343269 as the crash reporter won't let me report because it's not an official package.

Does this help? I have a bunch of bluetooth devices that I'd like to finally work on Jaunty, so please let me know how can I assist.

Alex,

Could you post the crash? I guess it is stored under /var/crash/?
Thanks a lot

Baptiste,

Attached as you requested. Let me know if anything else is needed.

Thanks

Baptiste,

you could send out a call for testing on ubuntu-devel@.

I tested the 4.33 packages with file transfer to my Nokia 6303. There's not much else I can test with it, I'm afraid.

Alex,

I'd would interested also if you can reproduce the crash in 4.32? if yes could you install debug packages of bluez (see https://wiki.ubuntu.com/DebuggingProgramCrash). and open new bug with apport so I'll have all crash information with debug symbol.

Baptiste,

FWIW a very similar crash on 4.32 is already reported as Bug #343269 I'll try a debug over the weekend.

Baptiste,

4.33+git20090327-0ubuntu1 doesn't seem to crash any longer, yet I'm unable to do anything with it, not even "see" fully discoverable devices.

$ hcitool scan
Scanning ...
Inquiry failed: Connection timed out

$ hciconfig
hci0: Type: USB
 BD Address: 00:0X:X1:X1:X3:X3 ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:667 acl:0 sco:0 events:19 errors:0
 TX bytes:609 acl:0 sco:0 commands:27 errors:0

dmesg over an unplug/replug of the dongle
$dmesg
[ 1020.204655] usb 3-1: new full speed USB device using ohci_hcd and address 2
[ 1020.379960] usb 3-1: configuration #1 chosen from 1 choice
[ 1020.447508] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 1020.470636] usbcore: registered new interface driver btusb
[ 1025.615777] hci_cmd_task: hci0 command tx timeout
[ 1030.621399] hci_cmd_task: hci0 command tx timeout
[ 1035.627145] hci_cmd_task: hci0 command tx timeout
[ 1072.753865] hci_cmd_task: hci0 command tx timeout
[ 1113.641282] hci_cmd_task: hci0 command tx timeout
[ 1271.246426] hci_cmd_task: hci0 command tx timeout
[ 1384.006653] hci_cmd_task: hci0 command tx timeout
[ 1402.792824] hci_cmd_task: hci0 command tx timeout
[ 1497.571030] hci_cmd_task: hci0 command tx timeout
[ 1624.353271] usb 3-1: USB disconnect, address 2
[ 1624.353471] btusb_intr_complete: hci0 urb e145ab80 failed to resubmit (19)
[ 1624.356468] btusb_send_frame: hci0 urb f5c66580 submission failed
[ 1632.957072] usb 3-1: new full speed USB device using ohci_hcd and address 3
[ 1633.135410] usb 3-1: configuration #1 chosen from 1 choice
[ 1638.282833] hci_cmd_task: hci0 command tx timeout
[ 1643.289604] hci_cmd_task: hci0 command tx timeout
[ 1648.325794] hci_cmd_task: hci0 command tx timeout
[ 1653.328405] hci_cmd_task: hci0 command tx timeout

$ sudo lsusb -vv
Bus 003 Device 003: ID 4851:1103
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x4851
  idProduct 0x1103
  bcdDevice 0.04
  iManufacturer 1 Formosa
  iProduct 2 BCM92035DGROM
  iSerial 3 000EA131B3A3
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 200
    bNumInterfaces 3
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 224 Wireless
      bInterfaceSubClass 1 Radio Frequency
      bInterfaceProtocol 1 Bluetooth
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type ...

Tried with another dongle I have and I seem to be looking at bug 148290 too:

alex-mayorga@inspiron-1501:~$ lsusb |grep Logitech
Bus 003 Device 006: ID 046d:c70c Logitech, Inc. BT Mini-Receiver (HID proxy mode)
Bus 003 Device 005: ID 046d:c70b Logitech, Inc. BT Mini-Receiver (HID proxy mode)
Bus 003 Device 004: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)
alex-mayorga@inspiron-1501:~$ hcitool dev
Devices:
alex-mayorga@inspiron-1501:~$ hid2hci
Switching device 046d:c70c to HCI mode failed (No such file or directory)
Switching device 046d:c70b to HCI mode failed (No such file or directory)

Again anything I can provide please don't hesitate to ask.

On Mon, Mar 30, 2009 at 2:35 AM, Alex Mayorga Adame
<email address hidden> wrote:
> Baptiste,
>
> 4.33+git20090327-0ubuntu1 doesn't seem to crash any longer, yet I'm
> unable to do anything with it, not even "see" fully discoverable
> devices.
>

> dmesg over an unplug/replug of the dongle
> $dmesg
> [ 1020.204655] usb 3-1: new full speed USB device using ohci_hcd and address 2
> [ 1020.379960] usb 3-1: configuration #1 chosen from 1 choice
> [ 1020.447508] Bluetooth: Generic Bluetooth USB driver ver 0.3
> [ 1020.470636] usbcore: registered new interface driver btusb
> [ 1025.615777] hci_cmd_task: hci0 command tx timeout
> [ 1030.621399] hci_cmd_task: hci0 command tx timeout
> [ 1035.627145] hci_cmd_task: hci0 command tx timeout
> [ 1072.753865] hci_cmd_task: hci0 command tx timeout
> [ 1113.641282] hci_cmd_task: hci0 command tx timeout
> [ 1271.246426] hci_cmd_task: hci0 command tx timeout
> [ 1384.006653] hci_cmd_task: hci0 command tx timeout
> [ 1402.792824] hci_cmd_task: hci0 command tx timeout
> [ 1497.571030] hci_cmd_task: hci0 command tx timeout

Theses problem is a kernel bug and not a bluetooth one, the bug is
https://bugs.edge.launchpad.net/ubuntu/+source/bluez/+bug/268502, so
--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés

Baptiste,

Any idea on when the "cherry picked" kernel would be available?

What about the Logitech issue, should I add my comments on Bug #123920 or file a new report?

Thanks a lot

I'm sorry that this didn't make it in for the jaunty release, but karmic now has bluez 4.37. Please put the new version through its paces, and file bugs for any problems you have with it, so we can make sure to get everything working well for the 9.10 release!