From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754295Ab2D2Qp2 (ORCPT ); Sun, 29 Apr 2012 12:45:28 -0400 Received: from icebox.esperi.org.uk ([81.187.191.129]:49540 "EHLO mail.esperi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752867Ab2D2Qp0 (ORCPT ); Sun, 29 Apr 2012 12:45:26 -0400 From: Nix To: Jesse Brandeburg Cc: Chris Boot , , , , Subject: Re: [PATCH RFC 0/2] e1000e: 82574 also needs ASPM L1 completely disabled References: <9BBC4E0CF881AA4299206E2E1412B6260E512E0C@ORSMSX102.amr.corp.intel.com> <1335216578-21542-1-git-send-email-bootc@bootc.net> <20120423161119.0000022f@unknown> Emacs: the prosecution rests its case. Date: Sun, 29 Apr 2012 17:45:10 +0100 In-Reply-To: <20120423161119.0000022f@unknown> (Jesse Brandeburg's message of "Mon, 23 Apr 2012 16:11:19 -0700") Message-ID: <87y5pe1o89.fsf@spindle.srvr.nix> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-DCC-wuwien-Metrics: spindle 1290; Body=6 Fuz1=6 Fuz2=6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24 Apr 2012, Jesse Brandeburg outgrape: > Please let us know the results of your testing, we will let you know if > we see any issues as well. Alas, it has no effect at all here; L0s and L1 claim to be being disabled at boot time, but if you ask with lspci you see that they are not. I strongly suspect that they *are* being disabled, but then get re-enabled by something else, because even if I force them off with setpci in the boot scripts, by the time the scripts have finished executing and I've got to a root prompt where I can run setpci, L0s and L1 are always back on again. I may try simply running setpci between every line of my boot scripts just to see if it's something I'm doing there, but I very much doubt it, since I see these symptoms even if I run setpci at a point in the boot scripts after all the network interface setup is over. I suspect it's more to do with the link stabilizing or something. (But this is purest guesswork.) [ 1.087592] e1000e 0000:03:00.0: Disabling ASPM L0s L1 [ 1.211748] e1000e 0000:02:00.0: Disabling ASPM L0s L1 spindle# setpci -s 02:00.0 CAP_EXP+10.b 43 spindle# setpci -s 03:00.0 CAP_EXP+10.b 43 spindle:/etc/rc.d# lspci -vv -s 02:00.0 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: Intel Corporation Device 0000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR-