Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
 Contact HP
HP.com home
HP Tru64 UNIX: Technical Updates for the Version 5.1B and Higher Operating System and Patches > Technical Updates for the Version 5.1B and Higher Operating System and Patches

Processor-Specific Updates


Content starts here

S47/ES80/GS1280 Performance Improvements by Turning off Environmental Monitoring Daemon (May 2005)

The AlphaServer ES47/ES80/GS1280 is susceptible to minor performance penalties when the Tru64 UNIX environmental monitoring daemon (envmond) is running, or when an application uses the hwmgr command to query the attributes of a sensor in the hardware manager's device hierarchy. Also, the use of hwmgr or envmond can lead to delays in the timely servicing of interrupts.

This is most likely to be noticeable when running applications that are sensitive to increased interrupt latencies. In these cases, envmond should be looked at closely as a possible source of performance degradation until further notice (it is possible that future versions of envmond will not use hwmgr). Additionally, users with root access should avoid manually querying the hardware sensors using the hwmgr -get attr command.

The envmond daemon runs by default. See the envconfig(8) reference page for instructions on changing this behavior.

Inappropriate Environmental Message Seen on AlphaServer GS1280 (May 2005)

Environmental monitoring on an AlphaServer GS1280 may act incorrectly if an environmental event such as a power supply or fan failure or an over-temperature condition is detected when the system is booting. When this occurs you will see the following message on your console:

   mvcpu_log_error: Cannot find temperature sensor

This message indicates that the system tried to send an EVM event describing the environmental error, but an internal error occurred.

In most configurations, you can ignore this message. The machine check data will have been logged into the binary error log as usual. Proceed with determining the root cause of the environmental event using the binary error log.

If you see this problem at times other than during booting, you can correct it by installing the Version 5.1B-3 patch kit.

Limitation on CPU Offline Process (Feb. 2005)

Each CPU on the AlphaServer ES47/ES80/GS1280 series has the capacity to handle I/O interrupts from either a locally attached I/O adapter or from another CPU that has been offlined. However, each CPU is limited to handling the I/O interrupts of two CPUs total, including its own local I/O. Therefore, on a system with X I/O hoses, the largest number of CPUs that can be offline at any one time is (X/2). Attempts to offline more CPUs will result in the following error message from psradm:

 offline: processor N: Invalid argument

There is currently no command to tell you which CPUs are handling I/O interrupts from which I/O adapters.

This information will be included in the psradm(8) reference page that will be installed with Tru64 UNIX Version 5.1B-3.

Shared SCSI Support on AlphaServer DS15 Systems (Feb. 2005)

Tru64 UNIX supports a shared SCSI bus using the DS15 embedded external SCSI port and the following Tri-link cabling kit:

Part Number Description
3X-H8411-BAShared SCSI Adapter Kit for AlphaServer DS15 (Tri-link)
3X-BN56A-03 3 meter terminator cable
3X-BN56A-04 4 meter terminator cable

This adapter kit and cables replaces the y-cable based solution previously supported on AlphaServer DS15 systems. The following sections describe the configuation requirements for the shared SCSI bus.

Hardware Configuration

When operating on a shared bus, jumper J41 must be installed on the system board. This disables the on-board SCSI terminators for that SCSI bus.

When not operating on a shared bus, J41 must be removed and all SCSI BIOS parameters must be reset to their default values otherwise unpredictable system behavior may result.

See section 4.10.1 of the DS15 Owner's Guide for more information: http://h18002.www1.hp.com/alphaserver/download/ek-ds150-og-a01-web.pdf

The following figure shows the cable configuration for the Tri-link cables.

Figure 1 Tri-link Cable Configuration

Tri-link Cable Configuration

Configuring the Shared SCSI Bus

