Linux bluetooth development
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221696] btmtk: regression in 6.6.142: NULL pointer dereference in btmtk_usb_hci_wmt_sync during resume from S4
Date: Thu, 02 Jul 2026 06:46:02 +0000	[thread overview]
Message-ID: <bug-221696-62941-ifTay80NLC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221696-62941@https.bugzilla.kernel.org/>

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

--- Comment #2 from Matt Whitlock (kernel@mattwhitlock.name) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #1)
> Not my area of expertise, but sounds a bit like your problem will hopefully
> soon be fixed by
> https://lore.kernel.org/all/20260626104604.3465124-1-sivakumar.bs@gmail.com/

Thanks for the tip. I applied those two patches atop 6.6.143, then rebuilt and
rebooted, but the BUG trace still appears in the kernel log. I agree that the
patches did look promising, but they do not solve my issue.

-- 
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:[~2026-07-02  6:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 10:13 [Bug 221696] New: btmtk: regression in 6.6.142: NULL pointer dereference in btmtk_usb_hci_wmt_sync during resume from S4 bugzilla-daemon
2026-07-01  6:42 ` [Bug 221696] " bugzilla-daemon
2026-07-02  6:46 ` bugzilla-daemon [this message]
2026-07-02  6:53 ` bugzilla-daemon
2026-07-02  8:41 ` bugzilla-daemon
2026-07-02  9:13 ` bugzilla-daemon
2026-07-02  9:25 ` bugzilla-daemon
2026-07-02 12:36 ` bugzilla-daemon
2026-07-02 14:18 ` bugzilla-daemon
2026-07-02 14:52 ` bugzilla-daemon
2026-07-06  7:07 ` 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-221696-62941-ifTay80NLC@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