Re: [Barry-devel] Bad packet size
Status: Beta
Brought to you by:
ndprojects
Menu
▾
▴
Re: [Barry-devel] Bad packet size
|
From: Alan M. <Ala...@sy...> - 2007-01-30 11:43:32
|
Chris,
Un- and re-plugging the device doesn't seem to help.
I don't see what could be trying to communicate with the BB.
No Vmware running (just CrossOver Outlook 2003), some terms, and
firefox.
I have bcharge enabled in udev/10-blackberry.rules and can see that it
Correctly sets the port to 500mA. With the rule disabled the port is at
100mA.
The laptop is connected to a docking station. Maybe that's the problem.
With bcharge/udev-rule disabled I see this:
[amiller@localhost] /sbin/lsusb
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 052: ID 0fca:0001 Research In Motion, Ltd. Blackberry
Handheld Bus 004 Device 001: ID 0000:0000 Bus 004 Device 002: ID
413c:0058 Dell Computer Corp.=20
Bus 004 Device 003: ID 413c:1003 Dell Computer Corp.=20
Bus 004 Device 006: ID 413c:2010 Dell Computer Corp.=20
Bus 004 Device 005: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel=20
[amiller@localhost] sudo barrybackup -p 24f74ef3 -t
usb_set_debug: Setting debugging level to 9 (on)
usb_os_init: Found USB VFS at /dev/bus/usb on_startup
usb_os_find_busses: Found 002
usb_os_find_busses: Found 003
usb_os_find_busses: Found 001
usb_os_find_busses: Found 004
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 052 on 004
usb_os_find_devices: Couldn't open /dev/bus/usb/004/039
usb_os_find_devices: Couldn't open /dev/bus/usb/004/106
usb_os_find_devices: Couldn't open /dev/bus/usb/004/085
usb_os_find_devices: Couldn't open /dev/bus/usb/004/058
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 006 on 004
skipped 1 class/vendor specific interface descriptors skipped 1
class/vendor specific interface descriptors
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors error obtaining
child information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device BulkWrite to endpoint 4:
00000000: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00
............l...
BulkWrite to endpoint 4:
00000000: 00 00 0c 00 05 ff 00 01 14 00 01 00
............
BulkWrite to endpoint 4:
00000000: 00 00 0c 00 05 ff 00 02 08 00 04 00
............
Using ReadEndpoint: 131
WriteEndpoint: 4
usb_os_find_busses: Found 002
usb_os_find_busses: Found 003
usb_os_find_busses: Found 001
usb_os_find_busses: Found 004
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 052 on 004
usb_os_find_devices: Couldn't open /dev/bus/usb/004/039
usb_os_find_devices: Couldn't open /dev/bus/usb/004/106
usb_os_find_devices: Couldn't open /dev/bus/usb/004/085
usb_os_find_devices: Couldn't open /dev/bus/usb/004/058
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 006 on 004
skipped 1 class/vendor specific interface descriptors skipped 1
class/vendor specific interface descriptors
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors error obtaining
child information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device BulkWrite to endpoint 4:
00000000: 00 00 18 00 07 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
00000010: 74 6f 70 00 00 00 00 00 top.....
Socket::Send: Endpoint 131
Received:
00000000: 00 00 2c 00 08 07 00 05 52 49 4d 20 44 65 73 6b
..,.....RIM Desk
00000010: 74 6f 70 00 00 00 00 00 00 00 00 00 01 00 04 00
top.............
00000020: 02 00 04 00 03 01 00 00 04 01 00 00
............
BulkWrite to endpoint 4:
00000000: 00 00 08 00 0a 07 00 06 ........
Socket::Send: Endpoint 131
Received:
00000000: 00 00 0c 00 13 07 01 00 00 00 00 00
............
Socket::Receive: Endpoint 131
Received:
00000000: 00 00 10 00 0e 07 00 06 0a 00 04 00 e0 a1 9e 8d
................
Packet:
00000000: 00 00 10 00 0e 07 00 06 0a 00 04 00 e0 a1 9e 8d
................
>> [root@localhost]# btool -p 24f74ef3 -t
>> usb_set_debug: Setting debugging level to 1 (on)
>> usb_os_init: Found USB VFS at /dev/bus/usb Blackberry devices found:
>> Device ID: 0x87fa1c0. PIN: 24f74ef3
>> Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
>> 00000000: 00 00 1a 00 09 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00 02 00
top.......
>>=20
>> Sent packet:
>> 00000000: 00 00 18 00 07 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00
top.....
>>=20
>> Response packet:
>> 00000000: 00 00 1a 00 09 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00 02 00
top.......
>=20
> I've only seen these errors when the device has already had a partial=20
> conversation. Usually unplugging it and replugging it solves the
issue.
>=20
> Do you have anything else running that might be talking to the
Blackberry?
> Say a windows install in vmware or something?
>=20
> Thanks,
> - ChrisChris,
Un- and re-plugging the device doesn't seem to help.
I don't see what could be trying to communicate with the BB.
No Vmware running (just CrossOver Outlook 2003), some terms, and
firefox.
I have bcharge enabled in udev/10-blackberry.rules and can see that it
Correctly sets the port to 500mA. With the rule disabled the port is at
100mA.
The laptop is connected to a docking station. Maybe that's the problem.
With bcharge/udev-rule disabled I see this:
[amiller@localhost] /sbin/lsusb
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 004 Device 052: ID 0fca:0001 Research In Motion, Ltd. Blackberry
Handheld Bus 004 Device 001: ID 0000:0000 Bus 004 Device 002: ID
413c:0058 Dell Computer Corp.=20
Bus 004 Device 003: ID 413c:1003 Dell Computer Corp.=20
Bus 004 Device 006: ID 413c:2010 Dell Computer Corp.=20
Bus 004 Device 005: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel=20
[amiller@localhost] sudo barrybackup -p 24f74ef3 -t
usb_set_debug: Setting debugging level to 9 (on)
usb_os_init: Found USB VFS at /dev/bus/usb on_startup
usb_os_find_busses: Found 002
usb_os_find_busses: Found 003
usb_os_find_busses: Found 001
usb_os_find_busses: Found 004
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 052 on 004
usb_os_find_devices: Couldn't open /dev/bus/usb/004/039
usb_os_find_devices: Couldn't open /dev/bus/usb/004/106
usb_os_find_devices: Couldn't open /dev/bus/usb/004/085
usb_os_find_devices: Couldn't open /dev/bus/usb/004/058
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 006 on 004
skipped 1 class/vendor specific interface descriptors skipped 1
class/vendor specific interface descriptors
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors error obtaining
child information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device BulkWrite to endpoint 4:
00000000: 00 00 10 00 01 ff 00 00 a8 18 da 8d 6c 02 00 00
............l...
BulkWrite to endpoint 4:
00000000: 00 00 0c 00 05 ff 00 01 14 00 01 00
............
BulkWrite to endpoint 4:
00000000: 00 00 0c 00 05 ff 00 02 08 00 04 00
............
Using ReadEndpoint: 131
WriteEndpoint: 4
usb_os_find_busses: Found 002
usb_os_find_busses: Found 003
usb_os_find_busses: Found 001
usb_os_find_busses: Found 004
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 052 on 004
usb_os_find_devices: Couldn't open /dev/bus/usb/004/039
usb_os_find_devices: Couldn't open /dev/bus/usb/004/106
usb_os_find_devices: Couldn't open /dev/bus/usb/004/085
usb_os_find_devices: Couldn't open /dev/bus/usb/004/058
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 002 on 004
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 006 on 004
skipped 1 class/vendor specific interface descriptors skipped 1
class/vendor specific interface descriptors
usb_os_find_devices: Found 005 on 004
skipped 1 class/vendor specific interface descriptors error obtaining
child information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device error obtaining child
information: Inappropriate ioctl for device BulkWrite to endpoint 4:
00000000: 00 00 18 00 07 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
00000010: 74 6f 70 00 00 00 00 00 top.....
Socket::Send: Endpoint 131
Received:
00000000: 00 00 2c 00 08 07 00 05 52 49 4d 20 44 65 73 6b
..,.....RIM Desk
00000010: 74 6f 70 00 00 00 00 00 00 00 00 00 01 00 04 00
top.............
00000020: 02 00 04 00 03 01 00 00 04 01 00 00
............
BulkWrite to endpoint 4:
00000000: 00 00 08 00 0a 07 00 06 ........
Socket::Send: Endpoint 131
Received:
00000000: 00 00 0c 00 13 07 01 00 00 00 00 00
............
Socket::Receive: Endpoint 131
Received:
00000000: 00 00 10 00 0e 07 00 06 0a 00 04 00 e0 a1 9e 8d
................
Packet:
00000000: 00 00 10 00 0e 07 00 06 0a 00 04 00 e0 a1 9e 8d
................
>> [root@localhost]# btool -p 24f74ef3 -t
>> usb_set_debug: Setting debugging level to 1 (on)
>> usb_os_init: Found USB VFS at /dev/bus/usb Blackberry devices found:
>> Device ID: 0x87fa1c0. PIN: 24f74ef3
>> Bad packet size. Packet: 26. DataSize(): 26. Required size: 44
>> 00000000: 00 00 1a 00 09 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00 02 00
top.......
>>=20
>> Sent packet:
>> 00000000: 00 00 18 00 07 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00
top.....
>>=20
>> Response packet:
>> 00000000: 00 00 1a 00 09 ff 00 05 52 49 4d 20 44 65 73 6b
........RIM Desk
>> 00000010: 74 6f 70 00 00 00 00 00 02 00
top.......
>=20
> I've only seen these errors when the device has already had a partial=20
> conversation. Usually unplugging it and replugging it solves the
issue.
>=20
> Do you have anything else running that might be talking to the
Blackberry?
> Say a windows install in vmware or something?
>=20
> Thanks,
> - Chris
|
Thanks for helping keep SourceForge clean.
X