From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: RFCOMM connection lag (slow)
Date: Sun, 24 Jul 2011 19:58:10 +0200 [thread overview]
Message-ID: <4E2C5D32.5030108@kernelconcepts.de> (raw)
In-Reply-To: <1311527208.2657.27.camel@THOR>
Am 24.07.2011 19:06, schrieb Peter Hurley:
> Hi Nils,
Hi Peter!
First, thanks for the fast reply!
> On Sun, 2011-07-24 at 12:22 -0400, Nils Faerber wrote:
>> I recently found a strange behaviour...
> ...
>> But as soon as larger chunks of data are sent (something like 128 bytes
>> at a time) it starts to take a pretty long time to transfer it (in the
>> range of about a second). The connection stays connected and data can be
>> sent but at a very slow pace.
>> This is from a 2.6.39 kernel to the device, my PC has a Bluetooth3.0 USB
>> device.
> ....
>> It is pretty likely that the device also has an RFCOMM bug here but
>> since it works with the HTC phone it must be possible to make it work
>> with my notebook too.
>>
>> Any hint would be very much appreciated ;)
>
> 1. What does an hcidump -tX of the session say?
The complete log would be a little longer.
Is there something special that I could watch for?
Here an excerpt:
1311530163.994927 > HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
1311530165.033926 > ACL data: handle 12 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 0]
0000: 09 ff 01 02 5c ....\
1311530165.034148 < ACL data: handle 12 flags 0x00 dlen 40
0000: 24 00 43 00 0b ef 41 01 20 40 00 57 60 00 00 03 $.C...A. @.W`...
0010: fc 01 00 07 00 00 00 00 58 60 00 00 fe ff 01 80 ........X`......
0020: 03 00 00 00 00 d7 af 9a ........
1311530165.034254 < ACL data: handle 12 flags 0x00 dlen 39
0000: 23 00 43 00 0b ef 3f 01 20 40 00 59 60 00 00 fc #.C...?. @.Y`...
0010: ff 01 e0 01 00 00 00 00 5a c0 00 00 fc ff 01 38 ........Z......8
0020: 00 00 00 00 00 cc 9a .......
1311530165.244924 > HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
1311530166.494919 > HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 0c 00 01 00 .....
1311530167.594936 > ACL data: handle 12 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 0]
0000: 09 ff 01 02 5c ....\
> 2. What flow control is being used?
You mean the serial port flow control on the RFCOMM channel?
>From my Linux app I do not use any handshake. On the G1 I can not check
since the Android app seems to go through the socket interface instead
of the /dev/rfcomm device.
> 3. What does the log say when bluetoothd is in debug mode?
In how far is bluetooth involved in the rfcomm conection? The
establishment is done manually using the rfcomm cmdline utility.
> That's where I would start...
>
> Regards,
> Peter
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
next prev parent reply other threads:[~2011-07-24 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 16:22 RFCOMM connection lag (slow) Nils Faerber
2011-07-24 17:06 ` Peter Hurley
2011-07-24 17:58 ` Nils Faerber [this message]
2011-07-24 18:42 ` Nils Faerber
2011-07-24 19:20 ` Peter Hurley
2011-07-26 8:42 ` Nils Faerber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E2C5D32.5030108@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter@hurleysoftware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.