On Fri, Feb 14, 2014 at 11:01 AM, Jeff Chua <jeff.chua.li...@gmail.com> wrote: > On Fri, Feb 14, 2014 at 9:57 PM, Takashi Iwai <ti...@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 > > > Strange? > > Jeff
Of those modules, which are loaded? If you load all of them and then try to suspend, does it still work? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
