Fixes in this Version

The MESA Information log displayed “N/A” for the Engineering Date Code, and an empty string for the Board Revision. This was because gelan was erroring out these requests.Resolution:The gelan driver has been modified to return correct values for these requests.

Could not set Jumbo MTU when link was DOWN. This was because a driver check explicitly disallowed this.Resolution:The driver allows MTU changes to all values between 1024-9000, regardless of the link status.

The maximum supported MTU value was retrieved with an IOCTL that was not supported by the gelan driver.Resolution:The driver now implements this IOCTL.

The gelan driver's ISR (Interrupt Service Routine) did not provide any information on the entry/exit timestamps.Resolution:The driver has 2 new members in its data structure to record the entry and exit timestamps of its ISR.

The driver did not support RFC 2863 compliant 64-bit statistics requests.Resolution:The gelan driver now supports 64-bit statistics requests.

The gelan shared library for nettl was not passing the right number of parameters while invoking formatter's subsystem function in “nice” mode. Hence formatter dumped core when used with “nice” option.Resolution:The gelan shared library for nettl is modified to pass in all the arguments to the formatter subsystem.

When netfmt(1m) was used with the “nice” option, the gelan driver's formatter library also performed a “raw” format. This caused each traced packet from the gelan driver to be displayed in both “nice” and “raw” formats.Resolution:The gelan driver's formatter library performs only the “nice” format when netfmt(1m) is invoked with the “nice” option.

WBEM clients could not retrieve the properties port type, flow control status, and maximum speed on gelan interfaces.Resolution:The gelan driver now processes the requests and returns the appropriate values.

On systems subjected to high stress, gelan interfaces were found to transition to GELAN_ERROR state, as reported by the “-x card_info” option of the lanadmin(1m) command. This brought the link to DOWN state for the interface, and a reset of the card was required to recover. This happened because the gelan driver's interrupt service routine was not invoked for a long time due to the high stress on the system. So, a watchdog timer put the interface into GELAN_ERROR state.Resolution:The watchdog timer has been modified to not rely on the interrupt service routine for monitoring the health of the gelan interface.

In one observed instance, the content of the receive control structure DMAd to the host memory by the card was incorrect. That control structure contains an index used by the driver to process inbound packets. Incorrect index could lead driver to access wrong host memory location and result in system panic.Resolution:A check is added in the driver to verify that the index is within the expected limit. If the index is invalid, the driver will take the interface offline.