From: Takashi Iwai <tiwai@suse.de>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
lkml <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: Lenovo X240 (haswell) suspend-to-ram hangs on 3-14.0-rc2
Date: Fri, 14 Feb 2014 21:07:35 +0100 [thread overview]
Message-ID: <s5hk3cxzce0.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAAJw_ZtviRCtaC4-3_ubkYuEt+LYstwbi6qus-5GOoOLYhfecw@mail.gmail.com>
At Sat, 15 Feb 2014 03:01:24 +0800,
Jeff Chua wrote:
>
> On Fri, Feb 14, 2014 at 9:57 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > The other possible change in hda_intel.c is the enablement of runtime
> > PM for Panther Point. But it's been working for other chips, so
> > wondering why it hits anything. In anyway, please give the full
> > Oops messages not only the stack trace.
>
> > Any difference in the sound hardware, i.e. PCI controller and codec
> > chips?
>
> # X230 reported the sound card as:
> 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
> Family High Definition Audio Controller (rev 04)
> == HDA Intel PCH, ALC269VC Analog
>
> # X240 reported the sound card as:
> 00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio
> Controller (rev 04)
> == HDA Intel PCH, ALC292 Analog
>
> Now I managed to make suspend-to-ram work by using sound as module
> instead of build-in.
>
> Here's the difference ...
>
> # bad
> CONFIG_SND_HDA_CODEC_HDMI =y
> CONFIG_SND_HDA_INTEL=y
> CONFIG_SND_HDA_INPUT_BEEP=y
> CONFIG_SND_HDA_CODEC_HDMI=y
> CONFIG_SND_HDA_GENERIC=y
>
>
> # good
> CONFIG_SND_HDA_CODEC_HDMI =m
> CONFIG_SND_HDA_INTEL=m
> CONFIG_SND_HDA_INPUT_BEEP=m
> CONFIG_SND_HDA_CODEC_HDMI=m
> CONFIG_SND_HDA_GENERIC=m
It might be the remaining bugs of modularization in 3.14-rc2.
A few patches are found in for-linus branch of sound git tree, which
are included in Today's pull request. Could you give it a try?
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-linus
Takashi
next prev parent reply other threads:[~2014-02-14 20:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 13:02 Jeff Chua
2014-02-13 17:14 ` Peter Hurley
2014-02-13 17:28 ` Takashi Iwai
2014-02-13 21:21 ` Theodore Ts'o
2014-02-14 13:46 ` Jeff Chua
2014-02-14 13:57 ` Takashi Iwai
2014-02-14 14:00 ` Peter Hurley
2014-02-14 19:01 ` Jeff Chua
2014-02-14 19:10 ` Steven Noonan
2014-02-14 20:07 ` Takashi Iwai [this message]
2014-02-17 17:54 ` Jeff Chua
2014-02-17 19:54 ` Theodore Ts'o
2014-02-18 19:06 ` Theodore Ts'o
2014-02-18 20:28 ` Takashi Iwai
2014-02-18 21:32 ` Theodore Ts'o
2014-02-19 2:01 ` Jeff Chua
2014-02-27 12:01 ` Takashi Iwai
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=s5hk3cxzce0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=airlied@redhat.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.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 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®