All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218952] bluetooth and wireplumber stop working after some time - dmesg report BUG
Date: Thu, 08 Aug 2024 11:36:14 +0000	[thread overview]
Message-ID: <bug-218952-62941-W5YFCVph7e@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218952-62941@https.bugzilla.kernel.org/>

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

--- Comment #3 from Nicolas BARANGER (nicolas.baranger@3xo.fr) ---
Dear maintener

Hope you're doing well...
For the moment, (good news?) I did not succeeded in reproducing the issue on
mainline kernel. 

I'll keept a particuliar attention on this issue and will update this case if
the issue appears again with newer kernel. 

Also, as I did not succeeded in reproducing the issue on mainline since now ~2
months, I did not get any new logs/status which could help to find the Root
Cause, sorry !

I remain available if you need help to make a deeper investigatation on this
issue.

Kind regards 
Nicolas Baranger

-- 
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:[~2024-08-08 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  6:21 [Bug 218952] New: bluetooth and wireplumber stop working after some time - dmesg report BUG bugzilla-daemon
2024-06-11  7:21 ` [Bug 218952] " bugzilla-daemon
2024-06-11 17:10 ` bugzilla-daemon
2024-08-08 11:36 ` bugzilla-daemon [this message]
2024-11-06  8:58 ` bugzilla-daemon
2025-07-11 14:58 ` bugzilla-daemon
2025-07-11 15:01 ` 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-218952-62941-W5YFCVph7e@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.