You can use the information in the Cluster Hardware Configuration Technical Update for the 3X-KZPEA-DB Ultra3 SCSI PCI Host Bus Adapter (http://h30097.www3.hp.com/docs/updates/kzpea/TITLE.HTM) to configure the shared bus. Note that there are minor differences when configuring the Alphaserver DS15:

  • The AlphaServer DS15 only supports a single shared bus using the embedded controller.

  • The SCSI BIOS menus are slightly different from the KZPEA BIOS menus.

  • At the SRM console the shared bus is always called PKB0 . So the user would issue ">>>run bios PKA0" at the console and then select "AIC-7899 B" to configure the BIOS settings as follows:

    • When prompted, enter <CTRL>A to enter the BIOS.

    • Select “AIC-7899 B” to configure the shared port.

    • Select “Configure/View SCSI Controller Settings”.

    • Change the SCSI controller ID to 6 on one system while leaving it set to7 on the other system.

    • Change the “SCSI Controller Termination” to Disabled on both systems.

    • Exit the BIOS and reply “Yes” to save the changes.

Mouse/Keyboard Detection Problem Possible on AlphaServer GS1280, ES80, and ES47 Systems (Aug. 2004)

A rare problem in which the USB keyboard and mouse are not detected by the host at boot time may occur on AlphaServer GS1280, ES80, and ES47 systems.

If this happens, you can correct the problem by unplugging the keyboard and mouse, waiting a few seconds, and reconnecting them. If this fails to correct the problem, connect the devices to a different USB port.

Potential False Temperature Error Condition on AlphaServer DS10, DS10L, and TS10 Systems (Feb. 2004)

A sensor error can potentially indicate a false over-temperature condition on AlphaServer DS10, DS10L, and TS10 systems. While the sensor accurately reports the temperature, it falsely reports the high temperature threshold. This false reporting of the threshold value can cause the Insight Management SMP Agents to forward false traps, and potentially result in the Tru64 UNIX environmental monitoring daemon (envmond(8)) initiating the shutdown process. However, this false reporting condition is temporary and the high temperature threshold soon returns to normal, at which point the shutdown is cancelled.

To work around this problem, use the envconfig utility to manually set the high temperature threshold to its current default value. While this does not change the value, the act of setting it manually forces envmond to use the manually applied value. Once manually set, the ENVMON_HIGH_THRESH variable persists in the /etc/rc.config database. This will permanently work around the issue for current and future envmond sessions. To manually set the variable, follow these steps:

  1. Determine the the value of ENVMON_HIGH_THRESH:

    # sysconfig -q envmon | grep thresh
    # env_high_temp_thresh = 60
  2. Manually set the threshold value using the envconfig utility:

    # envconfig -c ENVMON_HIGH_THRESH=60

Increasing PCI Box Support on GS1280 M32 to 16 (Aug. 2003)

The maximum number of standard I/O hoses (IDE buses) allowed for an initial install of Tru64 UNIX Version 5.1B from the CD-ROM is eight. Any I/O drawer connected to a hose that has more than eight must be disconnected or powered down during a fresh install from the Tru64 UNIX CD-ROM.

Console Error in the XP1000 Workstation (Aug. 2003)

There is a console error on XP1000 workstations that prevents you from using IDE CD-ROMs attached to the secondary port as boot devices. The secondary IDE devices are seen at the console on the XP1000 as follows:

Primary IDE devices that you can boot from:

dqa0. (master primary) dqa1. (slave primary)

Secondary IE devices that you cannot boot from:

dqb0. (master secondary) dqb1. (slave secondary)

There is no problem in using the IDE devices on the secondary port once the system is set up, but you cannot boot from them.

General and Problem Information for AlphaServer ES47, ES80, and GS1280 Systems (Jan. 2003)

The following information pertains to the new AlphaServer ES47, ES80, and GS1280 systems, which require Tru64 UNIX Version 5.1B and Patch Kit 1 to be installed.

Time Loss (March 2003)

During some operations of the Environmental Monitoring daemon, and the use of some hwmgr commands, these systems may experience time loss. This time loss is caused by problems with the console callbacks for environmental information.

To ensure that this time loss does not occur, do not use the following commands:

# hwmgr -view devices
# hwmgr -view hierarchy

In addition, you must configure your system so that the Environmental Monitoring daemon does not start when the system boots. Follow these steps to reconfigure your system:

  • Edit the /rtc/rc.config file and disable automatic start of the daemon: ENVMON_CONFIG=0

  • Add the following line to the end of the /etc/sysconfig tab file:

    marvel_syvmgmt: MV_Env_Support = 0

If the Environmental Monitoring daemon is running, you must stop the daemon or reboot the system in order for these changes to take effect.

These problems will be corrected with Version 6.4-11 of the AlphaServer firmware.

CPU Offline Restrictions (Jan. 2003)

The primary CPU cannot be taken off line.

CPUs that have I/O hoses attached to them can only be taken off line if another CPU without I/O attached is present in the system . A failure to adhere to this restriction will cause the psradm command to return an error.

In a two–CPU configuration, the AlphaServer ES47 and ES80 systems do not allow any CPUs to be taken off line.

Problem with Capacity–on–Demand Process (Jan. 2003)

A problem has been discovered with the capacity-on-demand process in which a CPU can be designated as spare, but is not taken off line as expected.

With the capacity-on-demand process, the codconfig [cpu_id_list] command lets you specify which CPUs you have paid for and which are spares. The command is supposed to mark the others as spare and then take them off line. Once a CPU is marked as spare, the hwmgr command and Manage CPUs SUITLET will not let you put them on line until you use the ccod -l or ccod -p command to either loan or purchase the CPU.

The workaround to the problem is to use the codconfig [cpu_id_list] command to mark the CPUs as spare, and then use either the hwmgr command or the Manage CPUs SUITLET to take them off line (sometimes referred to as offlining them). In the following example, N is the CPU number.

# hwmgr -offline -name cpuN

If, for example, the codconfig command returns the message "Error for CPU 2: Unable to offline this CPU," you would enter the following hwmgr command:

# hwmgr -offline -name cpu2

For more information, see codconfig(8) and hwmgr(8).

The Manage CPUs SUITLET is available from the SysMan Menu and SysMan Station.

Hardware SCSI Errors (Jan. 2003)

SCSI errors experienced by the Adaptec controller that require SCSI bus resets could cause PCI bus faults. These faults will be seen as a “Machine Check System Uncorrectable” panic. This will require the system to be booted after the machine check. A fix for this problem will be included in a future release.

Compact Disk Drive Errors Logged (Jan. 2003)

The TEAC CDR-W 416E drive that is shipped with the AlphaServer system will log errors on reboot if the CD-ROM media is not present. These messages are only informational.

Presence of Third-Party Devices May Cause System Panic (Jan. 2003)

The ATM 3X-DAPBA-FA/UA driver may experience a panic on shutdown if third-party devices are installed.

Repeated Reboots May Cause Panic (Jan. 2003)

Repeated reboots of the system may cause a kernel memory fault panic, but does not result in the loss of data. A reboot after the panic should be successful. A fix for this problem will be included in a future release.

Incorrect Free Page Counts Reported (Jan. 2003)

The vmstat -S command reports incorrect free page counts on a sparsely configured system. A sparsely configured system is one that has gaps in the numbering of CPUs, for example 0, 1, 8, 9, 10, 11.

USB Keyboard Driver Does Not Support Non-U.S. Locales (Jan. 2003)

The USB keyboard driver does not support non-U.S. locales, and setting the system's language to anything other than 36 (U.S./English) causes the keyboard to be interpreted as a U.S./English keyboard anyway.

For example, on the Japanese keyboard with the SRM variable "language" set to 50 (Japanese JIS), Shift-2 produces a double quote (") character, while on the U.S./English keyboard it produces the at sign (@). With this problem, keyboards set to Japanese will produce the ampersand (&).

A fix for this problem will be included in a future release.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
2002–2009 Hewlett-Packard Development Company, L.P.