From: Takashi Iwai <tiwai@suse.de>
To: Christian Labisch <clnetbox@gmail.com>
Cc: gregkh@linuxfoundation.org,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Takashi Iwai <tiwai@suse.com>,
amadeuszx.slawinski@linux.intel.com
Subject: Re: Haswell audio no longer working with new Catpt driver
Date: Fri, 01 Jan 2021 13:09:09 +0100 [thread overview]
Message-ID: <s5h1rf4c10a.wl-tiwai@suse.de> (raw)
In-Reply-To: <088cd3b6ba6589266e316d6adcb76861edd18775.camel@gmail.com>
On Fri, 01 Jan 2021 12:10:23 +0100,
Christian Labisch wrote:
>
> Hi Lars,
>
> Thanks for your response, as requested I ran alsa-info while playing audio.
> Please check the attached information - to me it looks like it being a bug.
> It should affect many users, will it be solved in the next release 5.10.5 ?
It's likely some runtime PM-related changes that caused this behavior
change. But, there must be some program that sets the power_save
option explicitly on your system. As dmesg shows, the default
power_save to this device has been suppressed, but it's activated by
the later action. On, 5.9.x, this didn't take effect, but on 5.10.x,
this became effective, as it seems.
You can try to pass power_save=0 option to snd-hda-intel module (or
boot with snd_hda_intel.power_save=0 boot option). It could work
around the issue, although it's no solution.
thanks,
Takashi
next prev parent reply other threads:[~2021-01-01 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:26 sound Christian Labisch
2020-12-30 15:36 ` sound Greg KH
2020-12-30 15:45 ` sound Christian Labisch
2020-12-30 18:10 ` sound Christian Labisch
2020-12-31 8:33 ` sound Greg Kroah-Hartman
2020-12-31 10:04 ` Haswell audio no longer working with new Catpt driver (was: sound) Lars-Peter Clausen
2020-12-31 10:04 ` Lars-Peter Clausen
2020-12-31 10:50 ` Christian Labisch
2020-12-31 10:50 ` Christian Labisch
2020-12-31 11:20 ` Haswell audio no longer working with new Catpt driver Amadeusz Sławiński
2020-12-31 11:20 ` Amadeusz Sławiński
2020-12-31 11:31 ` Christian Labisch
2020-12-31 11:31 ` Christian Labisch
[not found] ` <1ad341b1b0e0eefb83d157ac24d162eaad53ab32.camel@gmail.com>
2020-12-31 15:30 ` Lars-Peter Clausen
2021-01-01 11:10 ` Christian Labisch
2021-01-01 12:09 ` Takashi Iwai [this message]
2021-01-01 13:25 ` Christian Labisch
2021-01-01 13:29 ` Lars-Peter Clausen
2021-01-01 13:40 ` Christian Labisch
2021-01-01 17:24 ` Takashi Iwai
2021-01-02 11:50 ` Christian Labisch
2021-01-02 12:16 ` Greg KH
2020-12-31 11:10 ` Haswell audio no longer working with new Catpt driver (was: sound) Christian Labisch
2020-12-31 11:10 ` Christian Labisch
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=s5h1rf4c10a.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=clnetbox@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=tiwai@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.