From: patchwork-bot+bluetooth@kernel.org
To: Xin Chen <xin.chen2@oss.qualcomm.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_chejiang@quicinc.com,
liulzhao@qti.qualcomm.com, cxin@qti.qualcomm.com,
stable@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb
Date: Wed, 19 Aug 2026 17:10:09 +0000 [thread overview]
Message-ID: <178715940938.3583745.2165256517061172398.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260819135321.1444185-1-xin.chen2@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 19 Aug 2026 21:53:21 +0800 you wrote:
> BT enable fails intermittently with -ETIMEDOUT (-110). The kernel log
> shows the HCI Read Local Version command was sent and the firmware
> replied with status 0x00 (logged by hci_req_cmd_complete() BT_DBG),
> but the waiter in __hci_cmd_sync_sk() never woke up and timed out
> after 10 s:
>
> bluetooth hci0: Opcode 0xfc00 // __hci_cmd_sync_sk
> bluetooth hci0: opcode 0xfc00 plen 1 // hci_cmd_sync_add
> bluetooth hci0: skb len 4 // hci_cmd_sync_alloc
> bluetooth hci0: length 1 // hci_req_sync_run
> Bluetooth: hci0 cmd_cnt 1 cmd queued 1 // hci_cmd_work
> Bluetooth: hci0 type 1 len 4 // hci_send_frame
> Bluetooth: opcode 0xfc00 status 0x00 // hci_req_cmd_complete
> <-- req_skb NULL: req_complete_skb not set,
> hci_cmd_sync_complete() never called,
> req_status stays HCI_REQ_PEND -->
> <-- 10 s later: wait_event_interruptible_timeout expires -->
> bluetooth hci0: end: err -110 // __hci_cmd_sync_sk
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb
https://git.kernel.org/bluetooth/bluetooth-next/c/be766d775060
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-19 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 13:53 [PATCH v1] Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb Xin Chen
2026-08-19 14:50 ` [v1] " bluez.test.bot
2026-08-19 17:10 ` patchwork-bot+bluetooth [this message]
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=178715940938.3583745.2165256517061172398.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cxin@qti.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulzhao@qti.qualcomm.com \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=quic_chejiang@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=xin.chen2@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox