New: graph xrun not-triggered
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: [email protected]
Reporter: [email protected]
Regression: Nodec 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?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 219642] graph xrun not-triggered
https://bugzilla.kernel.org/show_bug.cgi?id=219642
Francois ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version| |Linux fedora
| |6.12.6-200.fc41.x86_64 #1
| |SMP PREEMPT_DYNAMIC Thu Dec
| |19 21:06:34 UTC 2024 x86_64
| |GNU/LinuxSignature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 219642] graph xrun not-triggered
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=219642
--- Comment #1 from Artem S. Tashkinov ([email protected]) --- This looks similar to this:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4310
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4233
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4182
And it looks like these messages couldn't have produced the behaviour you're observing.
Please try upgrading to the latest version of PipeWire regardless.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
[Bug 219642] graph xrun not-triggered
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=219642
Artem S. Tashkinov ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |ANSWERED--- Comment #2 from Artem S. Tashkinov ([email protected]) --- Or maybe just maybe even create a bug report in the PW's bug tracker.
The messages you're seeing are not coming from the kernel.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.