public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216683] [REGRESSION] HCI_QUIRK_NO_SUSPEND_NOTIFIER causes kernel panic on fake CSR 5.0 clones
Date: Mon, 28 Nov 2022 16:26:23 +0000	[thread overview]
Message-ID: <bug-216683-62941-m2DUrIxpa5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216683-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216683

--- Comment #9 from JustANormalTinkererMihir (justanormaltinkerermihir@duck.com) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #7)
What sort of update do you require? As far as I can tell
HCI_QUIRK_NO_SUSPEND_NOTIFIER causes this regression, and the dongle continues
to work fine after just removing the line. One thing I have noticed in the
dmesg log is that the dongle sometimes disconnects and reconnects, this is
largely the reason why the kernel fault even occurs, it disconnects and
reconnects like this:
[   53.494546] Bluetooth: RFCOMM TTY layer initialized
[   53.494558] Bluetooth: RFCOMM socket layer initialized
[   53.494561] Bluetooth: RFCOMM ver 1.11
[   60.757711] rfkill: input handler disabled
[   73.717144] rfkill: input handler enabled
[   80.462376] rfkill: input handler disabled
[   80.468335] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Quota
mode: none.
[   93.275986] input: Airdopes 121v2 (AVRCP) as /devices/virtual/input/input23
[  136.650027] usb 2-1.5: USB disconnect, device number 3
[  136.892439] usb 2-1.5: new full-speed USB device number 4 using ehci-pci
[  136.998154] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001,
bcdDevice=88.91
[  136.998160] usb 2-1.5: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[  136.998162] usb 2-1.5: Product: BT DONGLE10
[  137.000158] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=9 rev=0810;
LMP ver=9 subver=2312; manufacturer=10
[  137.000163] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding
workarounds...
[  137.000164] Bluetooth: hci0: CSR: Unbranded CSR clone detected;
force-suspending once...
[  137.000166] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot
8041a02 receive-issue workaround
[  137.000188] Bluetooth: hci0: HCI Delete Stored Link Key command is
advertised, but not supported.
[  137.000189] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting
command is advertised, but not supported.
[  137.000190] Bluetooth: hci0: HCI Set Event Filter command not supported.
[  137.082247] Bluetooth: MGMT ver 1.22
[  143.561978] usb 2-1.5: USB disconnect, device number 4

This seems to only happen when idle not when there is any activity. Maybe the
dongle has some built-in power saving feature that disables the dongle when not
in use? Please note this also happens after disabling the
HCI_QUIRK_NO_SUSPEND_NOTIFIER. These dongles seem really messed up.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2022-11-28 16:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12  6:31 [Bug 216683] New: notifier callback hci_suspend_notifier [bluetooth] already registered bugzilla-daemon
2022-11-13 17:15 ` [Bug 216683] " bugzilla-daemon
2022-11-25  2:41 ` bugzilla-daemon
2022-11-26 14:37 ` bugzilla-daemon
2022-11-26 14:39 ` [Bug 216683] [REGRESSION] HCI_QUIRK_NO_SUSPEND_NOTIFIER causes kernel panic on fake CSR 5.0 clones bugzilla-daemon
2022-11-26 16:05 ` bugzilla-daemon
2022-11-26 16:29 ` bugzilla-daemon
2022-11-26 16:30 ` bugzilla-daemon
2022-11-26 23:26 ` bugzilla-daemon
2022-11-27 12:32 ` bugzilla-daemon
2022-11-27 19:54 ` bugzilla-daemon
2022-11-28 16:26 ` bugzilla-daemon [this message]
2022-11-28 16:31 ` bugzilla-daemon
2022-11-28 17:04 ` bugzilla-daemon
2022-11-28 17:10 ` bugzilla-daemon
2022-11-28 17:48 ` bugzilla-daemon
2022-11-28 18:14 ` bugzilla-daemon
2022-11-29  9:26 ` bugzilla-daemon
2022-11-29 21:54 ` bugzilla-daemon
2022-11-30 21:59 ` bugzilla-daemon
2022-12-01 11:31 ` bugzilla-daemon
2022-12-02  0:39 ` bugzilla-daemon
2022-12-02  0:45 ` bugzilla-daemon
2022-12-02  2:46 ` bugzilla-daemon
2022-12-02  3:10 ` bugzilla-daemon
2022-12-12 13:50 ` bugzilla-daemon

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=bug-216683-62941-m2DUrIxpa5@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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