FDDI/9000 EISA Adapter Release Notes

16 Chapter1
FDDI/9000 EISA Adapter Release Notes
Patches and Fixes in Version B.10.20.11
3. netstat(1M) used with the -i option
shows a large number of inbound
errors on the EISA FDDI interface.
3. Packets which were being dropped,
either due to the interface being
configured down (using the
ifconfig(1M) command), or due to the
driver not being able to decipher the
protocol type of the packet, were
counted as inbound errors for IP.
4. When the EISA FDDI interface is
configured down using the
ifconfig(1M) command, an unbound
SAP promiscuous stream opened on
the interface failed to receive IP/ARP
packets coming in on the interface.
4. When an unbound stream in SAP
promiscuous mode is operating over
the EISA FDDI interface and the
interface is configured down using the
ifconfig(1M) command, the driver
stops sending IP/ARP packets to the
promiscuous stream. The expected
behavior is to continue sending these
packets to the promiscuous stream.
5. The system may panic with a ‘Data
page fault’ when the EISA FDDI
interface is operating in promiscuous
mode with heavy inbound traffic.
5. Under heavy network traffic, with
the EISA FDDI interface in
promiscuous mode, when a call to
allocate memory failed, an inbound
buffer could be freed more than once,
resulting in a system panic.
6. The system panics with a ‘Data page
fault’ when promiscuous mode is
repeatedly turned on and off over the
EISA FDDI interface.
6. When promiscuous mode is turned
on/off repeatedly, there was a time
window during which the stream,
which had previously turned
promiscuous mode off, was closed
before the card’s promiscuous mode
was turned off by the driver. The time
window was introduced because of the
order in which the driver carried out
the steps to disable promiscuous mode
on the interface. Due to this time
window, some packets were still sent
to a non-existent stream, leading to a
system panic.
Table 1-2 PHNE_17285
Symptom Defect