From: Linus Torvalds <torvalds@linux-foundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: akpm@linux-foundation.org, perex@perex.cz, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ALSA post-2.6.25-rc3 fixes
Date: Wed, 2 Apr 2008 10:09:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0804020952030.14670@woody.linux-foundation.org> (raw)
In-Reply-To: <s5hy793q13x.wl%tiwai@suse.de>
Takashi,
I just tried to suspend my mac mini with sound running on my box that I
test Fedora 9 on, and it all suspended and resumed ok, but on resume audio
didn't work.
I could restart the X session, and audio was ok, so the actual driver was
ok, but some state didn't restore well.
I *think* the problem may be due to this message which happened right
after the resume:
Apr 2 09:50:47 macmini pulseaudio[2296]: module-alsa-sink.c: Got POLLERR from ALSA
and I wonder what ALSA does over a suspend. Yes, it can be a pulseaudio
bug too (and even if it's not a pulseaudio bug I suspect pulseaudio could
work aroun this by re-initializing when it gets POLLERR), but the thing
is, suspend/resume *should* generally be invisible from user space!
So the POLLERR seems wrong, and I assume it is coming from
snd_pcm_playback_poll() and the runtime->status->state has been scrogged
by the suspend/resume cycle.
The PCM code seems to set the state to SNDRV_PCM_STATE_SUSPENDED on
suspend and resume it from suspended_state, but maybe there's some path
that misses this?
This is Intel HDA audio, in case it mattes (but none of the POLLERR code
seems to have anything to do with the low-level drivers).
Linus
prev parent reply other threads:[~2008-04-02 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 14:38 Takashi Iwai
2008-04-02 17:09 ` Linus Torvalds [this message]
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=alpine.LFD.1.00.0804020952030.14670@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®