From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215872] QCA6390 firmware crashes after some time
Date: Tue, 27 Dec 2022 16:00:57 +0000 [thread overview]
Message-ID: <bug-215872-62941-eJKNPT0ov2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215872-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215872
Mark Herbert (mark.herbert42@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark.herbert42@gmail.com
--- Comment #6 from Mark Herbert (mark.herbert42@gmail.com) ---
(In reply to Jakub Kicinski from comment #5)
> I believe this is closed by
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/
> ?id=d44e1dbda36fff5d7c2586683c4adc0963aef908 upstream.
It is not. QCA6390 bluetooth is not USB, it is serial device. So all btusb
changes can not help here at all.
It is still crashes from at least 5.17 up to 6.2-rc1, and what is bad it can
not be reactivated by any means except of total power off. Reboot does not help
- unless it is reboot to Windows.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-12-27 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 20:07 [Bug 215872] New: ath11k: QCA6390 firmware crashes after some time bugzilla-daemon
2022-04-21 20:07 ` [Bug 215872] " bugzilla-daemon
2022-04-21 20:08 ` bugzilla-daemon
2022-04-21 20:08 ` bugzilla-daemon
2022-04-27 7:33 ` [Bug 215872] " bugzilla-daemon
2022-04-29 11:59 ` [Bug 215872] New: ath11k: " Thorsten Leemhuis
2022-06-20 9:02 ` [Bug 215872] New: ath11k: QCA6390 firmware crashes after some time #forregzbot Thorsten Leemhuis
2022-06-08 20:12 ` [Bug 215872] QCA6390 firmware crashes after some time bugzilla-daemon
2022-12-27 16:00 ` bugzilla-daemon [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=bug-215872-62941-eJKNPT0ov2@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.