FDDI/9000 EISA Adapter Release Notes

18 Chapter1
FDDI/9000 EISA Adapter Release Notes
Patches and Fixes in Version B.10.20.11
3. High checksum errors and degraded
network performance, observed over
EISA FDDI interface, on B and d class
systems which are non-cache coherent
I/O (that is, CCIO).
3. On systems without CCIO support,
the driver needs to maintain cache
coherency during DMA transactions,
by flushing/purging the CPU cache as
necessary. The EISA FDDI driver did
not synchronize its inbound data buffer
pool with the processor cache. Hence,
stale data was passed up to the upper
layers, resulting in checksum errors
and re-transmissions, leading to
degraded performance. To verify this
problem, run netstat(1M) to
display bad checksum. In addition, t
check if the system supports CCIO,
run the following command on the
system:
/usr/bin/grep “^ccio”
/stand/system
4. When OSI stack is configured on
top of EISA FDDI interface it fails to
communicate with its peers, resulting
in application aborts.
4. The control field in the packet
header of outbound Unnumbered
Information (UI) packets in the EISA
FDDI driver was not initialized. As a
result, communication was not
established with remote hosts, causing
application aborts.
5. System panics during system
shutdown when OSI stack is
configured over EISA FDDI driver.
5. During system shutdown, the OSI
stack sends the OSIUNBIND request
to the driver. The driver failed to
unbind the protocol stack stream as it
incorrectly compared the service
access pooling (SAP) values and
returned and error. However, the OSI
stack was unbound and any attempt by
the driver to send packets on that
stream resulted in a system panic.
Table 1-3 PHNE_17061 (Continued)
Symptom Defect