From: Marcel Holtmann <marcel@holtmann.org>
To: Mike <puffy.taco@gmail.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: hcidump / avtest issues
Date: Fri, 27 Apr 2012 20:51:40 +0200 [thread overview]
Message-ID: <1335552700.16897.477.camel@aeonflux> (raw)
In-Reply-To: <CAB7rCTgK1eZwHQVp-VXxzWH_CmE_uygvcJ2HMJfZSTdE_LGiSw@mail.gmail.com>
Hi Mike,
> I'm having issues where hcidump seems to be losing packets. I'm
> trying to collect traces of avtest running. Avtest properly prints
> out that it sent a packet and received a reply, but I don't always see
> it in hcidump. Seems if I run avtest a lot successively, it does show
> up. I'm running a 2.6.33.20 kernel with hcidump-2.3. Let me know if
> the kernel is just too ancient, but I'd like to know if others have
> seen this type of issue.
actually hcidump can not loose any packets. Write them into a file in
BTSnoop format and double check with Wireshark or the Frontline Viewer.
The kernel is always sending the exact copy to the hcidump sockets and
thus there is no way you loose packets. The only explanation would be
that L2CAP socket has a bug and swallows it. Have you checked that
avtest actually reports L2CAP send errors.
Regards
Marcel
next prev parent reply other threads:[~2012-04-27 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 15:21 hcidump / avtest issues Mike
2012-04-27 18:51 ` Marcel Holtmann [this message]
2012-04-27 19:12 ` Mike
2012-04-27 20:13 ` Mike
2012-04-27 20:51 ` Marcel Holtmann
2012-04-27 20:57 ` Mike
2012-04-27 21:12 ` Mike
2012-04-28 15:15 ` Mike
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=1335552700.16897.477.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=puffy.taco@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox