public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Rafael Seste <rseste@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Corrupted skbs on ARM
Date: Fri, 17 Jul 2009 16:13:53 -0300	[thread overview]
Message-ID: <5d223510907171213n3fad15a5vd25dfd43e29c38fa@mail.gmail.com> (raw)

Hello,

We have been stuck with a problem regarding bluetooth audio
transmission in ARM processors for a long time. Our ARM machine runs
Linux (2.6.30 kernel) and has a Bluetooth USB adapter (Bluez 4.42).
When it plays or receives audio, some packets are right, but a good
deal of them have wrong handles and lengths.

When the same Bluetooth adapter is used in an x86 system, with the
same kernel version, the audio works perfectly, the handles are normal
(constant for one connection) and the lengths are 48 bytes for all
audio packets.

Using hcidump and printks in hci_core.c to see these packets, we found
that hci_rx_task() already receives corrupted skbs when it calls
skb_dequeue(&hdev->rx_q). Not having any experience with the Linux
Kernel, we don't know what enqueues skbs in that queue, nor in what
direction the calls are coming from - from to OS to the physical
device or from a device interrupt to an OS callback.

Has anyone else experienced this problem and found a solution? Also,
since we are backtracking the error, knowing where the skbs in rx_q
come from is essential. Could anyone point us where these skbs are
inserted in the queue?

Thank you in advance for the help.

-- 
Rafael S. Seste

                 reply	other threads:[~2009-07-17 19:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5d223510907171213n3fad15a5vd25dfd43e29c38fa@mail.gmail.com \
    --to=rseste@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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