Blackberry Utils Timing out on Jaunty

probe.cc already included commented out area that had a device reset followed by a sleep. Uncommenting those two lines made the device function under Jaunty.

---
Investigation:
   --> Program functioned properly under gdb in single step mode
   --> Suspect a timeout problem on the USB bus
   --> Mailing list had indicated a reset function added last summer for one instance

   --> Found reset already in the code but commented out. Waiting on answer on mailing list for how upstream wants to handle.

Have been working with upstream. Testing reveals that this bug only occurs with the current Kernel version and did not occur with the 2.6.27. See email below. I believe this should move to the Kernel. How do I get it reassigned there since the testing below showed this was not a barry-utils bug.

 <mailto:<email address hidden>?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: <email address hidden>
X-Evolution-Source: imap://paul%<email address hidden>/

On Thu, Feb 19, 2009 at 12:49:20AM -0500, Paul O'Keefe wrote:
> I'm on 2.6.28-8.23. I also have 2.6.28-7.20 and 2.6.27-11.27 sitting on
> the machine. Tests with 2.6.28-7.20 kernel are identical to the
> 2.6.28-8.23 version.
>
> Tests with 2.6.27-11.27 work correctly for btool. I tried
> msynctool/opensync using the 2.6.27-11.27 kernel and of course that
> worked as it should too.
>
> There is a prepatch and snapshot of 2.6.29 in the Kernel archives so
> tomorrow I will pull it down and install.

Thanks for the report! Please keep us posted. Can you submit kernel bugs
to the Ubuntu folks if 2.6.29 doesn't fix it? I'd hate to have kernel
issues hampering Barry on the latest Ubuntu release.

Thanks,
- Chris

Have been testing against the Ubuntu built kernels and Kernel mainline. Fails against any Kernel build from Ubuntu since 2.6.28-7. Fails against mainline 2.6.28.6 and 2.6.29-rc5 on both x86 and x86_64.

Back trace shows waiting on a bulk usb read, last userland in libusb, and hung in kernel space.

Works correctly if run under gdb. Thinking a timing issue.

Current thought is that write may not complete to device. Examined code and there is an unlimited wait time on the read.
Sent from my BlackBerry

-----Original Message-----
From: Andrew Starr-Bochicchio <email address hidden>

Date: Mon, 23 Feb 2009 02:50:59
To: <email address hidden>
Subject: [Bug 329540] Re: Blackberry Utils Timing out on Jaunty

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: barry (Ubuntu)
       Status: New => Triaged

--
Blackberry Utils Timing out on Jaunty
https://bugs.launchpad.net/bugs/329540
You received this bug notification because you are a direct subscriber
of the bug.

Status in “barry” source package in Ubuntu: Triaged
Status in “linux” source package in Ubuntu: New

Bug description:
Binary package hint: barry-util

New package barry-util (and associated barrybackup-gui) non-functional for current configuration:
Compilation of barry package on Intrepid using same dependencies works correctly.

breset tool functions properly
btool discovers device correctly:

---------
pokeefe@pokeefe-laptop:~$ btool
Blackberry devices found:
Device ID: 0x94d0810. PIN: 3039712f, Description: RIM BlackBerry Device
Using device (PIN): 3039712f

---------

btool cannot pull databases from device, receives timeout instead -- Bad packet size. Packet: 26. DataSize(): 26. Required size: 44.

---------
pokeefe@pokeefe-laptop:~$ btool -vt > /tmp/btool.log

device_desc loaded
bLength: 18
bDescriptorType: 1
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
bMaxPacketSize0: 64
idVendor: 4042
idProduct: 32772
bcdDevice: 513
iManufacturer: 1
iProduct: 5
iSerialNumber: 3
bNumConfigurations: 1

  config_desc #0 loaded
bLength: 9
bDescriptorType: 2
wTotalLength: 97
bNumInterfaces: 2
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 128
MaxPower: 250

    interface_desc #0 loaded
bLength: 9
bDescriptorType: 4
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 8
bInterfaceClass: 255
bInterfaceSubClass: 1
bInterfaceProtocol: 255
iInterface: 2

      endpoint_desc #0 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 131
bmAttributes: 2
wMaxPacketSize: 512
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 131
        pair.read = 131
        pair.type = 2
      endpoint_desc #1 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 5
bmAttributes: 2
wMaxPacketSize: 512
bInterval: 0
bRefresh: 0
bSynchAddress: 0

      endpoint added to map with bEndpointAddress: 5
        pair.write = 5
        pair.type = 2
        pair added! (read: 131,write: 5,type: 2)
      endpoint_desc #2 loaded
bLength: 7
bDescriptorType: 5
bEndpointAddress: 135
bmAttributes: 2
...

The following patch has been discussed on the barry mailing list and the
Kernel USB Mailing list. Please consider for inclusion in the 0.14
version of barry-util prior to the Jaunty release

On Mon, 2009-02-23 at 03:11 +0000, Paul O'Keefe wrote:
> Have been testing against the Ubuntu built kernels and Kernel mainline.
> Fails against any Kernel build from Ubuntu since 2.6.28-7. Fails against
> mainline 2.6.28.6 and 2.6.29-rc5 on both x86 and x86_64.
>
> Back trace shows waiting on a bulk usb read, last userland in libusb,
> and hung in kernel space.
>
> Works correctly if run under gdb. Thinking a timing issue.
>
> Current thought is that write may not complete to device. Examined code and there is an unlimited wait time on the read.
> Sent from my BlackBerry
>
> -----Original Message-----
> From: Andrew Starr-Bochicchio <email address hidden>
>
> Date: Mon, 23 Feb 2009 02:50:59
> To: <email address hidden>
> Subject: [Bug 329540] Re: Blackberry Utils Timing out on Jaunty
>
>
> ** Also affects: linux (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: barry (Ubuntu)
> Status: New => Triaged
>
> --
> Blackberry Utils Timing out on Jaunty
> https://bugs.launchpad.net/bugs/329540
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “barry” source package in Ubuntu: Triaged
> Status in “linux” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: barry-util
>
> New package barry-util (and associated barrybackup-gui) non-functional for current configuration:
> Compilation of barry package on Intrepid using same dependencies works correctly.
>
> breset tool functions properly
> btool discovers device correctly:
>
> ---------
> pokeefe@pokeefe-laptop:~$ btool
> Blackberry devices found:
> Device ID: 0x94d0810. PIN: 3039712f, Description: RIM BlackBerry Device
> Using device (PIN): 3039712f
>
> ---------
>
> btool cannot pull databases from device, receives timeout instead -- Bad
> packet size. Packet: 26. DataSize(): 26. Required size: 44.
>
> ---------
> pokeefe@pokeefe-laptop:~$ btool -vt > /tmp/btool.log
>
> device_desc loaded
> bLength: 18
> bDescriptorType: 1
> bcdUSB: 512
> bDeviceClass: 0
> bDeviceSubClass: 0
> bDeviceProtocol: 0
> bMaxPacketSize0: 64
> idVendor: 4042
> idProduct: 32772
> bcdDevice: 513
> iManufacturer: 1
> iProduct: 5
> iSerialNumber: 3
> bNumConfigurations: 1
>
> config_desc #0 loaded
> bLength: 9
> bDescriptorType: 2
> wTotalLength: 97
> bNumInterfaces: 2
> bConfigurationValue: 1
> iConfiguration: 0
> bmAttributes: 128
> MaxPower: 250
>
> interface_desc #0 loaded
> bLength: 9
> bDescriptorType: 4
> bInterfaceNumber: 0
> bAlternateSetting: 0
> bNumEndpoints: 8
> bInterfaceClass: 255
> bInterfaceSubClass: 1
> bInterfaceProtocol: 255
> iInterface: 2
>
> endpoint_desc #0 loaded
> bLength: 7
> bDescriptorType: 5
> bEndpointAddress: 131
> bmAttributes: 2
> wMaxPacketSize: 512
> bInterval: 0
> bRefresh: 0
> bSynchAddress: 0
>
> endpoint added to map with bEndpointAddress: 131
> pair.read = 131
> pair.type = 2
> endpoint_desc #1 loaded
> bLength: 7
> bDescriptorType...

On Fri, 2009-02-27 at 19:11 +0000, Paul O'Keefe wrote:
> The following patch has been discussed on the barry mailing list and the
> Kernel USB Mailing list. Please consider for inclusion in the 0.14
> version of barry-util prior to the Jaunty release
>

Trying again with patch included here as plain text

---------------------------------------------------

diff -Naur barry.orig/src/usbwrap.cc barry.patch/src/usbwrap.cc
--- barry.orig/src/usbwrap.cc 2009-02-27 01:54:00.000000000 +0000
+++ barry.patch/src/usbwrap.cc 2009-02-27 01:56:34.000000000 +0000
@@ -187,6 +187,11 @@
  dout("usb_clear_halt(" << std::dec << m_handle << "," << std::dec <<
ep << ")");
  int ret = usb_clear_halt(m_handle, ep);
  m_lasterror = ret;
+
+ //Paul O'Keefe <email address hidden> 26-feb-2009
+ //Device may hang if commands sent immediately after this call.
+ //Add small sleep to allow device to settle before continuing
+ usleep(100000);
  return ret >= 0;
 }

diff -Naur barry.orig/src/usbwrap.h barry.patch/src/usbwrap.h
--- barry.orig/src/usbwrap.h 2009-02-27 01:54:00.000000000 +0000
+++ barry.patch/src/usbwrap.h 2009-02-27 01:55:04.000000000 +0000
@@ -29,6 +29,9 @@
 #include <map>
 #include "error.h"

+// Paul O'Keefe. <email address hidden> 26-feb-2009
+#include <unistd.h>
+
 #define USBWRAP_DEFAULT_TIMEOUT 30000

 namespace Barry { class Data; }

----------------------------------------------------
>
>
> On Mon, 2009-02-23 at 03:11 +0000, Paul O'Keefe wrote:
> > Have been testing against the Ubuntu built kernels and Kernel mainline.
> > Fails against any Kernel build from Ubuntu since 2.6.28-7. Fails against
> > mainline 2.6.28.6 and 2.6.29-rc5 on both x86 and x86_64.
> >
> > Back trace shows waiting on a bulk usb read, last userland in libusb,
> > and hung in kernel space.
> >
> > Works correctly if run under gdb. Thinking a timing issue.
> >
> > Current thought is that write may not complete to device. Examined code and there is an unlimited wait time on the read.
> > Sent from my BlackBerry
> >
> > -----Original Message-----
> > From: Andrew Starr-Bochicchio <email address hidden>
> >
> > Date: Mon, 23 Feb 2009 02:50:59
> > To: <email address hidden>
> > Subject: [Bug 329540] Re: Blackberry Utils Timing out on Jaunty
> >
> >
> > ** Also affects: linux (Ubuntu)
> > Importance: Undecided
> > Status: New
> >
> > ** Changed in: barry (Ubuntu)
> > Status: New => Triaged
> >
> > --
> > Blackberry Utils Timing out on Jaunty
> > https://bugs.launchpad.net/bugs/329540
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in “barry” source package in Ubuntu: Triaged
> > Status in “linux” source package in Ubuntu: New
> >
> > Bug description:
> > Binary package hint: barry-util
> >
> > New package barry-util (and associated barrybackup-gui) non-functional for current configuration:
> > Compilation of barry package on Intrepid using same dependencies works correctly.
> >
> > breset tool functions properly
> > btool discovers device correctly:
> >
> > ---------
> > pokeefe@pokeefe-laptop:~$ btool
> > Blackberry devices found:
> > Device ID: 0x94d0810. PIN: 3039712f, Description: RIM BlackB...

OK..so stupid question. How do I apply this patch?

Seems patch is needed for barry rather than the kernel itself. Closing linux task for now. Thanks.

Same stupid question, how to apply this patch?? Thanks!