From: "Daryl Van Vorst" <daryl@wideray.com>
To: "'Max Krasnyansky'" <maxk@qualcomm.com>,
"'Marcel Holtmann'" <marcel@rvs.uni-bielefeld.de>
Cc: <bluez-devel@lists.sourceforge.net>
Subject: RE: Qualification testing - rfcomm
Date: Thu, 12 Jun 2003 10:30:11 -0700 [thread overview]
Message-ID: <000501c33108$47499590$1a01010a@baked> (raw)
In-Reply-To: <5.1.0.14.2.20030611094056.0b771918@unixmail.qualcomm.com>
Max,
Below is exactly why the tests were failing (well, incomplete) - the tester
was waiting for an MSC which we never sent. Thanks!
With a little luck there won't be more bugs found in those tests. :) I'll
let you know what the results are when we do another round of tests.
-Daryl.
> Here is the relevant part of the trace
> > ACL data: handle 0x0001 flags 0x02 dlen 8
> L2CAP(d): cid 0x40 len 4 [psm 3]
> RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> < ACL data: handle 0x0001 flags 0x02 dlen 8
> L2CAP(d): cid 0x40 len 4 [psm 3]
> RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> > HCI Event: Number of Completed Packets(0x13) plen 5
> 01 01 00 01 00
> > ACL data: handle 0x0001 flags 0x02 dlen 8
> L2CAP(d): cid 0x40 len 4 [psm 3]
> RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> < ACL data: handle 0x0001 flags 0x02 dlen 8
> L2CAP(d): cid 0x40 len 4 [psm 3]
> RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
> > HCI Event: Number of Completed Packets(0x13) plen 5
> 01 01 00 01 00
>
> See, that's what I meant by incomplete in my prev email. We
> now always send MSC after UA,
> I mean it's unconditional in the code
> /* DLC was previously opened by PN request */
> rfcomm_send_ua(s, dlci);
>
> rfcomm_dlc_lock(d);
> d->state = BT_CONNECTED;
> d->state_change(d, 0);
> rfcomm_dlc_unlock(d);
>
> rfcomm_send_msc(s, 1, dlci,
> d->v24_sig);
> But there is no MSC in the trace.
>
> Hold on! I think I found a bug here. We always send MSC when
> DLC was opened by PN request but don't send it when DLC was
> opened by SABM. Ok that would explain it
> (trace doesn't have PN in it). They probably sit there and
> wait for MSC from us and
> in the mean time send() times out.
> Should be fixed now, I'm pushing a one liner fix as we speak :)
>
> Max
>
>
next prev parent reply other threads:[~2003-06-12 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001b01c32ee1$6a949eb0$1a01010a@baked>
[not found] ` <1055225608.3057.39.camel@pegasus>
2003-06-11 17:11 ` Qualification testing - rfcomm Max Krasnyansky
2003-06-12 17:30 ` Daryl Van Vorst [this message]
2003-07-08 18:16 Daryl Van Vorst
-- strict thread matches above, loose matches on Subject: below --
2003-07-11 8:55 [Bluez-devel] " Marcel Holtmann
2003-07-11 16:43 ` Daryl Van Vorst
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='000501c33108$47499590$1a01010a@baked' \
--to=daryl@wideray.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
--cc=maxk@qualcomm.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.