OK, that's great news! I'll check into why ASPM is not getting set correctly by the kernel.
>-----Original Message----- >From: Nix [mailto:n...@esperi.org.uk] >Sent: Wednesday, February 09, 2011 12:24 PM >To: Allan, Bruce W >Cc: Jesse Brandeburg; e1000-devel@lists.sourceforge.net >Subject: Re: [E1000-devel] 82754L spontaneous freeze networking woes continue >in >2.6.37 > >On 2 Feb 2011, n...@esperi.org.uk uttered the following: > >> 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. > >Update: After a week of testing, it does indeed appear that > >setpci -s 02:00.0 CAP_EXP+10.b=40 > >(where 02:00.0 is the PCI address of the 82754L which is running in >gigabit mode) fixes it in 2.6.36+: I have had no recurrences of sudden >NIC 0xff register death, and without this they happened on an almost >daily and sometimes hourly basis. Of course the question is why the >code to flip this automatically, isn't... ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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
