All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update
Date: Thu, 17 Jul 2025 22:45:20 +0000	[thread overview]
Message-ID: <bug-220344-62941-LbaAeuHU9f@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220344-62941@https.bugzilla.kernel.org/>

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

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Thank you for your report. Is this a duplicate of bug 220341 ([URL][1])?

If yes, and you ruled out the newer firmware, than bisecting the issue is
needed. As it’s not immediately reproducible this might take some time though.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=220341

-- 
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:[~2025-07-17 22:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 10:45 [Bug 220344] New: Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update bugzilla-daemon
2025-07-17 22:45 ` bugzilla-daemon [this message]
2025-07-19 12:06 ` [Bug 220344] " bugzilla-daemon
2025-07-19 13:36 ` bugzilla-daemon
2025-07-20  9:02 ` bugzilla-daemon
2025-07-20 11:30 ` bugzilla-daemon
2025-07-24 19:29 ` bugzilla-daemon
2025-08-13  8:16 ` bugzilla-daemon
2026-03-08 14:56 ` 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-220344-62941-LbaAeuHU9f@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.