From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753179Ab3GXPT7 (ORCPT ); Wed, 24 Jul 2013 11:19:59 -0400 Received: from mga03.intel.com ([143.182.124.21]:6309 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752031Ab3GXPT6 convert rfc822-to-8bit (ORCPT ); Wed, 24 Jul 2013 11:19:58 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,736,1367996400"; d="scan'208";a="272610618" From: "Wyborny, Carolyn" To: Bjorn Helgaas , Pavel Machek CC: Greg KH , kernel list , Joe Lawrence , Myron Stowe , "Kirsher, Jeffrey T" , "Brandeburg, Jesse" , "Allan, Bruce W" , "Skidmore, Donald C" , "Rose, Gregory V" , "Waskiewicz Jr, Peter P" , "Duyck, Alexander H" , "Ronciak, John" , "Dave, Tushar N" , "e1000-devel@lists.sourceforge.net" Subject: RE: /sys/module/pcie_aspm/parameters/policy not writable? Thread-Topic: /sys/module/pcie_aspm/parameters/policy not writable? Thread-Index: AQHOfae/YJf6t4xSdkSmx+6rM4DMuJlhWxyAgAtunQCABzyS4A== Date: Wed, 24 Jul 2013 15:19:55 +0000 Message-ID: <9BBC4E0CF881AA4299206E2E1412B6264F921872@ORSMSX102.amr.corp.intel.com> References: <20130709012611.GA22371@amd.pavel.ucw.cz> <20130709041321.GA30555@kroah.com> <20130709094906.GA3870@amd.pavel.ucw.cz> <20130709101039.GA4479@amd.pavel.ucw.cz> <20130710132950.GA3684@amd.pavel.ucw.cz> <20130712111121.GB3515@amd.pavel.ucw.cz> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > -----Original Message----- > From: Bjorn Helgaas [mailto:bhelgaas@google.com] [..} > > We *could* consider something like this, since its scope is limited. > But since the problem also occurs with Windows, it's pretty likely that there's a > BIOS update to fix it. I notice on the X60 support page that there are several > versions newer than what you're running. > > Bjorn I believe that some BIOS don't allow user control on this feature, thus we end up unable to disable it from driverspace or from userspace, with the method we use today in this scenario. I have a patch almost ready that attempts to disable using the pci_disable_link_state() call but then checks again to see if its still enabled and if not, then changes the pci config space on the devices on either side of the pcie link. I plan to send it to this list for Pavel's testing as soon as I have it finished, at worst end of week. Thanks, Carolyn Carolyn Wyborny Linux Development Networking Division Intel Corporation