From: "Daryl Van Vorst" <daryl@wideray.com>
To: "'Marcel Holtmann'" <marcel@rvs.uni-bielefeld.de>
Cc: "'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] RE: Qualification testing - rfcomm
Date: Fri, 18 Jul 2003 11:53:29 -0700 [thread overview]
Message-ID: <002301c34d5d$e1069c70$5796fea9@baked> (raw)
In-Reply-To: <001501c347df$5c945550$1a01010a@baked>
Marcel,
Just wanted to make sure that you saw this (not trying to be pushy). :)
I haven't actually run into this problem with a real product yet, but the
rfcomm tester runs into it. So as far as qualification goes, it's pretty
marginal.
-Daryl.
> -----Original Message-----
> From: bluez-devel-admin@lists.sourceforge.net
> [mailto:bluez-devel-admin@lists.sourceforge.net] On Behalf Of
> Daryl Van Vorst
> Sent: July 11, 2003 12:05 PM
> To: 'Marcel Holtmann'
> Cc: 'BlueZ Mailing List'
> Subject: RE: [Bluez-devel] RE: Qualification testing - rfcomm
>
>
> Marcel,
>
> I just reproduced it here. Attached is an aclsession script
> which will do it. First run aclsession on one machine, then
> run rctest on the other machine. Also attached are the
> console output and hcidump from the machine running rctest.
>
> The pattern of send 5 packets, wait 20 seconds, send 5 more,
> etc appears to continue forever. I'm told that it should just
> keep sending data.
>
> -Daryl.
>
> > -----Original Message-----
> > From: bluez-devel-admin@lists.sourceforge.net
> > [mailto:bluez-devel-admin@lists.sourceforge.net] On Behalf Of
> > Daryl Van Vorst
> > Sent: July 11, 2003 9:44 AM
> > To: 'Marcel Holtmann'
> > Cc: 'BlueZ Mailing List'
> > Subject: [Bluez-devel] RE: Qualification testing - rfcomm
> >
> >
> > Marcel,
> >
> > You're right that it doesn't check the error code, it just
> > exits. But that doesn't explain why it sends 5 frames, waits
> > for 20 seconds, and then sends 5 more. Shouldn't send block?
> >
> > I haven't yet tried to reproduce that behaviour. So I'm not
> > certain that the sequence of send 5, wait 20, send 5 repeats
> > indefinitely. I'll take a look at it shortly.
> >
> > Thanks for the flow control patch... I'll wait and see if
> > anything comes out of the above stuff before sending it out
> > for testing.
> >
> > -Daryl.
> >
> > > -----Original Message-----
> > > From: Marcel Holtmann [mailto:marcel@rvs.uni-bielefeld.de]
> > > Sent: July 11, 2003 1:55 AM
> > > To: Daryl Van Vorst
> > > Cc: BlueZ Mailing List
> > > Subject: Re: Qualification testing - rfcomm
> > >
> > >
> > > Hi Daryl,
> > >
> > > > Finally got some results on those latest rfcomm changes for
> > > > qualification. Looks like there are a few more problems. :(
> > > But we're
> > > > close. :)
> > > >
> > > > TP/RFC/BV-09-C:
> > > > "Verify that the IUT handles flow control correctly when
> > > the Tester,
> > > > acting as a device conforming to Bluetooth version 1.0B,
> > > controls the
> > > > data flow using the Modem Status Command. The IUT's device
> > > role is of
> > > > no importance."
> > > >
> > > > The command and console output:
> > > >
> > > > root@jack-00000000:~>./rctest -s -P 1 -b 20 00:A0:96:1F:83:71
> > > > rctest[351]: Connected
> > > > rctest[351]: Sending ...
> > > > rctest[351]: Send failed. Resource temporarily unavailable(11)
> > > >
> > > > The IUT sends data in 5 frames, then stops for aboue 20s,
> > > then sends 5
> > > > more, then stops, etc. Technically, this test passed
> > because we did
> > > > stop sending data after the tester send MSC stop to the IUT. But
> > > > something's clearly not right.
> > >
> > > this looks quite right, but the rctest program don't
> check the error
> > > code. If it receives EAGAIN it should try again, but it aborts.
> > >
> > > Regards
> > >
> > > Marcel
> > >
> > >
> > >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Parasoft
> > Error proof Web apps, automate testing & more.
> > Download & eval WebKing and get a free book.
> > www.parasoft.com/bulletproofapps1
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/b> luez-devel
> >
>
next prev parent reply other threads:[~2003-07-18 18:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 18:16 Qualification testing - rfcomm Daryl Van Vorst
2003-07-08 21:47 ` [Bluez-devel] " James Courtier-Dutton
2003-07-08 23:23 ` Daryl Van Vorst
2003-07-18 19:35 ` James Courtier-Dutton
2003-07-11 8:18 ` [Bluez-devel] " Marcel Holtmann
2003-07-22 16:23 ` Max Krasnyansky
2003-07-22 16:46 ` Marcel Holtmann
2003-07-22 17:40 ` Max Krasnyansky
2003-07-22 19:13 ` Marcel Holtmann
2003-07-22 16:48 ` Daryl Van Vorst
2003-07-22 16:53 ` Marcel Holtmann
2003-07-22 17:01 ` Daryl Van Vorst
2003-07-11 8:55 ` Marcel Holtmann
2003-07-11 16:43 ` Daryl Van Vorst
2003-07-11 19:05 ` [Bluez-devel] " Daryl Van Vorst
2003-07-18 18:53 ` Daryl Van Vorst [this message]
2003-07-18 18:58 ` Marcel Holtmann
2003-07-18 19:07 ` Daryl Van Vorst
2003-07-18 19:12 ` Marcel Holtmann
2003-07-18 19:19 ` Daryl Van Vorst
2003-07-22 17:09 ` Max Krasnyansky
2003-07-22 18:13 ` David Woodhouse
2003-07-22 19:43 ` Max Krasnyansky
2003-07-22 16:26 ` Max Krasnyansky
2003-07-18 19:30 ` [Bluez-devel] " James Courtier-Dutton
2003-07-18 20:25 ` 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='002301c34d5d$e1069c70$5796fea9@baked' \
--to=daryl@wideray.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox