MT25408 ConnectX Firmware fw-25408

Transcription

1 Release Notes MT25408 ConnectX Firmware fw Supportg: InfiBand, Ethernet, FCoE, VPI

2 2 Copyright 2009., Inc. All Rights Reserved. MT25408 ConnectX Firmware fw Release Notes, Inc. 350 Oakmead Parkway, Suite 100 Sunnyvale, CA U.S.A. Tel: (408) Fax: (408) Ltd PO Box 586 Hermon Buildg Yokneam Israel Tel: Fax:

3 MT25408 ConnectX Firmware fw Release Notes 3 1 Overview These are the release notes for the ConnectX and ConnectX EN adapters firmware, fw This firmware supports the followg protocols: InfiBand Ethernet Fibre Channel over Ethernet (FCoE) Virtual Protocol Interconnect (VPI) this capability enables ConnectX devices to support the InfiBand, Ethernet and DCE network standards, cludg auto-sensg of the network protocol to which each device port is connected. This firmware supports the devices and protocols listed Table 1. For the most updated list of adapter cards supported, visit the firmware download pages via Note: After burng new firmware to an adapter card, reboot the mache so that the new firmware can take effect. If you do not reboot, you will get an error the RUN_FW command. Table 1 - PCI Device ID PCI Device ID (Decimal) Device Part Number Device Name Supported Protocols MT25408A0-FCC-SI ConnectX, Dual Port 10Gb/s InfiBand / 10GigE Adapter IC with PCIe 2.0 x8 2.5GT/s Interface InfiBand, Ethernet, FCoE, VPI MT25408A0-FCC-DI ConnectX, Dual Port 20Gb/s InfiBand / 10GigE Adapter IC with PCIe 2.0 x8 2.5GT/s Interface MT25408A0-FCC-GI ConnectX, Dual Port 20Gb/s InfiBand / 10GigE Adapter IC with PCIe 2.0 x8 5.0GT/s Interface MT25408A0-FCC-QI ConnectX, Dual Port 40Gb/s InfiBand / 10GigE Adapter IC with PCIe 2.0 x8 5.0GT/s Interface MT25448A0-FCC-SE ConnectX EN, Dual Port 10GigE Adapter IC with PCIe 2.0 x8 2.5GT/s Interface Ethernet MT26448A0-FCC-TE ConnectX EN, Dual Port 10GigE Adapter IC with PCIe 2.0 x8 2.5GT/s Interface MT25458A0-FCC-SE ConnectX EN, Dual Port 10BASE-T Adapter IC with PCIe 2.0 x8 2.5GT/s Interface MT25458A0-FCC-TE ConnectX EN, Dual Port 10BASE-T Adapter IC with PCIe 2.0 x8 5.0GT/s Interface The document consists of the followg sections: Revision Compatibility (page 4) Changes & Major New Features (page 4) Bug Fixes (page 4) Known s (page 6) Creatg a Device Configuration (.i) File (page 7) History of Fixed s (page 8)

4 4 Revision Compatibility 2 Revision Compatibility Firmware fw complies with the followg programmer s reference manual: - ConnectX Programmer's Reference Manual (PRM), Rev 0.39 or later, which has Command Interface Revision 0x3. The command terface revision can be retrieved by means of the QUERY_FW command and is dicated by the field cmd_terface_rev. 3 Changes & Major New Features 3.1 Changes From Rev Support for extended port counters QUERY_DEV_CAP.local_ack_timeout is now taken from the.i file Support for Ethernet loopback Support for ModStatCfg opcode modifiers 2,3 (query) Support for ModStatCfg.mac Bug fixes 3.2 Changes of Rev From Rev Added the field QUERY_PORT.port_type Bug fixes 4 Bug Fixes The followg table describes known issues from previous releases of ConnectX firmware which were fixed this firmware release. Table 2 - Bug Fixes (Sheet 1 of 2) Fixed 1. InfiBand auto-negotiation issues Fixed MOD_STAT_CFG.port_en command does not apply to Ethernet 3. Mellanox auto-negotiation is not optimized for environments with significant crosstalk 4. CQ/EQ doorbell is lost Configuration cycles 5. Congestion issues 6. SW2HW_MPT command may fail when MPT is FREE state (used for FRWR) 7. Adapter may get stuck upon multicast traffic stress

5 MT25408 ConnectX Firmware fw Release Notes 5 Table 2 - Bug Fixes (Sheet 2 of 2) Fixed 8. IB Spec Release 1.2 lk data-rate issues 9. Adapter may get stuck if QPC extended auxiliary table base address is not aligned to 1MB 10. Port mod_stat_cfg.disable does not take effect if the device is configured as an Ethernet device Fixed HCA might hang when enterg PCIe L1 mode Fixed

6 6 Known s 5 Known s The followg table describes known issues this firmware release and possible workarounds. Table 3 - Known s Index Current Implemented Workaround FW Possible Workaround Scheduled Release (fix) 1. UAR Bar is too small for 64k-page maches The small BAR causes driver loadg to fail N/A Change the "log2_uar_bar_megabytes".i parameter under the [HCA] section as follows: log2_uar_bar_megabytes = 5 N/A 2. Change of memory bars on a disabled system 3. BAR resizg on an enabled system 4. Ethernet only: Must query all capabilities upon boot Changg memory bars size / addresses between SYS_DIS and SYS_EN may cause the device to hang (ID: 24206) Changg bar sizes when a system is enabled may cause the device to hang (ID: 24208) If not all capabilities are queried upon boot, then the query command may fail. See the QUERY_CAP command ConnectX EN Programmer's Reference Manual N/A N/A N/A N/A N/A N/A N/A Query all capabilities upon boot N/A 5. Disruptg QDR negotiation may lead to port risg as SDR Disconnectg an IB cable (or closg the port) durg QDR negotiation and then reconnectg (or reopeng) may cause the adapter to brg up the port at SDR N/A Disconnect the cable (or close the port) aga and then reconnect (reopen). To avoid this scenario, wait for QDR negotiation to fish prior to disconnectg the cable (or closg the port) and reconnectg (or reopeng). The followg are two possible methods to verify QDR negotiation is complete: N/A a. The physical (green) LED is on. b. A query of LkPhyState usg a GetPortInfo MAD dicates LkUp. 6. Ethernet lk issues with back-to-back settg on 5m Twax cables 7. InfiBand Static rate is not supported 8. Autosensg after cable reconnection to different port protocol If you disconnect a cable from an IB/Eth port and reconnect it to an Eth/IB port (different protocol), the lk may not rise N/A Restart the driver (openibd restart) N/A

7 MT25408 ConnectX Firmware fw Release Notes 7 6 Creatg a Device Configuration (.i) File Mellanox firmware burng tools enable settg and/or changg configuration variables by the use of an optional configuration (.i) file. This is needed case the default values of some variables do not suit a user s specific system requirements. This section describes how to create this configuration file. To beg with, the.i file is a text file is composed of one or several configuration sections (see Section 6.1 for the format and/or an example). It is recommended to clude, under the appropriate sections, only those variables that need to be changed. A firmware release cludes a reference file called fw defaults.ref. This file contas the list of all variables which can be configured by a configuration (.i) file. For each variable the reference file cludes a short explanation, the [<section>] it should be under, the range of possible values, and a le with the default settg of the variable which is assumed by the firmware release. To create the.i file, simply copy the les with the variables you wish to set, paste them under their appropriate [<section>] headgs, and change the settg values as desired. 6.1 Configuration (.i) File Format The.i file is composed of one or more sections with variable settgs. Each section the file starts with its name between square brackets, e.g. [ADAPTER], [HCA], [IB], etc. The section name is followed by one or more les of configuration settgs and comments, as the.i file example shown below. Note that comment les start with a semicolon. Excerpt from fw defaults.ref: ;;;;; VPD support can be Disabled/Enabled ;;;;; Under [ADAPTER] section ;;;;; Boolean parameter. Possible values: true, false. vpd_enable = true Example of a.i file: ;Beg of.i file [ADAPTER] vpd_enable = false ;This is a comment le ;End of.i file

8 8 History of Fixed s 7 History of Fixed s Table 4 - History of Bug Fixes (Sheet 1 of 5) Fixed 1. MOD_STAT_CFG.port_en command does not apply to Ethernet 2. Mellanox auto-negotiation is not optimized for environments with significant crosstalk 3. CQ/EQ doorbell is lost Configuration cycles 4. Congestion issues 5. SW2HW_MPT command may fail when MPT is FREE state (used for FRWR) 6. Adapter may get stuck upon multicast traffic stress 7. IB Spec Release 1.2 lk data-rate issues 8. Adapter may get stuck if QPC extended auxiliary table base address is not aligned to 1MB 9. Port mod_stat_cfg.disable does not take effect if the device is configured as an Ethernet device Fixed HCA might hang when enterg PCIe L1 mode 11. Lk may come up as SDR stead of DDR on some systems 12. Possible live lock QP upon retransmission stress 13. Wrong lk state reported durg lk speed negotiation 14. CQs may be generated after CQ overrun error 15. Slow handlg of configuration cycles 16. Wrong fields CQE-w-Error on XRC QP 17. Wrong handlg of Remote Invalidate Error 18. Multiple RNR Nack may cause slowdown Fixed Fixed (ID: 49870, 52066) Fixed (ID: 49951) Fixed (ID: 49982) Fixed (ID: 49807) Fixed (ID: 49742) Fixed (ID: 49559)

9 MT25408 ConnectX Firmware fw Release Notes 9 Table 4 - History of Bug Fixes (Sheet 2 of 5) Fixed 19. QUERY_DEV_CAP.apm bit was fixed at 0 even though APM was active 20. PCIe physical errors upon enterg L1 state 21. PCI_CFG.terrupt_disable has no impact 22. Non-default settg of VLCap via.i does not take effect 23. SET_PORT may lead to non-optimal RX buffer reallocation if opvl was less than vlcap Fixed (ID: 49548) Fixed (ID: 52025) Fixed (ID: 53350) Modified PLL parameter settgs.i Some PLL parameter settgs were changed to allow a longer period for PLL stabilization Adapter may generate PCIe transactions with wrong function ID 26. Adapter may generate PCIe ERR_NON_FATAL case of an unsupported request 27. Ethernet only: Different VLAN priorities for WQE and QP may cause wrong SchedQ allocation 28. Wrong VLAN Priority PPP mode The ConnectX device may send pause frames for the wrong priority PPP mode (ID: 49533) Wrong aliasg address steerg mode This issues applies only to the VMware Infrastructure 3 v3.5 operatg system netq mode Possible packet droppg though the pause policy is set 31. Wrong PCI Class Code for Ethernet Network Controller 32. Brgg up/down of an adapter port may lead to PHY errors on the second adapter port 33. PPP does not work for an MTU of 9600 Fixed This issue applies to Ethernet devices only. Fixed Applies only to dual-port adapter cards. Fixed (ID: 51356) Fixed PCI Express compliancy issues Fixed L1 and L0s power states compliancy issues Fixed PCIE-CV test completion_timeout failure Fixed teroperability issue with all available PCIe Gen. 2.0 servers (Ref. ID: 43852) 35. INTA may be lost under stress Fixed. (Ref. ID: 44473) 36. Modifyg SRQ number usg RTS2RTS Modifyg SRQ number usg RTS2RTS does not guarantee that no new CQEs will be generated usg the old SRQ number. Fixed.

