Bug 91606 - Native protocol usage results in "Client sent non-aligned memblock" messages from server
Summary: Native protocol usage results in "Client sent non-aligned memblock" messages ...
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: clients (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-11 12:32 UTC by Ben Gamari
Modified: 2018-07-30 10:20 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Ben Gamari 2015-08-11 12:32:32 UTC
I am attempting to stream audio with pulseaudio's native protocol from a laptop running Debian testing (running pulseaudio 6.0) and a desktop also running Debian testing (running pulseaudio 6.0).

I have configured the server to expose its devices for anonymous use with,

    load-module module-native-protocol-tcp auth-anonymous=1
    load-module module-zeroconf-publish

in /etc/pulse/default.pa. As the desktop is headless, I ssh in to the machine and start pulseaudio manually so I can observe its output. paplay'ing an audio file on the server produces the expected audio output.

As expected, the server's analog sink is shown in padevchooser on the laptop. However, if I select the device to be the laptop's default sink and play audio with rhythmbox, the server begins spewing messages of the form,

    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 7140, length 1052, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 2856, length 4284, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 7140, length 196, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 0, length 4284, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 4284, length 3908, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 2856, length 1428, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 4284, length 3908, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 0, length 4284, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 4284, length 2580, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 0, length 4364, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 4364, length 1348, frame size: 8
    W: [pulseaudio] protocol-native.c: Client sent non-aligned memblock: index 0, length 1428, frame size: 8

and no audio output is produced.

Intriguingly, paplay'ing the same file from the laptop simply hangs with no audio output. stracing the process shows that is hung on a poll syscall [1].


[1] https://gist.github.com/bgamari/845b10900c79a5e81bce
Comment 1 Ben Gamari 2015-08-11 12:46:07 UTC
paplay run with -v reveals the following,

$ paplay gd73-12-08d1t02.shn.ogg  -v
Opening a playback stream with sample specification 'float32le 2ch 44100Hz' and channel map 'front-left,front-right'.
Connection established.
Stream successfully created.
Buffer metrics: maxlength=4194304, tlength=705600, prebuf=698552, minreq=7056
Using sample spec 'float32le 2ch 44100Hz', channel map 'front-left,front-right'.
Connected to device alsa_output.pci-0000_00_1b.0.analog-stereo (index: 1, suspended: no).
Time: 0.035 sec; Latency: 215449 usec.
[hangs here]
Comment 2 Ben Gamari 2015-08-11 12:47:32 UTC
It appears that each invocation of the paplay command above produces one block of 85 "Client sent non-aligned memblock" messages on the server.
Comment 3 Ben Gamari 2015-08-11 12:48:49 UTC
(In reply to Ben Gamari from comment #2)
> It appears that each invocation of the paplay command above produces one
> block of 85 "Client sent non-aligned memblock" messages on the server.

Actually, it seems that observation may have been a statistical fluke; the number of messages is actually fairly arbitrary, but typically somewhere around 100.
Comment 4 GitLab Migration User 2018-07-30 10:20:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/363.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.