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 17:48:55 +0000 [thread overview]
Message-ID: <bug-216683-62941-c2HwjPErMv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216683-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216683
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #13 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to JustANormalTinkererMihir from comment #12)
> I am now able to reproduce this issue on kernel 5.19. Same kernel fault,
> same thing happened again, the dongle disconnected and reconnected causing
> the kernel fault.
I don't think this is related to HCI_QUIRK_NO_SUSPEND_NOTIFIER as it was only
introduced by the following change:
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btusb.c?id=b3cf94c8b6b2f1a2b94825a025db291da2b151fd
Or did it reach 5.19 via stable?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-11-28 18:02 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
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 [this message]
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-c2HwjPErMv@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 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.