10 10 History of Fixed s Table 4 - History of Bug Fixes (Sheet 3 of 5) Fixed 37. QP may get stuck upon Responder Gather Error Fixed. 38. Wrong handlg of SL mismatch between WQE and MLX QP An SL mismatch between WQE and MLX QP may cause the QP to get stuck. Fixed. 39. UC QP CQE with Error causes corruption 40. Query_CQ/Query_EQ commands may return the old consumer_dex Fixed. Fixed. 41. CQ error may cause corruption A CQ error such as an overrun may cause CQ corruption, leadg to a wrong CQ number the CQ error event or to an ternal FW error. Fixed. 42. Possible FW ternal error on a very noisy lk Fixed. (Ref. ID:41526) 43. QueryDebugMSG command returns wrong status Fixed. (Ref. ID: 44744) 44. Droppg a ReadResponse packet may lead to retry exceeded Fixed. 45. CQ moderation parameters are wrongly configured Fixed. (Ref. ID: 45570) 46. False generation of CQE with error (vendor code 0x6f) upon large stress Fixed. (Ref. ID: 45317) 47. Bandwidth degradation if SetPort command is not called Fixed. 48. SQERR2RTS command followed by an error causes QP to be unfunctional Fixed. (Ref. ID: ) 49. QUERY_FW fails after RUN_FW The command QUERY_FW fails after runng the RUN_FW command 50. HCA stall The HCA might stall any of the followg scenarios: If runng the command SET_DEBUG_MESSAGE (ID:42128) Under large stress (ID: 43385, 43378) Upon closg a large number of QPs (ID: 43697) If the WQE SL is different than the QP Context SL a UD QP (ID: 41423) Upon multiple retransmissions 51. QUERY_QP errors Wrong QUERY_QP command the followg cases: Returns wrong values (ID: 42078, 40707) Enters the error state erroneously (ID: 43110) 52. IB & PCI Express lks quality General improvements 53. Incomplete support for PCI Express 2.0 configuration header Fixed 54. Wrong trap generation rate The HCA might exceed the maximum trap generation rate upon processg different trap types

11 MT25408 ConnectX Firmware fw Release Notes 11 Table 4 - History of Bug Fixes (Sheet 4 of 5) Fixed 55. Client Reregister event not generated The HCA might fail to generate a Client Reregister event under large stress. (ID: 42232) 56. Possible ICM corruption Possible ICM (Interconnect Context Memory) corruption upon large stress (ID: 42529) 57. Performance HCA performance improvements for the followg cases: Upon receivg multiple ACK packets Upon multiple QPs error state (ID:43377) Upon multiple RNR NACKs 58. Wrong wqe_dex Receive CQE with Error This can occur when runng stress IPoIB CM tests. (ID: 43076) 59. Possible multicast corruption Fixed (ID: 43301) 60. Wrong limit on number of supported EQ UARs The HCA now supports the requested number of EQ UARs specified INIT_HCA 61. SchedQueue corruption Fixed (ID: 43289) 62. Wrong SL2VL mappg upon set_sl2vl Fixed 63. False MAD packet drops The HCA might drop MAD packet erroneously under large stress 64. PCI Express 2.0 x1 lk fails to rise Fixed 65. Command timeouts The HCA times out commands while closg multiple QPs 66. False ternal error generation Fixed 67. Transport timeouts Multiple RNR NACKs may lead to transport timeouts (ID: 44160) 68. Opcode/Input Modifier verification Command Opcode/Input Modifier values are now checked for correctness. If a wrong value is provided, the command status dicates the error. 69. Wrong sl and/or port number returned The QUERY_QP command may return a wrong sl value and/or a wrong port number (ID: 40707) HCA stall The HCA might stall upon stress volvg RNR Nacks and RDMA reads (ID: 41918) QP corruption QP corruption may occur followg a CQ_overrun Sched Queue corruption Sched Queue corruption may occur upon multiple re-transmissions False SRQ WQE limit event A false SRQ WQE limit event is generated due to a race condition Wrong Dt value returned The QUERY_FW command may return a wrong Dt value HCA hangs The device hangs one of the followg cases: upon retry due to local_ack_timeout upon retry due to RNR Nack upon rgg a CQ doorbell for an valid QP upon stress conditions (IDs: 41543,732/6,755,778)

12 12 History of Fixed s Table 4 - History of Bug Fixes (Sheet 5 of 5) Fixed 76. High ACK latency Delays ACK may cause multiple local ACK timeouts HCA performance HCA performance may be impacted the followg conditions: QPs error state Slow QP context handlg IB lk stability issues High QP closg duration Closg QPs with outstandg posted WQs may take a long time due to slow CQE with error generation