From: Marcel Holtmann <marcel@holtmann.org>
To: hongyi mao <maohongyicn@gmail.com>
Cc: Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: Kernel Bluetooth Protocol Stack Problem
Date: Tue, 8 Oct 2019 10:41:06 +0200 [thread overview]
Message-ID: <140A3914-6A0F-4E42-9858-7CDFE348C0CA@holtmann.org> (raw)
In-Reply-To: <CACokStdMboxnDPR6cdQYfpfdNApQCn73pjQZNqQ+ag0QPYZXgw@mail.gmail.com>
Hi Hongyi,
> Currently we have found a problem when using the kernel Bluetooth
> protocol stack.
>
> Bluetooth hardware: support BR/BLE USB Client Module
>
> Kernel version: 3.18.20
>
> The problem: our host received the HCI_EV_CONN_REQUEST event, in this
> event call hci_conn_add () and create a struct hci_conn,
> then the host will send HCI_OP_ACCEPT_SYNC_CONN_REQ command in the
> event processing.
> However, according to the Bluetooth protocol core_v5.0 description,
> the host will then receive a Command Status event or Synchronous
> Connection Complete event or Connection Complete event for the link,
> which will include Connection_Handle and the link parameters if the
> setup is successful.
> However, the host did not receive these events for the link.
> Hdev->rx_work workqueue is still working to collect events.
> After a period of time, the host receives an HCI_EV_CHANNEL_SELECTED
> event, which is to operate the hci_conn->amp_mgr structure,
> but the host has not received any events containing any information
> in the structure, this structure has not been created, so the kernel
> appears oops
>
> Thanks and Best Regards!
please create a binary trace with btmon -w trace.log and I can have a look at it. However if your BR/EDR/LE controllers sends AMP controller events, something is wrong with your controller.
Regards
Marcel
next prev parent reply other threads:[~2019-10-08 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 8:34 Kernel Bluetooth Protocol Stack Problem hongyi mao
2019-10-08 8:41 ` Marcel Holtmann [this message]
[not found] ` <CACokStd_VLLP=dc+v=MZXpYF+Pw57f0Cma3-HSrXz5_PdiyRfw@mail.gmail.com>
2019-10-10 3:43 ` Marcel Holtmann
2019-10-10 8:27 ` hongyi mao
2019-10-16 19:08 ` Marcel Holtmann
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=140A3914-6A0F-4E42-9858-7CDFE348C0CA@holtmann.org \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=maohongyicn@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;
as well as URLs for NNTP newsgroup(s).