From: Robert Hancock <hancockrwd@gmail.com>
To: Christian Hartmann <cornogle@googlemail.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-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??
Date: Sun, 13 Dec 2009 14:30:09 -0600 [thread overview]
Message-ID: <4B254ED1.5040805@gmail.com> (raw)
In-Reply-To: <ffd8902a0912121351x3b29bcf8pc402f77cba7afa88@mail.gmail.com>
On 12/12/2009 03:51 PM, Christian Hartmann wrote:
> sorry,
>
> here are some logs&& configs attached:
>
> cheers
> chris
>
> 2009/12/12 Robert Hancock<hancockrwd@gmail.com>:
>> 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?
>>
That might help, but you didn't actually answer either of these questions:
>> 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..
>>
next prev parent reply other threads:[~2009-12-13 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 9:21 Q: Why I do have to restart alsa everytime after a resume from disk/ram ? Is this alsa- or kernel or config related?? Christian Hartmann
2009-12-12 0:00 ` Robert Hancock
2009-12-12 21:51 ` Christian Hartmann
2009-12-13 20:30 ` Robert Hancock [this message]
2009-12-13 23:27 ` Ray Lee
2009-12-14 15:16 ` Christian Hartmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B254ED1.5040805@gmail.com \
--to=hancockrwd@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=cornogle@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox