On 1 Feb 2011, Bruce W. Allan stated: >>From: Jesse Brandeburg [mailto:jesse.brandeb...@gmail.com] >>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.
Done! Bug 3170405. There's lspci output from a working kernel too. > Actually, when CONFIG_ASPM=n the e1000e driver will forcibly disable ASPM > by directly writing to the PCI config space instead of using the kernel > API. ... but the PCI configuration space shows that even in 2.6.35.x (which did not have ASPM kernel support as I recall, and which works for me perfectly well with no freezing NICs), L0s and L1 are active. This is getting more confusing by the moment. > So, I doubt that is how CONFIG_ASPM is set. But I agree, a bug filed > on SourceForge should be done for better tracking of this issue and an > owner can be properly assigned. Sorry for not doing it initially, but I have an allergy to SourceForge's impossibly slow and clumsy user interface :) it seems to have improved a bit recently though. ------------------------------------------------------------------------------ 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
