Nothing jumped out at me when I checked, but here's the documentation check I did to see if there was something obvious. First, download the specification update for your part (go to intel.com and search for "82571EB spec update"). Then, check the release date for your driver (I usually just check e1000.sourceforge.net and look at the dates for the files there). You should be able to look at the changes in the spec update and everything after the time of your driver release is new, but should be fixed in later drivers.
Hope that helps. Todd Fujinaka Software Application Engineer Networking Division (ND) Intel Corporation [email protected] (503) 712-4565 -----Original Message----- From: Paul [mailto:[email protected]] Sent: Tuesday, June 04, 2013 7:29 PM To: Dave, Tushar N Cc: [email protected] Subject: Re: [E1000-devel] Abnormal link down after running long time Dave, Thanks for your suggestion. The server is running something important traffic. I worry that upgrading the driver will cause other stability problems. If the old driver was possible to cause my problems, then I will have to replace it. Thanks, Paul On Wed, Jun 5, 2013 at 3:08 AM, Dave, Tushar N <[email protected]>wrote: > >-----Original Message----- > >From: Paul [mailto:[email protected]] > >Sent: Tuesday, June 04, 2013 12:14 AM > >To: [email protected] > >Subject: [E1000-devel] Abnormal link down after running long time > > > >Hi, All, > > > >I met a strange NIC link down problem and couldn't find any useful > >clues by now. > > > >I ran RHEL6.0 (kernel version: 2.6.32.71), and used Intel 82571EB > >Gigabit Ethernet Controller. The version of e1000e driver was 1.2.7, > >which was the original version in RHEL6.0. My system could run for > >several months, but suddenly saw these messages in log: > >May 19 18:46:37 (none) kernel: e1000e: eth1 NIC Link is Down May 19 > >18:46:39 (none) kernel: e1000e: eth1 NIC Link is Up 1000 Mbps Full > >Duplex, Flow Control: RX/TX Then eth1 couldn't be used any more. I > >checked the cables and the switch. > >Both had no problems. After rebooting the system and not touching > >anything else, then it could work again. > > > >Previously I didn't notice this problem. But now I viewed the old > >logs and found it happened for several times. Each time the system > >could run for several months. The network traffic over the NIC was not heavy. > > > >This problem could be reproduced on another hardware with the same > >hardware and software configuration. > > > >Is it related to a bug of e1000e? The driver version 1.2.7 seems very old. > >Is it useful if I upgrade the driver? > Yes, the driver you are using is very old. It is a good idea to try > recently released driver. > http://sourceforge.net/projects/e1000/files/?source=navbar > > -Tushar > ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ 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
