PCI Mux Release Notes

Release Note for HP-UX 11.0x
Known Problems and Workarounds
Chapter 2 11
Known Problems and Workarounds
The known problems and corresponding workarounds for the current version of the PCI Mux
products are as follows:
• Disconnecting or connecting port modules while the system is active might generate a
break character on the serial ports of any port module still connected. The gettys active
on those ports might treat the break as an auto-speed detection loop and change the baud
rate, causing the ports to appear “hung”.
Workaround: Pressing the Break key a few times will bring the getty back to the
original baud rate.
• The emux_diag program relies on HP terminal function keys. If you change the terminal
function key definitions from the default values, emux_diag will not work.
Workaround: If you have changed the HP terminal function key definitions from their
default values (press cntl-menu to see the menu on HP terminals), you need to change
them back to the default values (that is, f1=<ESC>p, f2=<ESC>q,... f8=<ESC>v) before
running the emux_diag program.
• When adding a new port module to an already configured system, insf does not
automatically create device files for new ports at boot time.
Workaround: Each time you add a new port module to an installed PCI Mux card, you
must enter the command below to create device files for each newly added port:
insf -e -d pci_mux0
• Xterm does not support HP function keys. Because emux_diag relies on HP terminal
function keys, emux_diag will not work with Xterm.
Workaround: Configure your console to use dtterm or hpterm.
• When you run swverify after installing the Mux driver on a C-class or J-class
workstation running HP-UX 11.0/ 64- bit, swverify logs the following error in
swverify.log:
ERROR: “<system_name>:/”: This task is operating on an existing multiple
version of 2 products or filesets.
This problem happens because the PCI-MUX.PCI-MUX-RUN fileset is installed twice.
You should ignore the error message.