pipewire-aes67 hangs on startup on Raspberry Pi 5
- PipeWire version (
pipewire --version
): 1.1.0 (built today from master 92f0815e) - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Debian GNU/Linux 12 (bookworm) - Desktop Environment: N/A
- Kernel version (
uname -r
): 6.1.0-rpi7-rpi-2712
Description of Problem:
When launching pipewire-aes67, Pipewire freezes (possibly during loop_update_io?). It is not possible to use pw-cli or pw-dump to interact with Pipewire.
This seems to be related to PTP, as with the PTP clock source commented out in pipewire-aes67.conf, Pipewire does not freeze. Unfortunately my experience with PTP on Linux is very limited, so please forgive me if this is simply a configuration error!
How Reproducible:
Can be reliably reproduced on a Raspberry Pi 5 with the default pipewire-aes67.conf. I am testing using ptp4l as the network's clock source.
I'm hoping pipewire-aes67 and Pi 5 could provide a low-cost, low-configuration method for audio and adjacent industries to connect [analog] devices to an AES67 network.
Steps to Reproduce:
- Build and compile Pipewire
- Start Pipewire as root (seems necessary to access /dev/ptp0)
Actual Results:
Pipewire becomes completely unresponsive on startup.
Expected Results:
Pipewire runs, either fine, or displaying an error about the clock if it's misconfigured.
Additional Info (as attachments):
-
pw-dump > pw-dump.log
: pw-dump cannot connect and hangs indefinitely -
PIPEWIRE_DEBUG=5 pipewire > debug.log
: see attached
pipewire-aes67.service:
[Unit]
Description=PipeWire Multimedia Service
Requires=pipewire.socket
[Service]
Type=simple
ExecStart=/usr/bin/pipewire-aes67
Restart=on-failure
RuntimeDirectory=pipewire
RuntimeDirectoryPreserve=yes
User=root
Environment=PIPEWIRE_DEBUG=5
Environment=PIPEWIRE_RUNTIME_DIR=%t/pipewire
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket
[Install]
Also=pipewire.socket pipewire-manager.socket
WantedBy=default.target