10GigEthr-02 (iexgbe) B.11.31.1303 Ethernet Driver Release Notes (Edition 2)
4 Known problems and limitations
The following problems and limitations are known to exist in version B.11.31.1303:
• QXCR1001270195 — iexgbe 1303 versions introduced issues due to missing firmware lock
The following symptoms might be seen because of this defect:
◦ iexgbe driver continuously sends UP/DOWN notification events to the WBEM provider.
(QXCR1001268673) The WBEM events seen by the user are of these types:
DL_HP_EXT_LINK_DOWN_IND and DL_HP_EXT_LINK_UP_IND.
◦ (QXCR1001267062) The nettl log becomes filled with link EPHY8073 link up
notification messages.
The following is an example of the messages seen:
<4006> 10GBase-SR in path 0/0/0/3/0/0/5
Link Event.
EPHY8073 link up or
<4006> 10GBase-SR in path 0/0/0/3/0/0/5
Link Event.
EPHY8726 link up
◦ (QXCR1001268375) Speed mismatch error frequently recorded in syslog.
The driver can present the following message in syslog during DLKM load/unload,
boot, or other control path operations:
internal_link_settings_status: 10G speed mismatch 0x300
◦ (QXCR1001268375) Ports for which the adapter reports the incorrect speed might
occasionally cause APA formation to fail during startup.
◦ iexgbe m45write and m45read message logged on the console.
(QXCR1001267051) During DLKM load/unload, the following message might be seen
on the console:
...m45write: Setting PHY address to write failed, phyreg 0xffe4, devad 0x7, val 0x1e0
...m45read: Setting PHY address to read failed 0x2227ffe4 0x1
(QXCR1001265402) During installation or deinstallation of the 10GigEthr-02 bundle,
the following message might be seen:
...m45read: Read of PHY register failed, addr 0x2227ffe4 init_done 1,
status 0x2e270000
• QXCR1001267697 — Problem with nwmgr -s -A all --sa --fr cu -c command
The command does not properly store the parameter settings in the
/etc/rc.config.d/hpiexgbeconf configuration file.
• QXCR1001247823 — iexgbe driver intermittently stops collecting/incrementing link statistics
The iexgbe driver intermittently stops collecting and updating link statistics. This does not
affect data traffic; it only affects statistics. However, this can cause false link failure detection;
systems with MC/Serviceguard might exhibit a system Transfer Of Control (TOC), thereby
inhibiting Serviceguard recovery from a link outage or network connectivity problem.
Severity: Medium
Workaround: Resolve the problem by resetting the link. Statistics will then be collected and
updated properly.
10