All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219642] New: graph xrun not-triggered
Date: Mon, 30 Dec 2024 14:21:45 +0000	[thread overview]
Message-ID: <bug-219642-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219642
           Summary: graph xrun not-triggered
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: blocking
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: francois5537@gmail.com
        Regression: No

dec 30 15:15:53 fedora wireplumber[1803]: pw.node:
(bluez_output.F8_4E_17_A3_5F_01.1-99) graph xrun not-triggered (0 suppressed)
dec 30 15:15:53 fedora wireplumber[1803]: pw.node: (-99) xrun
state:0x7f67c9f99008 pending:1/2 s:9372234501939 a:9372234564499
f:9372234623413 waiting:62560 process:58914 status:triggered
dec 30 15:15:53 fedora wireplumber[1803]: pw.node: (-93) xrun
state:0x7f67c9f98008 pending:0/1 s:9372328286234 a:9372328361058
f:9372234547036 waiting:74824 process:18446744073615737594 status:awake


This causes interrupts in my Bluetooth audio, which isn't great when listing to
music. It's on a Lenovo Yoga Pro 7 14AHP9.

The following warnings(?) also popup:

dec 30 15:17:33 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-52 noise=9999 txrate=1921500
dec 30 15:17:57 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-47 noise=9999 txrate=1729600
dec 30 15:18:16 fedora systemd-resolved[1397]: Using degraded feature set UDP
instead of UDP+EDNS0 for DNS server 192.168.50.1.
dec 30 15:18:17 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-51 noise=9999 txrate=1921500
dec 30 15:18:45 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-51 noise=9999 txrate=1729600
dec 30 15:19:05 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-49 noise=9999 txrate=1729600
dec 30 15:19:29 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-48 noise=9999 txrate=1225100
dec 30 15:19:51 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-49 noise=9999 txrate=1470200
dec 30 15:20:11 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-54 noise=9999 txrate=1470200
dec 30 15:20:33 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-50 noise=9999 txrate=1633500
dec 30 15:20:57 fedora wpa_supplicant[1625]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE
above=1 signal=-45 noise=9999 txrate=1814800

For some reason it keeps logging this, or re-connecting to my AP for a reason?

-- 
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-12-30 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 14:21 bugzilla-daemon [this message]
2024-12-30 14:22 ` [Bug 219642] graph xrun not-triggered bugzilla-daemon
2024-12-30 20:23 ` bugzilla-daemon
2024-12-30 20:24 ` 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-219642-62941@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.