All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lovekesh Solanki <lovekeshsolanki00@gmail.com>
To: Snake Pilot <snakepilot10@gmail.com>
Cc: linux-wireless@vger.kernel.org, pkshih@realtek.com,
	 linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] rtw88_8723de: Wi-Fi and Bluetooth fail after warm reboot
Date: Thu, 6 Aug 2026 16:18:20 +0530	[thread overview]
Message-ID: <anRcsdWWWX7zyfj5@eggarch> (raw)
In-Reply-To: <CA+fxq6gBYA=qDrOQ+LmPHPdVGagtR0Vdnm_KeAC=nM7c-GSu5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

On Sun, Aug 02, 2026 at 11:40:51PM -0600, Snake Pilot wrote:
> Bluetooth: hci0: diag: hci_dev_shtudown: HCI_UP=1 HCI_UNREGISTER=0
> Bluetooth: hci0: diag: calling vendor shutdown callback
> Bluetooth: hci0: diag: btrtl_shutdown_realtek: sending HCI_OP_RESET
> Bluetooth: hci0: diag: btrtl_shutdown_realtek: HCI_OP_RESET completed OK
> Bluetooth: hci0: diag: vendor shutdown returned 0
I'm thinking if reset itself is the problem, since it does not run on
unloading manually but it does on shutdown.

> I did not find the btusb shutdown or rtw_pci_shutdown/D3hot diagnostic
> messages in the persisted previous-boot journal. The journal appears to end
> before the final device shutdown stage, so their absence from the journal
> does not necessarily mean that the callbacks were not invoked.
Yeah it seems it runs after journal is gone.

I suppose we should test by skipping HCI_OP_RESET if that improves the
issue.

Could you apply the attached patch only and start with a cold boot then
do a warm reboot and send the previous and current journal just like you
did before?

Thanks,
Lovekesh

[-- Attachment #2: skip-hci-reset.patch --]
[-- Type: text/plain, Size: 904 bytes --]

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 184e95c1625e..e7dd19b20cc8 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -3889,6 +3889,12 @@ static int btusb_shutdown_qca(struct hci_dev *hdev)
 	return 0;
 }

+static int btusb_shutdown_rtl8723de(struct hci_dev *hdev)
+{
+	bt_dev_info(hdev, "skipping HCI_OP_RESET......");
+	return 0;
+}
+
 static ssize_t force_poll_sync_read(struct file *file, char __user *user_buf,
 				    size_t count, loff_t *ppos)
 {
@@ -4338,6 +4344,9 @@ static int btusb_probe(struct usb_interface *intf,
 		set_bit(BTUSB_USE_ALT3_FOR_WBS, &data->flags);
 	}

+	if (id->idVendor == 0x0bda && id->idProduct == 0xb009)
+		hdev->shutdown = btusb_shutdown_rtl8723de;
+
 	if (id->driver_info & BTUSB_ACTIONS_SEMI) {
 		/* Support is advertised, but not implemented */
 		hci_set_quirk(hdev, HCI_QUIRK_BROKEN_ERR_DATA_REPORTING);

  reply	other threads:[~2026-08-06 10:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  7:13 [BUG] rtw88_8723de: Wi-Fi and Bluetooth fail after warm reboot Snake Pilot
2026-07-29  9:43 ` Lovekesh Solanki
2026-07-31  9:58   ` Snake Pilot
2026-07-31 20:30     ` Lovekesh Solanki
2026-08-01  8:00       ` Snake Pilot
2026-08-01 16:09         ` Lovekesh Solanki
2026-08-03  5:40           ` Snake Pilot
2026-08-06 10:48             ` Lovekesh Solanki [this message]
2026-08-12  7:03               ` Snake Pilot

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=anRcsdWWWX7zyfj5@eggarch \
    --to=lovekeshsolanki00@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=snakepilot10@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.