Hi john I mean the machine firmware: IPMI, power management
Thanks jon -----Original Message----- From: Ronciak, John [mailto:[email protected]] Sent: Thursday, November 25, 2010 10:58 AM To: Jon Zhou; Skidmore, Donald C; '[email protected]' Subject: RE: [E1000-devel] failed to load because an unsupported SFP+ module type was detected. What firmware are you referring to? I can only speak to the NIC device and not system related items. The NIC driver is not part of any firmware but is in the Linux OS. Since you are using a NIC any BIOS update will not update anything on the NIC. If the Ethernet device was on the motherboard then the BIOS could update the EEPROM but that is not the case here. Cheers, John > -----Original Message----- > From: Jon Zhou [mailto:[email protected]] > Sent: Wednesday, November 24, 2010 6:45 PM > To: Ronciak, John; Skidmore, Donald C; '[email protected]' > Subject: RE: [E1000-devel] failed to load because an unsupported SFP+ > module type was detected. > > Hi john > > I didn't move it back to harpertown yet, > > Btw, do you think I need to update the firmware and driver also? (how > can I know my current IPMI and firmware version?) > > http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang > =en&cc=us&prodNameId=3884083&prodTypeId=15351&prodSeriesId=3884082&swLa > ng=13&taskId=135&swEnvOID=4048#12212 > > Driver - System Management Description Current version Size (MB) > Estimated download time Previous version HP OpenIPMI Device Driver for > SUSE LINUX Enterprise Server 11 (x86) 8.5.0-1.sles11 > 28 May 2010 0.8 56K: 1m > 512K: <1m 8.5.0-1.sles11 > 28 May 2010 > > > Firmware Description Current version Size (MB) Estimated download time > Previous version Online ROM Flash for Linux - Power Management > Controller (ML/DL G6 Servers) 2.9 (D) > 24 Jul 2009 2.9 (C) > 18 Jun 2009 > Obtain software > > > Thanks > jon > > -----Original Message----- > From: Ronciak, John [mailto:[email protected]] > Sent: Thursday, November 25, 2010 10:33 AM > To: Jon Zhou; Skidmore, Donald C; '[email protected]' > Subject: RE: [E1000-devel] failed to load because an unsupported SFP+ > module type was detected. > > Does the NIC still work in the Harpertown (hypertown) system you said > it worked in orginially? I also think you need to update the BIOS to > the latest version. > > Cheers, > John > > > > -----Original Message----- > > From: Jon Zhou [mailto:[email protected]] > > Sent: Wednesday, November 24, 2010 6:25 PM > > To: Skidmore, Donald C; '[email protected]' > > Subject: Re: [E1000-devel] failed to load because an unsupported SFP+ > > module type was detected. > > > > Hi don: > > > > lspci -s 0a:00.1 -n > > 0a:00.1 0200: 8086:10fb (rev 01) > > > > > > After I modified the BIOS setting: > > VT-D : enable->disable > > Power management: Minimum Processor Idle Power State C6 State ->Non C > > State > > (Note: before install the NIC, these actions are not required ) > > > > The OS successfully loaded > > But I still can't get nic work: > > > > dmesg|grep ixgbe > > [ 7.387497] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver > - > > version 2.0.44-k2 > > [ 7.387691] ixgbe: Copyright (c) 1999-2009 Intel Corporation. > > [ 7.387868] ixgbe 0000:0a:00.0: enabling device (0000 -> 0002) > > [ 7.388007] ixgbe 0000:0a:00.0: PCI INT A -> GSI 31 (level, low) - > > > > IRQ 31 > > [ 7.388150] ixgbe 0000:0a:00.0: setting latency timer to 64 > > [ 8.901638] ixgbe 0000:0a:00.0: HW Init failed: -15 > > [ 8.901776] ixgbe 0000:0a:00.0: PCI INT A disabled > > [ 8.901897] ixgbe: probe of 0000:0a:00.0 failed with error -15 > > [ 8.902031] ixgbe 0000:0a:00.1: enabling device (0000 -> 0002) > > [ 8.902163] ixgbe 0000:0a:00.1: PCI INT B -> GSI 39 (level, low) - > > > > IRQ 39 > > [ 8.902302] ixgbe 0000:0a:00.1: setting latency timer to 64 > > [ 10.412968] ixgbe 0000:0a:00.1: HW Init failed: -15 > > [ 10.413125] ixgbe 0000:0a:00.1: PCI INT B disabled > > [ 10.413256] ixgbe: probe of 0000:0a:00.1 failed with error -15 > > > > > > I also checked the BIOS, it is quite new (08/16/2010,newer than BZ), > > the latest one is 10/14/2010 which fix some PXE bugs. > > > > Thanks > > jon > > > > > > -----Original Message----- > > From: Skidmore, Donald C [mailto:[email protected]] > > Sent: Thursday, November 25, 2010 10:11 AM > > To: Jon Zhou; '[email protected]' > > Subject: RE: [E1000-devel] failed to load because an unsupported SFP+ > > module type was detected. > > > > Hi Jon, > > > > I don't believe we have an X520 fiber product that isn't SFP+. But I > > could be wrong. If you get me the device ID I could tell you for > sure. > > From looking at your lspci output below I think you could do it with: > > > > lspci -s 0a:00.1 -n > > > > Thanks, > > -Don > > > > >-----Original Message----- > > >From: Jon Zhou [mailto:[email protected]] > > >Sent: Wednesday, November 24, 2010 5:59 PM > > >To: Skidmore, Donald C; '[email protected]' > > >Subject: RE: [E1000-devel] failed to load because an unsupported > SFP+ > > >module type was detected. > > > > > >Hi Don > > > > > >The nic is X520-SR2, I don't think it has SFP+ module? > > > > > > (I plug SR fiber into the port directly) > > > > > >Regards, > > >Jon > > > > > >-----Original Message----- > > >From: Skidmore, Donald C [mailto:[email protected]] > > >Sent: Wednesday, November 24, 2010 11:29 PM > > >To: Jon Zhou; '[email protected]' > > >Subject: RE: [E1000-devel] failed to load because an unsupported > SFP+ > > >module type was detected. > > > > > > > > >Hi Jon, > > > > > >The original error message you mentioned "failed to load because an > > >unsupported SFP+ module type was detected." is triggered ixgbe not > > >getting the correct identifier back when it queries the NIC's > EEPROM. > > >Normally this means just what the message says, you have a SFP+ > > >module in the NIC that isn't supported. > > > > > >Now in your case I'm not that sure as you also got the NMI error. > > > > > >I have a couple questions. > > > > > >- do you see the NMI error every time you boot? If so could you > send > > >us some of the log like you did with the unsupported SFP+ message? > > > > > >- Have you tried loading without and SFP+ module in the system? Do > > you > > >still see the failure? > > > > > >- Have you tried updating your BIOS like it was mentioned in the BZ? > > > > > >Thanks, > > >-Don Skidmore <[email protected]> > > > > > >>-----Original Message----- > > >>From: Jon Zhou [mailto:[email protected]] > > >>Sent: Wednesday, November 24, 2010 6:27 AM > > >>To: Jon Zhou; '[email protected]' > > >>Subject: Re: [E1000-devel] failed to load because an unsupported > > >>SFP+ module type was detected. > > >> > > >>I found a similar problem > > >>https://bugzilla.redhat.com/show_bug.cgi?id=548198 > > >> > > >>Anybody knows reason? > > >> > > >> > > >>Thanks > > >>jon > > >> > > >>-----Original Message----- > > >>From: Jon Zhou > > >>Sent: Wednesday, November 24, 2010 5:37 PM > > >>To: Jon Zhou; '[email protected]' > > >>Subject: RE: [E1000-devel] failed to load because an unsupported > > >>SFP+ module type was detected. > > >> > > >>When I reboot the machine > > >>It shows ixgbe: EEPROM is invalid followed kernel panic due to NMI. > > >> > > >> > > >> > > >>-----Original Message----- > > >>From: Jon Zhou [mailto:[email protected]] > > >>Sent: Wednesday, November 24, 2010 3:38 PM > > >>To: '[email protected]' > > >>Subject: [E1000-devel] failed to load because an unsupported SFP+ > > >>module type was detected. > > >> > > >>Hi > > >> > > >>The X520 NIC was installed on a hypertown (Intel(R) Xeon(R) CPU > > >>E5440 @ 2.83GHz) and successfully loaded. > > >> > > >>It failed to init when I move it to a HP DL380(Intel(R) Xeon(R) CPU > > >>E5540 @ 2.53GHz) And it report these errors: > > >> > > >>I can't understand what is the meaning of "failed to load because > an > > >>unsupported SFP+ module type was detected." > > >> > > >>Thanks a lot! > > >> > > >> > > >>Oct 18 04:23:17 linaspl50 kernel: [ 2325.038363] Intel(R) 10 > Gigabit > > >>PCI Express Network Driver - version 3.0.12-NAPI Oct 18 04:23:17 > > >>linaspl50 > > >>kernel: [ 2325.038371] Copyright (c) 1999-2010 Intel Corporation. > > >>Oct 18 04:23:17 linaspl50 kernel: [ 2325.038413] ixgbe > 0000:0a:00.0: > > >>PCI INT A -> GSI 31 (level, low) -> IRQ 31 Oct 18 04:23:17 > linaspl50 > > >>kernel: [ 2325.038458] ixgbe 0000:0a:00.0: setting latency timer to > > 64 > > >>Oct 18 04:23:20 linaspl50 kernel: [ 2328.472454] ixgbe: > 0000:0a:00.0: > > >ixgbe_probe: > > >>failed to load because an unsupported SFP+ module type was > detected. > > >>Oct 18 04:23:20 linaspl50 kernel: [ 2328.472457] Reload the driver > > >>after installing a supported module. > > >>Oct 18 04:23:20 linaspl50 kernel: [ 2328.472479] ixgbe > 0000:0a:00.0: > > >>PCI INT A disabled Oct 18 04:23:20 linaspl50 kernel: [ 2328.472499] > > >>ixgbe > > >>0000:0a:00.1: PCI INT B -> GSI 39 (level, low) -> IRQ 39 Oct 18 > > >>04:23:20 linaspl50 kernel: [ 2328.472529] ixgbe 0000:0a:00.1: > > >>setting latency timer to 64 Oct 18 04:23:24 linaspl50 kernel: [ > > >>2331.895676] > > ixgbe: > > >0000:0a:00.1: > > >>ixgbe_probe: failed to load because an unsupported SFP+ module type > > >>was detected. > > >>Oct 18 04:23:24 linaspl50 kernel: [ 2331.895678] Reload the driver > > >>after installing a supported module. > > >>Oct 18 04:23:24 linaspl50 kernel: [ 2331.895692] ixgbe > 0000:0a:00.1: > > >>PCI INT B disabled > > >> > > >>linaspl50:~/ixgbe-3.0.12/src # lspci 00:00.0 Host bridge: Intel > > >>Corporation 5520 I/O Hub to ESI Port (rev > > >>13) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI > > >>Express Root Port 1 (rev 13) 00:02.0 PCI bridge: Intel Corporation > > >>5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 13) 00:03.0 PCI > > >>bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root > > >>Port > > >>3 (rev 13) 00:04.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub > > >>PCI Express Root Port 4 > > >(rev > > >>13) 00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI > > Express > > >Root > > >>Port 5 (rev 13) 00:06.0 PCI bridge: Intel Corporation 5520/X58 I/O > > Hub > > >>PCI Express Root Port 6 (rev 13) 00:07.0 PCI bridge: Intel > > Corporation > > >>5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13) 00:08.0 PCI > > bridge: > > >>Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 > (rev > > >>13) 00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI > > >>Express Root Port 9 (rev 13) 00:0a.0 PCI bridge: Intel Corporation > > >>5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 13) 00:0d.0 > Host > > >>bridge: Intel Corporation Device 343a (rev 13) > > >>00:0d.1 Host bridge: Intel Corporation Device 343b (rev 13) > > >>00:0d.2 Host bridge: Intel Corporation Device 343c (rev 13) > > >>00:0d.3 Host bridge: Intel Corporation Device 343d (rev 13) > > >>00:0d.4 Host bridge: Intel Corporation 5520/5500/X58 Physical Layer > > >>Port 0 (rev 13) > > >>00:0d.5 Host bridge: Intel Corporation 5520/5500 Physical Layer > Port > > 1 > > >(rev > > >>13) > > >>00:0d.6 Host bridge: Intel Corporation Device 341a (rev 13) 00:0e.0 > > >>Host > > >>bridge: Intel Corporation Device 341c (rev 13) > > >>00:0e.1 Host bridge: Intel Corporation Device 341d (rev 13) > > >>00:0e.2 Host bridge: Intel Corporation Device 341e (rev 13) > > >>00:0e.3 Host bridge: Intel Corporation Device 341f (rev 13) > > >>00:0e.4 Host bridge: Intel Corporation Device 3439 (rev 13) 00:14.0 > > PIC: > > >>Intel Corporation 5520/5500/X58 I/O Hub System Management Registers > > >>(rev > > >>13) > > >>00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and > > >>Scratch Pad Registers (rev 13) > > >>00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status > > >>and > > >RAS > > >>Registers (rev 13) 00:1c.0 PCI bridge: Intel Corporation 82801JI > > >>(ICH10 > > >>Family) PCI Express Root Port 1 > > >>00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI > > >>Express Root Port 3 00:1d.0 USB Controller: Intel Corporation > > >>82801JI (ICH10 > > >>Family) USB UHCI Controller #1 > > >>00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) > USB > > >>UHCI Controller #2 > > >>00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) > USB > > >>UHCI Controller #3 > > >>00:1d.3 USB Controller: Intel Corporation 82801JI (ICH10 Family) > USB > > >>UHCI Controller #6 > > >>00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) > > >>USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 > > >>PCI Bridge (rev > > >>90) 00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC > > >>Interface Controller > > >>00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 > > port > > >SATA > > >>IDE Controller #1 01:03.0 VGA compatible controller: ATI > > >>Technologies Inc ES1000 (rev 02) 01:04.0 System peripheral: Compaq > > >>Computer Corporation Integrated Lights Out Controller (rev 03) > > >>01:04.2 System peripheral: Compaq Computer Corporation Integrated > > >>Lights Out Processor (rev 03) > > >>01:04.4 USB Controller: Hewlett-Packard Company Proliant iLO2/iLO3 > > >>virtual USB controller > > >>01:04.6 IPMI SMIC interface: Hewlett-Packard Company Proliant iLO2 > > >>virtual UART 02:00.0 Ethernet controller: Broadcom Corporation > > >>NetXtreme II > > >BCM5709 > > >>Gigabit Ethernet (rev 20) > > >>02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II > > BCM5709 > > >>Gigabit Ethernet (rev 20) 03:00.0 Ethernet controller: Broadcom > > >Corporation > > >>NetXtreme II BCM5709 Gigabit Ethernet (rev 20) > > >>03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II > > BCM5709 > > >>Gigabit Ethernet (rev 20) 04:00.0 RAID bus controller: Hewlett- > > Packard > > >>Company Smart Array G6 controllers (rev 01) 0a:00.0 Ethernet > > controller: > > >>Intel Corporation 82599EB 10-Gigabit Network Connection (rev 01) > > >>0a:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit > > >>Network Connection (rev 01) 14:00.0 RAID bus controller: > > >>Hewlett-Packard Company Smart Array G6 controllers (rev 01) > > >> > > >>jon > > >> > > >>------------------------------------------------------------------- > - > > >>- > > - > > >>---- > > >- > > >>--- > > >>Increase Visibility of Your 3D Game App & Earn a Chance To Win > $500! > > >>Tap into the largest installed PC base & get more eyes on your game > > by > > >>optimizing for Intel(R) Graphics Technology. Get started today with > > >>the > > >>Intel(R) Software Partner Program. Five $500 cash prizes are up for > > grabs. > > >>http://p.sf.net/sfu/intelisp-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 > > > > --------------------------------------------------------------------- > - > > - > > ------- > > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > > Tap into the largest installed PC base & get more eyes on your game > by > > optimizing for Intel(R) Graphics Technology. Get started today with > > the > > Intel(R) Software Partner Program. Five $500 cash prizes are up for > > grabs. > > http://p.sf.net/sfu/intelisp-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 ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-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
