linux-kernel - Re: Q: Why I do have to restart alsa everytime after a resume from disk/ram ? Is this alsa- or kernel or config related??

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2c0942db0912131527x118f9689oe1dc128543f4fc27@mail.gmail.com>
Date:	Sun, 13 Dec 2009 15:27:48 -0800
From:	Ray Lee <ray-lk@...rabbit.org>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	Christian Hartmann <cornogle@...glemail.com>,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: Q: Why I do have to restart alsa everytime after a resume from 
	disk/ram ? Is this alsa- or kernel or config related??

On Fri, Dec 11, 2009 at 4:00 PM, Robert Hancock <hancockrwd@...il.com> wrote:
> On 12/11/2009 03:21 AM, Christian Hartmann wrote:
>>
>> hello list,
>>
>> everytime I suspended to disk or to ram, regardless of the used kernel
>> (git or stable from distri), I must restart alsa to hear sound again.
>> searched google and tried a lot but still the same awful behaviour.
>> Has anybode some suggestions for me? is this alsa related ? or is this
>> a kernel issue which could be dealt here?
>
> I'm not sure what you mean by restarting ALSA, do you mean reloading the
> audio device module or something?
>
> You didn't mention which kind of sound hardware you were using either..

Data point: Older versions of PulseAudio are very picky about the
timing data that comes back from ALSA, and throws a hissy-fit and goes
and sulks if it believes it's getting lied to. Perhaps you need to try
upgrading the PulseAudio packages, and try again.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/