Re: [LAU] Pulse Problem

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: İzlem Gözükeleş <izlemg@...>
Cc: linux-audio-user <linux-audio-user@...>
Date: Monday, September 23, 2013 - 8:32 pm

--047d7b6dd05e917dcd04e712ebc1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 23, 2013 at 4:21 PM, =C4=B0zlem G=C3=B6z=C3=BCkele=C5=9F wrote:

>

wrote:
was
r
,

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.

--047d7b6dd05e917dcd04e712ebc1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 23, 2013 at 4:21 PM, =C4=B0zlem G=C3=B6z=C3=BCkele=C5=
=9F <izlemg@gmail.com> wrote:
On Mon, Sep 23, 2013 at 10=
:39 PM, Paul Davis <paul@linuxaudiosystems.com> wro=
te:

=

On Mon, Sep 23, 2013 at 3:12 PM, =C4=B0zlem G=C3=B6z=C3=BCkele=C5=9F <=
span dir=3D"ltr"><=
izlemg@gmail.com
> wrote:th=
e message you pasted seems likely to be relevant:

=C2=A0=C2=A0=C2=A0 Sep 23 21:13:07 ank-yay7-30 pulseau=
dio[25029]: [alsa-sink]=20
alsa-sink.c: ALSA woke us up to write new data to the device, but there=20
was actually nothing to write!=C2=A0=C2=A0 Sep 23 21:=
13:07 ank-yay7-30 pulseaudio[25029]: [alsa-sink]=20
alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_lola&#39=
;.=20
Please report this issue to the ALSA developers.=C2=A0=C2=A0 Sep 2=
3 21:13:07 ank-yay7-30 pulseaudio[25029]: [alsa-sink]=20
alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent=20
snd_pcm_avail() returned 0 or another value < min_avail."why not start there?=

First, error logs always start with the lines as "S=
ep 23 21:08:58 ank-yay7-30 pulseaudio[25025]: [pulseaudio] main.c: User-con=
figured 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 exa=
mple, we didn't have this problem on the previous system error. Yet. we=
always see this message after system is started without any apparent probl=
em. 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 p=
laying 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 af=
ter many hours of continuous playback. you would have to add debugging outp=
ut to the ALSA driver to track what it thinks is happening.

--047d7b6dd05e917dcd04e712ebc1--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Pulse Problem, İzlem Gözükeleş, (Mon Sep 23, 7:12 pm)
Re: [LAU] Pulse Problem, Paul Davis, (Mon Sep 23, 7:40 pm)
Re: [LAU] Pulse Problem, İzlem Gözükeleş, (Mon Sep 23, 8:21 pm)
Re: [LAU] Pulse Problem, Paul Davis, (Mon Sep 23, 8:32 pm)