HP FDDI 9000 FDDI/9000 EISA Adapter Release Notes - Page 19

Table 1-4, PHNE_15665, Table 1-3, PHNE_17061, Continued

Page 19 highlights

Table 1-3 Table 1-4 FDDI/9000 EISA Adapter Release Notes Patches and Fixes in Version B.10.20.11 PHNE_17061 (Continued) Symptom Defect 6. System crashes, with either an HPMC or a memory protection fault panic, under high network traffic over the EISA FDDI interface. 7. System panics with an instruction page fault when multiple promiscuous streams are enabled over the EISA FDDI interface. 8. The netfnt(1M) output for traces generated by the EISA FDDI driver is incorrect. 6. Under heavy network traffic conditions, the EISA FDDI driver may sometimes invoke internal card resets to recover from transmit hangs. In the driver's watchdog timer, when attempting an internal reset (for automatic recovery), the driver invokes a kernel sleep routine while waiting for reset completion. Since the watchdog timer executes in an interrupt system context, calling sleep leads to a system crash (HPMC or memory protection fault). An alternate mechanism of completing resets in driver interrupt routines has been implemented. 7. When multiple streams enable promiscuous mode on a single interface, the driver failed t distinguish between bound and unbound streams. As a result, the streams queue pointer was corrupted, resulting in a panic. 8. The EISA FDDI formatting routines were using incorrect offsets into the trace buffers, resulting in incorrect output. PHNE_15665 Symptom Defect 1. The EISA FDDI interface may hang after logging the message, "Waited for stat2_ine4 but it never came" to syslog. 1.A software reset mechanism was introduced in the EISA FDDI driver to work around hardware defects in the Motorola FDDI system Interface (FSI) chip. This mechanism did not detect all the circumstances under which the card had to be reset. Chapter 1 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29

Chapter 1
19
FDDI/9000 EISA Adapter Release Notes
Patches and Fixes in Version B.10.20.11
6. System crashes, with either an
HPMC or a memory protection fault
panic, under high network traffic over
the EISA FDDI interface.
6. Under heavy network traffic
conditions, the EISA FDDI driver may
sometimes invoke internal card resets
to recover from transmit hangs. In the
driver’s watchdog timer, when
attempting an internal reset (for
automatic recovery), the driver invokes
a kernel sleep routine while waiting for
reset completion. Since the watchdog
timer executes in an interrupt system
context, calling sleep leads to a system
crash (HPMC or memory protection
fault). An alternate mechanism of
completing resets in driver interrupt
routines has been implemented.
7. System panics with an instruction
page fault when multiple promiscuous
streams are enabled over the EISA
FDDI interface.
7. When multiple streams enable
promiscuous mode on a single
interface, the driver failed t distinguish
between bound and unbound streams.
As a result, the streams queue pointer
was corrupted, resulting in a panic.
8. The
netfnt(1M)
output for traces
generated by the EISA FDDI driver is
incorrect.
8. The EISA FDDI formatting routines
were using incorrect offsets into the
trace buffers, resulting in incorrect
output.
Table 1-4
PHNE_15665
Symptom
Defect
1. The EISA FDDI interface may hang
after logging the message, “Waited for
stat2_ine4 but it never came” to syslog.
1.A software reset mechanism was
introduced in the EISA FDDI driver to
work around hardware defects in the
Motorola FDDI system Interface (FSI)
chip. This mechanism did not detect all
the circumstances under which the
card had to be reset.
Table 1-3
PHNE_17061
(Continued)
Symptom
Defect