From: Allan, B. W <bru...@in...> - 2011-01-31 23:26:56
|
>-----Original Message----- >From: Nix [mailto:ni...@es...] >Sent: Monday, January 31, 2011 3:24 PM >To: Allan, Bruce W >Cc: e10...@li... >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue in >2.6.37 > >On 31 Jan 2011, Bruce W. Allan spake thusly: > >>>Because lspci simply reads the PCI configuration space (IIRC), I doubt it >>>is reporting incorrect information. The e1000e driver uses the kernel >>>API to disable ASPM (when CONFIG_PCIEASPM is enabled in the kernel config >>>otherwise it writes directly to the PCI configuration space to disable >>>ASPM). Assuming your kernel config has CONFIG_PCIEASPM enabled, my guess >>>at this point would be there is something broken in the kernel. With ASPM >>>L0s enabled, the 82574 (and other parts supported by the driver) will most >>>definitely have issues, so we need to find out what is broke and fix it. >> >> Since it does appear to be a problem with the kernel, a brute force method >> to work around the issue is to manually disable ASPM (I suggest first try >> disabling only ASPM L0s) using setpci. If disabling ASPM L0s is not enough >> then disable ASPM L1 in both the 82574 and upstream PCI bridge. > >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??? |