On 1/31/2011 4:06 PM, Allan, Bruce W wrote: >> -----Original Message----- >> From: Nix [mailto:n...@esperi.org.uk] >> Sent: Monday, January 31, 2011 3:31 PM >> To: Allan, Bruce W >> Cc: e1000-devel@lists.sourceforge.net >> Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes >> continue in >> 2.6.37 >> >> On 31 Jan 2011, Bruce W. Allan spake thusly: >> >>>> From: Nix [mailto:n...@esperi.org.uk] >>>> I'm not so sure anymore. In 2.6.35.4, everything works -- but in 2.6.35.4, >>>> the lspci output is *exactly the same*, i.e. even there lspci claims that >>>> ASPM L0s and L1 are enabled. This seems unlikely, since even if the L0s/L1 >>>> state persists across a poweroff, the problem disappears upon a simple >>>> reboot into 2.6.35.4, and does not recur in that kernel release. >>> >>> Which kernel versions? The above mentioned are all the same??? >> >> Yes. 2.6.35.4..2.6.37 have no differences whatsoever in their lspci output >> for my 82574L cards. >> >> I am... confuzzled, but am happy to try turning L0s/L1 off (if I can >> figure out how to do it: setpci is... not the most friendly of tools >> and I've never even looked at its manpage before). > > ASPM is enabled/disabled via bits 1:0 of byte 16 in the Express Endpoint > capability register. First see what is in this byte with the following: > > # setpci -s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] CAP_EXP+10.b > > where [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] is the slot information > for your 82574. I'm guessing that command will return 43 (hex) to indicate > ASPM L0s (bit 0) and ASPM L1 (bit 1) are both enabled based on your previous > lspci output. Now, re-write the byte with bits 1:0 set to 10b (or 42 hex) > to disable ASPM L0s: > > # setpci -s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] CAP_EXP+10.b=42 > > or 00b (40 hex) to disable both ASPM L0s and L1: > > # setpci -s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] CAP_EXP+10.b=40 > > and verify with 'lspci -vvv' that ASPM L0s [and L1] are disabled.
Please, for our benefit, file a bug at e1000.sf.net (if you have not already) so you can attach the .config and full dmesg file from a non-working kernel, also please attach the full lspci -vvv output. The reason I'm asking for this is that the kernel may actually be configured to not do aspm at all (CONFIG_ASPM=n), but it still is "helpful" by printing strings like it did something[1] [1] http://lxr.linux.no/linux+v2.6.37/include/linux/pci-aspm.h#L41 ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
