From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215347] btintel: AX200 (8087:0029): hci crashes and can't recover after repeated rfkill on/off
Date: Thu, 23 Dec 2021 05:28:21 +0000 [thread overview]
Message-ID: <bug-215347-62941-DgLn6xgXNI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215347-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215347
--- Comment #10 from Hui Wang (hui.wang@canonical.com) ---
@Tedd and Luiz,
Got it, will re-test with the latest bluetooth-next. And we didn't experience
the kernel oops with ubuntu kernel 5.13 and 5.14, this kernel oops only happen
in the bluetooth-next kernel, so I guess the root cause is not the kernel oops.
Anyway, I will try to catch the log without the kernel oops (with the fix of
comment 9).
Thanks.
--
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:[~2021-12-23 5:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 11:42 [Bug 215347] New: btintel: AX200 (8087:0029): hci crashed and can't recover after repeated rfkill on/off bugzilla-daemon
2021-12-17 11:43 ` [Bug 215347] btintel: AX200 (8087:0029): hci crashes " bugzilla-daemon
2021-12-18 0:02 ` bugzilla-daemon
2021-12-18 6:12 ` bugzilla-daemon
2021-12-18 6:13 ` bugzilla-daemon
2021-12-18 6:14 ` bugzilla-daemon
2021-12-18 6:15 ` bugzilla-daemon
2021-12-18 6:36 ` bugzilla-daemon
2021-12-18 6:46 ` bugzilla-daemon
2021-12-22 22:56 ` bugzilla-daemon
2021-12-22 23:45 ` bugzilla-daemon
2021-12-23 5:28 ` bugzilla-daemon [this message]
2021-12-23 13:42 ` bugzilla-daemon
2021-12-25 1:32 ` bugzilla-daemon
2022-01-20 1:22 ` bugzilla-daemon
2022-01-20 1:22 ` 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-215347-62941-DgLn6xgXNI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).