Thanks Kristian, If you really are having the EEPROM corrupted this is highly unusual. The motherboards all look to have our devices down on them . So they aren't really NIC's right? (i.e. plug in PCIe boards) Are you having power issues or something like that? Are you seeing other strangeness with the motherboards? Like other devices having issues?
Cheers, John > -----Original Message----- > From: Kristian Kielhofner [mailto:[email protected]] > Sent: Thursday, September 27, 2012 12:04 PM > To: Ronciak, John > Cc: Dave, Tushar N; [email protected] > Subject: Re: [E1000-devel] 82574L issues with e1000e > > Hello John, > > This system is a Lex Atom D525 based system: > > http://www.lex.com.tw/product/SbcBoard-home-Pineview.htm > > There are four 82574L NICs in our configuration. These systems all > worked at some point but more and more we're starting to see this error > across our entire installed base. > > On Thu, Sep 27, 2012 at 1:48 PM, Ronciak, John <[email protected]> > wrote: > > Also what is the system HW these NIC's are being plugged into? Were > these systems working at some point but are now seeing this issue with > the same HW? > > > > Cheers, > > John > > > > > >> -----Original Message----- > >> From: Dave, Tushar N [mailto:[email protected]] > >> Sent: Thursday, September 27, 2012 10:45 AM > >> To: Kristian Kielhofner; [email protected] > >> Subject: Re: [E1000-devel] 82574L issues with e1000e > >> > >> >-----Original Message----- > >> >From: Kristian Kielhofner [mailto:[email protected]] > >> >Sent: Thursday, September 27, 2012 9:46 AM > >> >To: [email protected] > >> >Subject: [E1000-devel] 82574L issues with e1000e > >> > > >> >Hello everyone, > >> > > >> > We've been experiencing a slew of issues with our 82574L chips > and > >> >the e1000e driver. We have several of these units in the field. > >> >We're using a vanilla kernel 2.6.27.49 with e1000e 2.1.4. Kernel > >> >and hardware supports MSI-X but changing these options (IntMode=1 > >> >and disabling MSI-X globally) has no effect. Kernel is booted with > >> >pcie_aspm=off and we run the following setpci commands on boot: > >> > >> The problem is " probe of 0000:04:00.0 failed with error -2" > >> Just want to check are you running this in virtualized environment? > >> > >> Does this issue occur with driver update? Was it occurring with > >> previous versions of e1000e driver? > >> > >> -Tushar > >> > > >> >setpci -s 01:00.0 CAP_EXP+10.b=40 > >> >setpci -s 02:00.0 CAP_EXP+10.b=40 > >> >setpci -s 03:00.0 CAP_EXP+10.b=40 > >> >setpci -s 04:00.0 CAP_EXP+10.b=40 > >> > > >> > We (typically) discover the eeprom corruption issue addressed > with > >> >this patch as well: > >> > > >> > >http://sourceforge.net/projects/e1000/files/e1000e%20stable/eeprom_f > >> >ix > >> _ > >> >825 > >> >74_or_82583/ > >> > > >> > and apply it to affected units (even though our kernel isn't > >> compiled > >> >with FTRACE): > >> > > >> >grep -i ftrace .config > >> >CONFIG_HAVE_FTRACE=y > >> >CONFIG_HAVE_DYNAMIC_FTRACE=y > >> ># CONFIG_FTRACE is not set > >> > > >> > e1000e driver is compiled with "EXTRA_CFLAGS=-DDEBUG" . > >> > > >> > Even with all of these fixes and precautions we find that we > >> >typically "lose" at least one (if not two) out of the four > >> >interfaces on this > >> >system: > >> > > >> >e1000e 0000:01:00.0: eth0: Masking off all interrupts e1000e > >> 0000:01:00.0: > >> >eth0: Issuing a global reset to MAC e1000e 0000:01:00.0: eth0: > >> >Initializing the IEEE VLAN e1000e 0000:01:00.0: eth0: Programming > >> >MAC Address into RAR[0] e1000e 0000:01:00.0: eth0: Clearing > >> >RAR[1-14] e1000e > >> >0000:01:00.0: eth0: Zeroing the MTA e1000e 0000:01:00.0: eth0: > After > >> >fix- ups FlowControl is now = 3 e1000e 0000:01:00.0: eth0: > >> >Reconfiguring auto- neg advertisement params e1000e 0000:01:00.0: > >> eth0: > >> >autoneg_advertised 2f e1000e 0000:01:00.0: eth0: Advertise 10mb > Half > >> duplex e1000e 0000:01:00.0: > >> >eth0: Advertise 10mb Full duplex e1000e 0000:01:00.0: eth0: > >> >Advertise 100mb Half duplex e1000e 0000:01:00.0: eth0: Advertise > >> >100mb Full duplex e1000e 0000:01:00.0: eth0: Advertise 1000mb Full > >> >duplex e1000e > >> >0000:01:00.0: eth0: Auto-Neg Advertising de1 e1000e 0000:01:00.0: > >> eth0: > >> >Restarting Auto-Neg e1000e 0000:01:00.0: eth0: Unable to establish > >> link!!! > >> >e1000e 0000:01:00.0: eth0: Initializing the Flow Control address, > >> >type and timer regs e1000e 0000:01:00.0: PCI INT A disabled e1000e > >> 0000:01:00.0: > >> >Disabling ASPM L0s L1 e1000e 0000:01:00.0: PCI INT A -> GSI 16 > >> >(level, > >> >low) -> IRQ 16 e1000e 0000:01:00.0: setting latency timer to 64 > >> >e1000e > >> >0000:01:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic > >> >conservative mode e1000e 0000:01:00.0: (unregistered net_device): > >> >Masking off all interrupts e1000e 0000:01:00.0: (unregistered > >> >net_device): Issuing a global reset to MAC e1000e 0000:01:00.0: > >> (unregistered net_device): > >> >Masking off all interrupts e1000e 0000:01:00.0: (unregistered > >> net_device): > >> >Issuing a global reset to MAC e1000e 0000:01:00.0: (unregistered > >> >net_device): Initializing the IEEE VLAN e1000e 0000:01:00.0: > >> >(unregistered > >> >net_device): Programming MAC Address into RAR[0] e1000e > 0000:01:00.0: > >> >(unregistered net_device): Clearing RAR[1-14] e1000e 0000:01:00.0: > >> >(unregistered net_device): Zeroing the MTA e1000e 0000:01:00.0: > >> >(unregistered net_device): After fix-ups FlowControl is now = 3 > >> >e1000e > >> >0000:01:00.0: (unregistered net_device): Reconfiguring auto-neg > >> >advertisement params e1000e 0000:01:00.0: (unregistered > net_device): > >> >autoneg_advertised 2f e1000e 0000:01:00.0: (unregistered > net_device): > >> >Advertise 10mb Half duplex e1000e 0000:01:00.0: (unregistered > >> net_device): > >> >Advertise 10mb Full duplex e1000e 0000:01:00.0: (unregistered > >> net_device): > >> >Advertise 100mb Half duplex e1000e 0000:01:00.0: (unregistered > >> >net_device): Advertise 100mb Full duplex e1000e 0000:01:00.0: > >> >(unregistered net_device): Advertise 1000mb Full duplex e1000e > >> >0000:01:00.0: (unregistered net_device): Auto-Neg Advertising de1 > >> >e1000e > >> >0000:01:00.0: (unregistered net_device): Restarting Auto-Neg e1000e > >> >0000:01:00.0: (unregistered net_device): Unable to establish > link!!! > >> >e1000e 0000:01:00.0: (unregistered net_device): Initializing the > >> >Flow Control address, type and timer regs e1000e 0000:01:00.0: > eth0: > >> >(PCI Express:2.5GT/s:Width x1) 4c:02:89:08:ca:02 e1000e > 0000:01:00.0: eth0: > >> >Intel(R) PRO/1000 Network Connection e1000e 0000:01:00.0: eth0: NVM > >> PBA > >> >number is not stored as string e1000e 0000:01:00.0: eth0: MAC: 4, > PHY: > >> >8, PBA No: FFFFFF-0FF e1000e 0000:02:00.0: Disabling ASPM L0s L1 > >> e1000e > >> >0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 e1000e > >> >0000:02:00.0: setting latency timer to 64 e1000e 0000:02:00.0: > >> >Interrupt Throttling Rate (ints/sec) set to dynamic conservative > >> >mode e1000e > >> >0000:02:00.0: (unregistered net_device): Masking off all interrupts > >> >e1000e > >> >0000:02:00.0: (unregistered net_device): Issuing a global reset to > >> >MAC e1000e 0000:02:00.0: (unregistered net_device): Masking off all > >> >interrupts e1000e 0000:02:00.0: (unregistered net_device): Issuing > a > >> >global reset to MAC e1000e 0000:02:00.0: (unregistered net_device): > >> >Initializing the IEEE VLAN e1000e 0000:02:00.0: (unregistered > >> >net_device): Programming MAC Address into RAR[0] e1000e > 0000:02:00.0: > >> (unregistered net_device): > >> >Clearing RAR[1-14] e1000e 0000:02:00.0: (unregistered net_device): > >> >Zeroing the MTA e1000e 0000:02:00.0: (unregistered net_device): > >> >After fix-ups FlowControl is now = 3 e1000e 0000:02:00.0: > >> >(unregistered > >> net_device): > >> >Reconfiguring auto-neg advertisement params e1000e 0000:02:00.0: > >> >(unregistered net_device): autoneg_advertised 2f e1000e > 0000:02:00.0: > >> >(unregistered net_device): Advertise 10mb Half duplex e1000e > >> 0000:02:00.0: > >> >(unregistered net_device): Advertise 10mb Full duplex e1000e > >> 0000:02:00.0: > >> >(unregistered net_device): Advertise 100mb Half duplex e1000e > >> >0000:02:00.0: (unregistered net_device): Advertise 100mb Full > duplex > >> >e1000e 0000:02:00.0: (unregistered net_device): Advertise 1000mb > >> >Full duplex e1000e 0000:02:00.0: (unregistered net_device): Auto- > Neg > >> >Advertising de1 e1000e 0000:02:00.0: (unregistered net_device): > >> >Restarting Auto-Neg e1000e 0000:02:00.0: (unregistered net_device): > >> >Unable to establish link!!! > >> >e1000e 0000:02:00.0: (unregistered net_device): Initializing the > >> >Flow Control address, type and timer regs e1000e 0000:02:00.0: > eth1: > >> >(PCI Express:2.5GT/s:Width x1) 4c:02:89:08:ca:03 e1000e > 0000:02:00.0: eth1: > >> >Intel(R) PRO/1000 Network Connection e1000e 0000:02:00.0: eth1: NVM > >> PBA > >> >number is not stored as string e1000e 0000:02:00.0: eth1: MAC: 4, > PHY: > >> >8, PBA No: FFFFFF-0FF e1000e 0000:03:00.0: Disabling ASPM L0s L1 > >> e1000e > >> >0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 e1000e > >> >0000:03:00.0: setting latency timer to 64 e1000e 0000:03:00.0: > >> >Interrupt Throttling Rate (ints/sec) set to dynamic conservative > >> >mode e1000e > >> >0000:03:00.0: (unregistered net_device): Driver can't access the > PHY > >> >e1000e 0000:03:00.0: (unregistered net_device): Error getting PHY > ID > >> >e1000e 0000:03:00.0: PCI INT A disabled > >> >e1000e: probe of 0000:03:00.0 failed with error -2 e1000e > >> 0000:04:00.0: > >> >Disabling ASPM L0s L1 e1000e 0000:04:00.0: PCI INT A -> GSI 19 > >> >(level, > >> >low) -> IRQ 19 e1000e 0000:04:00.0: setting latency timer to 64 > >> >e1000e > >> >0000:04:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic > >> >conservative mode e1000e 0000:04:00.0: (unregistered net_device): > >> >Driver can't access the PHY e1000e 0000:04:00.0: (unregistered > >> >net_device): Error getting PHY ID e1000e 0000:04:00.0: PCI INT A > >> >disabled > >> >e1000e: probe of 0000:04:00.0 failed with error -2 > >> > > >> > "Driver can't access the PHY" and "Error getting PHY ID". At > this > >> >point it is virtually impossible to recover the unit and we have to > >> recall it. > >> >What can I do to address this? > >> > > >> >Thanks! > >> > > >> >-- > >> >Kristian Kielhofner > >> > > >> > >> > >> -------------------------------------------------------------------- > - > >> -- > >> ------- > >> Everyone hates slow websites. So do we. > >> Make your web apps faster with AppDynamics Download AppDynamics Lite > >> for free today: > >> http://ad.doubleclick.net/clk;258768047;13503038;j? > >> http://info.appdynamics.com/FreeJavaPerformanceDownload.html > >> _______________________________________________ > >> 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 > > > > -- > Kristian Kielhofner ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ 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
