FDDI/9000 EISA Adapter Release Notes

Chapter 1 27
FDDI/9000 EISA Adapter Release Notes
Patches and Fixes in Version B.11.00.07
3. HPMCs could occur during the
execution of the code that autorecovers
the interface after transmit time.
3. The transmit hang autorecovery
code uses the kernel sleep/wakeup
synchronization mechanism t await the
completion of events. As autorecovery
could be initiated with no process
context, the above scheme does not
work. The fix incorporates an interrupt
driven state transition mechanism t
complete the recovery.
Table 1-8 PHNE_18665
Symptom Defect
1. When the MTU of the EISA FDDI
interface is set or reset using the
lanadmin(1M) command with -M or
-R options respectively, the command
completes without any errors but does
not set/reset the MTU value for the
interfaces.
1. A missing cache purge at the time
the receive buffer is set up causes stale
data to appear in the received packed.
The stale data starts at cache line
boundaries and can run to multiples of
the cache line size.
2 When lanadmin(1M) is used to set
the physical address of the interface to
the broadcast address (0xfffffffffffff) or
to 0 (0x000000000000), the command
succeeds.
2. When the lanadmin(1M) command
is used with the -A option to set the
physical address of the interface to
either 0x000000000000 or
0xffffffffffff, the driver did not check
for these addresses and set the physical
address correctly. This is inconsistent
with the behavior of other networking
cards/drivers that prevent the physical
address from being set to the above
values. The driver has been fixed to
return an error (EINVAL) for the
above values.
Table 1-7 PHNE_13395 (Continued)
Symptom Defect