Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752299AbaBNTB0 (ORCPT ); Fri, 14 Feb 2014 14:01:26 -0500 Received: from mail-ve0-f171.google.com ([209.85.128.171]:52377 "EHLO mail-ve0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbaBNTBZ (ORCPT ); Fri, 14 Feb 2014 14:01:25 -0500 MIME-Version: 1.0 In-Reply-To: References: <52FCFD92.7040109@hurleysoftware.com> Date: Sat, 15 Feb 2014 03:01:24 +0800 Message-ID: Subject: Re: Lenovo X240 (haswell) suspend-to-ram hangs on 3-14.0-rc2 From: Jeff Chua To: Takashi Iwai Cc: Peter Hurley , lkml , Dave Airlie Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 14, 2014 at 9:57 PM, Takashi Iwai 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/