Nix wrote: > On 4 Nov 2010, Jesse Brandeburg spake thusly: >> The above could be responsible for your issue. If you don't want to >> disable ASPM system wide, then you could just make sure to run a >> recent kernel with the ASPM patches, or get our e1000.sf.net e1000e >> driver and try it, as it will work around the issue whether or not >> aspm is enabled. > > For the record, cherry-picking > ff10e13cd06f3dbe90e9fffc3c2dd2057a116e4b (the periodic > phy-crash-and-reset check) atop 2.6.36 seems to have fixed it: at > least, the machine has been up for a day now without trouble. This > commit doesn't seem to be in Greg's stable-queue yet, but seems like > a good candidate.
This patch should have no effect on your issue if it is indeed ASPM related. The ASPM issue can be intermittent and I have seen systems run for 3-5 days until the failure occurs, so one day doesn't necessarily rule it out. BTW - what is the exact make/model of your system (dmidecode). Thanks, Emil ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
