Re: SV: Problems with sound on thin clients (Was: Unidentified subject!)

[George <joje47@yahoo.se>]

Hi Steven,

$ lsof -nnP | grep pcm

did not return anything. so maybe that is not the problem.

I turned on debug in lts.conf and got some nice :( errors in the log. After seeing that I tried an old booksized pc as thin client, and then I got sound that keeps working. At least for 10 minutes now ;)

I attach the log. It seems to be a problem with the Intel driver as I can see it. I don't really know what to do about it though. The log is not as long as it seems. I get double records for every instance in the log. Maybe because of the debug setting. Because it was not like that before. Anyway, thats a very minor problem.

Regards   /George



--- Den ons 2012-03-21 skrev Steven Chamberlain <steven@pyro.eu.org>:

Från: Steven Chamberlain <steven@pyro.eu.org>
Ämne: Re: SV: Problems with sound on thin clients (Was: Unidentified subject!)
Till: "George" <joje47@yahoo.se>
Kopia: debian-edu@lists.debian.org
Datum: onsdag 21 mars 2012 19:43

Hi,

On 21/03/12 13:41, George wrote:
> From syslog;
> Mar 21 14:25:46 ltsp24 pulseaudio[2662]: ratelimit.c: 331 events suppressed
> Mar 21 14:25:46 ltsp24 pulseaudio[2662]: ratelimit.c: 331 events suppressed
...

Before those messages you should see the original error.  Multiple
occurrences of the same error then get suppressed like this.

> When sound stops working I can see this in syslog;
> Mar 21 14:28:56 ltsp24 pulseaudio[2662]: alsa-source.c: snd_pcm_avail:
> Enhet eller resurs upptagen
> Mar 21 14:28:56 ltsp24 pulseaudio[2662]: alsa-source.c: snd_pcm_avail:
> Enhet eller resurs upptagen
> (Enhet eller resurs upptagen=resource busy)

"Device or resource busy" -- I think that means some other program is
directly opening the audio output device, before pulseaudio loads.  The
reason for pulseaudio is to avoid this sort of competition for access to
the audio device.  dmix is an alternative but could have other drawbacks.

You might be able to find the responsible program by running this at the
shell on the thin client:

$ lsof -nnP | grep pcm

Maybe something like 'timidity' is starting as a daemon and opens the
audio device, before the user logs in and pulseaudio starts.

Regards,
--
Steven Chamberlain
steven@pyro.eu.org

Attachment: alsa.log
Description: Binary data