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 219003] "Bluetooth: hci0: corrupted SCO packet" on W800BT on kernel 6.9.7
Date: Thu, 04 Jul 2024 07:51:26 +0000	[thread overview]
Message-ID: <bug-219003-62941-bRJice6Stb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219003-62941@https.bugzilla.kernel.org/>

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

The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |regressions@leemhuis.info

--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
A few notes from a bystander:

* please attached a dmesg from a kernel where this problem occurs, ideally with
the latest 6.10-rc version or newer

* no developer might look into this, unless you bisect which change causes the
problem, as then someone is obliged to fix it
(https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html )

* not sure, the bluetooth developers might not even see this report (search for
bugzilla on
https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
for details)

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

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

  reply	other threads:[~2024-07-04  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 23:35 [Bug 219003] New: "Bluetooth: hci0: corrupted SCO packet" on W800BT on kernel 6.9.7 bugzilla-daemon
2024-07-04  7:51 ` bugzilla-daemon [this message]
2024-07-05 16:02 ` [Bug 219003] " 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-219003-62941-bRJice6Stb@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