[LAU] Pulse Problem

Paul Davis paul at linuxaudiosystems.com
Mon Sep 23 20:32:34 UTC 2013

On Mon, Sep 23, 2013 at 4:21 PM, İzlem Gözükeleş <izlemg at gmail.com> wrote:

> On Mon, Sep 23, 2013 at 10:39 PM, Paul Davis <paul at linuxaudiosystems.com>wrote:
>> On Mon, Sep 23, 2013 at 3:12 PM, İzlem Gözükeleş <izlemg at gmail.com>wrote:
>> the message you pasted seems likely to be relevant:
>>    Sep 23 21:13:07 ank-yay7-30 pulseaudio[25029]: [alsa-sink]
>> alsa-sink.c: ALSA woke us up to write new data to the device, but there was
>> actually nothing to write!
>>    Sep 23 21:13:07 ank-yay7-30 pulseaudio[25029]: [alsa-sink]
>> alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_lola'.
>> Please report this issue to the ALSA developers.
>>    Sep 23 21:13:07 ank-yay7-30 pulseaudio[25029]: [alsa-sink]
>> alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent
>> snd_pcm_avail() returned 0 or another value < min_avail."
>> why not start there?
> First, error logs always start with the lines as "Sep 23 21:08:58
> ank-yay7-30 pulseaudio[25025]: [pulseaudio] main.c: User-configured server
> at {d25201022b82858589f672715226f35f}unix:/tmp/pu
> lse-hQ0f0Qxjni5j/native, which appears to be local. Probing deeper."
> And in this example, we got error message about snd_lola 4 minutes after
> this message (Sound is lost during 21:08).
> Second, this alsa error message appears rarely. For example, we didn't
> have this problem on the previous system error. Yet. we always see this
> message after system is started without any apparent problem. Furthermore,
> we get the same error message with layla 3g againg without any apparent
> problem on the playing sound after boot.
> As a result, the above sound problem message seems as a consequence of
> another problem.
> Maybe I am wrong. But I cannot debug a problem that happens after 5 days
> (~5 x 17 hours of playing music).
> Where should I start?

unfortunately nothing that you've said here invalidates the idea that it
could be an issue with the ALSA driver - an issue that only shows up after
many hours of continuous playback. you would have to add debugging output
to the ALSA driver to track what it thinks is happening.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-user/attachments/20130923/e72d749a/attachment.html>

More information about the Linux-audio-user mailing list