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

Table 1-2, PHNE_17285, Table 1-1, PHNE_18869, Continued

Page 15 highlights

Table 1-1 Table 1-2 FDDI/9000 EISA Adapter Release Notes Patches and Fixes in Version B.10.20.11 PHNE_18869 (Continued) Symptom 8. Data page fault panic in fdi0_open. Defect 8. The panic was happening when the EISA FDDI device file was opened, with no EISA FDDI card configured on the system. Under these circumstances, the open routing tries to access a null board structure pointer, resulting in a data page fault panic. PHNE_17285 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 interface. 2. When lanadmin(1M) is used to set the physical address of the interface to the broadcast address (0xffffffffffff) or to 0 (0x0000000000000), the command succeeds. 1. When lanadmin(1M) is run with the -M option to set the MTU for the interface, or with the -R option to reset it to the default value, it sends a 'change MTU' ioctl (I/O Control) request to the driver. The driver did not handle this request nor returned an error. As a result, the lanadmin(1M) command completed without errors, but did not set/reset the MTU. 2. When the lanadmin(1M) command is used with the -A option to set the physical address of the interface to either 0xffffffffffff or 0x000000000000, the driver did not check for these addresses and set the physical address as such. This is inconsistent with the behavior of other networking cards/drivers. This behavior prevented the physical address from being set to either of the above values. Chapter 1 15

  • 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
15
FDDI/9000 EISA Adapter Release Notes
Patches and Fixes in Version B.10.20.11
8. Data page fault panic in fdi0_open.
8. The panic was happening when the
EISA FDDI device file was opened,
with no EISA FDDI card configured
on the system. Under these
circumstances, the open routing tries to
access a null board structure pointer,
resulting in a data page fault panic.
Table 1-2
PHNE_17285
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
interface.
1. When lanadmin(1M) is run with the
-M option to set the MTU for the
interface, or with the -R option to reset
it to the default value, it sends a
‘change MTU’ ioctl (I/O Control)
request to the driver. The driver did not
handle this request nor returned an
error. As a result, the lanadmin(1M)
command completed without errors,
but did not set/reset the MTU.
2. When lanadmin(1M) is used to set
the physical address of the interface to
the broadcast address (0xffffffffffff) or
to 0 (0x0000000000000), 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 0xffffffffffff or
0x000000000000, the driver did not
check for these addresses and set the
physical address as such. This is
inconsistent with the behavior of other
networking cards/drivers. This
behavior prevented the physical
address from being set to either of the
above values.
Table 1-1
PHNE_18869
(Continued)
Symptom
Defect