| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 93.1 | Update to V1.2-4 SRM console required for all customers | LANDO::CUMMINS | | Thu Jun 06 1996 12:40 | 479 |
| 93.2 | B3002-AB Cached CPU Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:53 | 107 |
| 93.3 | I2C Bus Power-Up Problem Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:54 | 94 |
| 93.4 | Installation Tips Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:57 | 96 |
| 93.5 | Memory Errors Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:58 | 115 |
| 93.6 | B3050 General Information Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:58 | 104 |
| 93.7 | NT 3.51 HAL Blitz | DANGER::HAYES | | Thu Aug 22 1996 14:59 | 69 |
| 93.8 | B3050 Wrong NVRAM Blitz | DANGER::HAYES | | Thu Aug 22 1996 15:00 | 146 |
| 93.9 | S3 Video Adapter Revisions Blitz | DANGER::HAYES | | Mon Sep 09 1996 11:32 | 123 |
| 93.10 | DE500 Autosense | MOVMON::DAVIS | | Wed Sep 11 1996 11:21 | 81 |
| 93.11 | Environmental Status Events | MOVMON::DAVIS | | Wed Sep 11 1996 11:22 | 112 |
| 93.12 | TEST Command and RAID Adapters | MOVMON::DAVIS | | Wed Sep 11 1996 11:22 | 73 |
| 93.13 | 93.11 Sys Env Reg Decoding | POBOXA::SHEPARD | | Fri Sep 13 1996 10:50 | 85 |
| 93.14 | Addendum to "B3050 Wrong NVRAM Blitz" posted in 93.8 | LANDO::CUMMINS | | Mon Sep 16 1996 12:17 | 52 |
| 93.15 | KZPSC FW upgrade or config save crash; older Blitz | LANDO::CUMMINS | | Wed Sep 18 1996 16:55 | 70 |
| 93.16 | DE500 Version and Mode Support | LANDO::CUMMINS | | Fri Sep 20 1996 13:14 | 70 |
| 93.17 | V2.0-3 console required for 400 MHz, 4MB cache CPU based systems | LANDO::CUMMINS | | Thu Oct 17 1996 10:02 | 63 |
| 93.18 | Windows NT 4.0 firmware/hardware requirements/issues | LANDO::CUMMINS | | Thu Oct 17 1996 10:04 | 73 |
| 93.19 | AlphaBIOS V5.24 | MOVMON::DAVIS | | Tue Oct 29 1996 09:29 | 351 |
| 93.20 | AlphaBIOS V5.24 Web Location | MOVMON::DAVIS | | Wed Oct 30 1996 09:17 | 36 |
| 93.21 | BA356 enclosures, RZ29B's, RZ28D's , DWZZB-VW's, and SWXA2-BA | LANDO::CUMMINS | | Mon Nov 04 1996 08:47 | 98 |
| 93.22 | B3002-AB & B3004-AA Cached CPU's | MOVMON::DAVIS | | Wed Nov 06 1996 08:50 | 87 |
| 93.23 | I2C Bus problems (update to previous blitz) | MOVMON::DAVIS | | Tue Nov 12 1996 09:02 | 109 |
| 93.3 | I2C/PCM blitz updated in reply .23 | MOVMON::DAVIS | | Mon Dec 09 1996 10:22 | 2 |
| 93.24 | 2 GByte Memory Option | MOVMON::DAVIS | | Mon Dec 09 1996 10:57 | 51 |
| 93.25 | Windows NT 4.0 not yet supported | MOVMON::DAVIS | | Wed Dec 11 1996 10:33 | 56 |
| 93.26 | KZPSA Configurations (from July, not previously posted) | MOVMON::DAVIS | | Thu Dec 12 1996 13:32 | 75 |
| 93.27 | Windows NT 3.51 (Intermittent FACEFEED bugchecks) | MOVMON::DAVIS | | Mon Dec 16 1996 09:25 | 90 |
| 93.28 | Windows NT 3.51 HAL Rev. C | MOVMON::DAVIS | | Fri Jan 17 1997 17:28 | 83 |
| 93.29 | B3050 Module Handling/Power Control Module Behaviour | MOVMON::DAVIS | | Wed Jan 22 1997 09:49 | 93 |
| 93.30 | Windows NT Installation Failure | MOVMON::DAVIS | | Tue Jan 28 1997 14:34 | 64 |
|
Request log number: 858
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - Windows NT Installation Failure
DATE: January 27, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - Windows NT Installation Failure
Affected System: Alpha Server 4100
Problems:
--------
There have been reports of failure to install Windows NT on newly
delivered systems. This problem is being investigated by Engineering.
The problem appears to be caused by extraneous data in the NVRAM.
Solution
--------
If a Windows NT 3.51 or 4,0 installation fails to continue setup after the
text mode screens you may have extraneous data in the NVRAM. The error
messages vary and they may indicate an unexpected hardware error. Before
fault finding the machine, try the zeroing the NVRAM and repeat the
installation. Please note this procedure was originally documented in a
BLITZ under the topic "Switching between Windows NT and Digital Unix".
Please note that this destroys all data in the eerom.
Zero out the contents of the eerom using the following command at
the SRM Console Prompt:
d -b -n 1FFF eerom:0 0
Note: 0 is the number zero.
Note: You will need to run the ECU for Unix or use CMOS Setup in WNT
after zeroing the contents of the eerom. When you run AlphaBIOS
for the first time after zeroing out the eerom, it will set the
eerom's contents to a valid, default state and then warm boot
back to itself.
tg 01/24/97
|
| 93.31 | AlphaBIOS V5.28 | MOVMON::DAVIS | | Wed Jan 29 1997 16:09 | 317 |
| Request log number: 859
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - AlphaBIOS V5.28
DATE: January 29, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - AlphaBIOS V5.28.
AlphaBIOS V5.28
---------------
AlphaBIOS Version 5.28 is now available from the following location:
http://www.windows.digital.com/support/Firmware/as4000.htp
This version is required to support mixed B3002-AB and B3004-BA (300 MHz
Cached CPU's)
Problems fixed in this version
------------------------------
* Update native Mylex driver to version 4.03.08.
* Update native QLogic driver to version 2.22.
* Disable EV56 byte/word memory instructions for configurations with both
EV5/300 and EV56/300 processors installed. EV56 byte/word IO instructions
are not supported by the AlphaServer 4100 product, and, therefore, are
disabled for all configurations.
* Display the correct SCSI ID for SCSI devices that support adapter/controller
SCSI ID assignment.
* Correctly quantify secondary processors as Ready.
* Removed SCSI ID from SCSIBIOS controlled device messages.
Full Text of Release Notes
--------------------------
****** AlphaBIOS Release Notes for post-FRS release
01/15/97 Version 5.28
Important Information:
----------------------
AlphaBIOS version can be verified from the boot menu, or by pressing
F2 to enter setup and selecting either:
* "About AlphaBIOS...", or
* "Display System Configuration...", then "Systemboard Configuration"
AlphaBIOS version can be verified from the SRM by typing "show flash".
Windows NT Help files can be viewed by typing "winhlp32 filename.HLP".
The release notes below are included in the AB.HLP file.
If using PKUNZIP to uncompress the compressed firmware image obtained from
the firmware update web site, be sure to restore the directory structure
contained in the ZIP file. This is done using the -d option of pkunzip.
Updating AlphaBIOS for 5.28:
----------------------------
To update the AlphaBIOS firmware on Rawhide to 5.28 using the LFU:
1. create the AS4100 Firmware Update floppy by Copying the contents of
the UPDATE directory to a floppy.
2. Insert the AS4100 Firmware Update floppy into the system.
3. Boot AlphaBIOS from the Main Menu, run "Upgrade AlphaBIOS"
4. Select OK to reboot.
At this point, the AS4100 will reboot run the AS4100 load firmware update
utility (LFU).
5. LFU will ask select firmware load device.
Type dva0
6. LFU will next ask you the name of the firmware files list.
Type as4x00cp.
7. LFU will then load the firmware update files from floppy into memory
and then display the LFU prompt.
8. From the LFU prompt, type List. This will show you the current versions
of the SRM and AlphaBIOS (ARC) firmware images.
Note, that if the previous installed AlphaBIOS was not an LFU image,
no version information for the currently installed version will be
available.
9. From the LFU prompt, type Update.
10. LFU will prompt you to confirm update ARC (AlphaBIOS),
type YES.
11. LFU will prompt you to confirm update for any boot drivers supported
by the SRM console (e.g., KZPSA).
type NO for all boot device prompts.
12. LFU will prompt you to confirm update the SRM,
type NO (Unless your SRM is out of rev).
13. If you have any boot devices supported by the SRM (e.g., KZPSA), the
LFU will prompt you to confirm update for each,
type NO for each.
13. LFU will then return to the prompt.
Type exit.
AlphaBIOS V5.28 for AlphaServer 4000 Family Release Notes
----------------------------------------------------------
* Visit Digital Windows NT Info Center's Guide to Hardware Systems for
the latest firmware, driver, and configuration utility information.
The URL is http://www.windows.digital.com/support/Firmware/as4000.htp.
NOTE: If using PKUNZIP to uncompress the compressed firmware image
obtained from this Web site, be sure to restore the directory
structure contained in the ZIP file. This is done using the -d
option of pkunzip.
* EISA Configuration Utility: AlphaServer 4000 systems with no EISA
devices installed do not require running the ECU.
Similarly, removing an EISA device will not force operator to rerun
ECU on subsequent boot of AlphaBIOS -- the device will be
automatically removed from the EISA configuration.
* MC Bus Display. Only revision information for CPU modules and
MC-PCI Bridge modules are valid.
* If the power-up self test detects an error, the following message
will be posted, in red, on the bottom of the MC Bus Display dialog:
Warning: Your system has encountered a power-up test failure.
If this message appears, it means the self test has detected one
or more of the following errors:
* One or more CPU tests failed.
* An I/O subsystem test failed.
* One or more CPUs failed external cache tests.
* An illegal memory configuration was detected.
* The memory address/data line march test fails
* Critical regions of memory are bad.
* Power-up test on embedded drives failed (Floppy, embedded NCR810,
keyboard, mouse, serial port, parallel port, etc.)
Suggested action: Call your field service representative.
* The SRM and AlphaBIOS consoles both provide power-up memory tests.
The SRM power-up memory test will run before AlphaBIOS appears on
your screen. The AlphaBIOS memory test appears as a pop-up dialog
during AlphaBIOS initialization.
AlphaBIOS memory test options are set via the "Advanced CMOS
Setup" dialog, reached by pressing <F6> from the "CMOS Setup" dialog.
AlphaBIOS memory test options made from this dialog will also
be honored by the SRM memory tests. However, SRM memory test
settings via the SRM MEMORY_TEST environment variable will not be
honored by AlphaBIOS.
The correct way to set the memory test parameters for Windows NT
systems is to use AlphaBIOS, not SRM to set memory test options.
Power-up Memory SRM Action AlphaBIOS Action
Test Test Length Test up to: Test up to:
------------------- ---------- ----------------
Disabled n/a 32 Mb (test disabled)
Enabled Partial 256 Mb 256 Mb
Enabled Full All memory up to 1 Gb
* *ALL* VGA-based graphics adapters must plugged into PCI0 (lower
four PCI slots).
Digital ZLXp-E1,E2,E3 graphics adapters (part numbers PBXGA-AN,BN,CN)
may be plugged into any PCI slot.
Other graphics adapters that (a) do not have a BIOS ROM and (b)
are used as secondary Windows NT graphics displays may be plugged into
any PCI slot.
* *S3 CHIPSET BUG MAY DESTROY HARDWARE*
Certain S3-based graphics adapters, when installed on the same bus
as a device that incorporates a PCI-PCI bridge (e.g., Adaptec 3940UW),
may cause damage to other adapter cards on the same bus or to the Alpha
Server 4100 itself. The Alpha Server only supports S3 adapters
based on the TRIO32 chipset, the TRIO64 chipset version 86C764X, and
the Virgie chipset.
* Certain S3-based graphics adapters will hang AlphaBIOS when
installed on the same bus as a Adaptec 3940UW. The chip-sets/versions
that will cause this hang are:
1. All version of the TRIO32,
2. Revision 864X of the TRIO64.
* Certain S3-based adapters will cause AlphaBIOS to hang on reboot.
#9 TRIO64 (version 764X) video adapters with a BIOS version less than
02.03.15 will cause this problem to occur. Contact field service to
receive BIOS upgrades.
* AlphaBIOS may hang when I/O adapters are configured with more than one
level of PCI-PCI bridge. Adapters with a single, embedded PCI-PCI
bridge are functional and are supported.
* Adaptec support in AlphaBIOS V5.12 is limited to the
following AIC7880-based adapters: 2940UW and 3940UW.
* The following Adaptec AIC7870-based adapters are not supported:
2940, 2940W, 2944W, 3940, and 3940W.
* It is now possible to run the Adaptec SCSI select utility from AlphaBIOS.
This is enabled by setting the "BIOS Emulation" environment variable to
"Enabled" from the "Advanced CMOS Setup" menu. When this is done, and
an Adaptec 2940UW or 3940UW is installed in the system on PCI0, then
the SCSI select utility may be entered during SCSI BIOS initialization.
* Digital KZPSA: The KZPSA configuration utility (cnfgdiag.exe V1.4)
and firmware update utility (fwupdate.exe V1.2) will
corrupt the KZPSA NVRAM when used on AlphaServer 4000 systems.
Browse http:\\www.____________________ for updates to these KZPSA
utilities that support the AlphaServer 4000 Family.
* AlphaBIOS no longer supports NTFS file system.
The impacts to the AlphaBIOS user are:
1. Verifying a boot selection from the "OS Selection Setup" item of
the "Utilities" menu can no longer verify the "OS Path" if it
is resides on an NTFS partition.
2. You can no longer run an ARC app from the "Run Maintenance Program"
item of the "Utilities" menu if the ARC app resides on an NTFS partition.
* The AlphaBIOS dynamic memory pool size has been increased. You will
no longer encounter temporary pool problems when running ARC applications
such as the RCU.
* Byte/Word memory instructions are enabled for AlphaServer 4000 systems
with EV56 processors installed. Application programs can now take
advantage of Byte/Word memory instructions on EV56 platforms if they
are compiled with Byte/Word instructions.
* Mylex DAC960 / Digital KZPSC "SWXCRMGR" RAID Configuration Utility
now works on systems configured with 3 Mylex DAC960's (KZPSC)
and 1 or more KZPSC's.
* It is no longer necessary to configure drivers connected to the
Adaptec 2940UW or 3940UW to spin up at power up.
* The AlphaServer 4100 is known to hang in the SRM when the kernel
debugger is attached to the system. The workaround is to either
detach the kernel debugger cable from the system when rebooting,
or set an SRM environment variable to prevent this from occurring.
For the latter, you must update the SRM console version to V2.0-3
or higher and set the SRM environment variable tt_allow_login to
zero.
Problems fixed in this version
------------------------------
* Update native Mylex driver to version 4.03.08.
* Update native QLogic driver to version 2.22.
* Disable EV56 byte/word memory instructions for configurations with both
EV5/300 and EV56/300 processors installed. EV56 byte/word IO instructions
are not supported by the AlphaServer 4100 product, and, therefore, are
disabled for all configurations.
* Display the correct SCSI ID for SCSI devices that support adapter/controller
SCSI ID assignment.
* Correctly quantify secondary processors as Ready.
* Removed SCSI ID from SCSIBIOS controlled device messages.
|
| 93.32 | SRM bootdef_dev | MOVMON::DAVIS | | Wed Jan 29 1997 16:36 | 70 |
|
Request log number: 860
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SRM bootdef_dev
DATE: January 29, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - SRM bootdef_dev
Problem
-------
If a PCI boot adapter pointed to by the SRM console bootdef_dev is swapped
with a non-boot adapter/device and an attempt is made to display or
manipulate the bootdef_dev the console will hang or fail the operation.
An example would be swapping a KZPSA with a VGA adapter.
If auto_action is set to boot and bootdef_dev is in this undesirable
state, the effect is that boots will hang. The only way to get out of
this situation is to depress the front-panel halt button and take the
actions listed under Solution. Similarly, a boot command that relies upon
bootdef_dev will fail/hang unless the problem is corrected.
Solution
--------
To correct this state, either the configuration needs to be restored or
the SRM console's NVRAM needs to be erased. Please note that erasing the
NVRAM will cause all saved environment variables to be lost,
To erase the SRM's NVRAM, type the following at console:
P00>>> d eerom:1800 -b -n 7ff 0
Then cycle reset and reset any preferred environment variables.
Long Term Fix
-------------
Version 4.8 console corrects this problem and also adds features to assist
if similar problems are encountered:
- save/restore NVRAM contents to/from a floppy diskette.
This is implemented as save_nvram and restore_nvram scripts
which tell the user what to do.
- Clear_arc_nvram and clear_srm_nvram scripts which provide an alternative
to the deposit mentioned in the solution.
tg 01/29/96
|
| 93.33 | Raid Initialisation Times | MOVMON::DAVIS | | Thu Jan 30 1997 16:12 | 60 |
|
Request log number: 861
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - Raid Initialisation Times
DATE: January 30, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - Raid Initialisation Times
Affected System: AlphaServer 4000 and 4100
Affected Module: Backplane RAID Adapters - KZPSC, KZPAC
Problem
-------
Long initialisation time for backplane based RAID controllers, examples
are the KZPSC and the KZPAC, on the AlphaServer 4100 family.
Work Around
-----------
Use the serial mode RCU to reduce RAID initialization times faster by a
factor of three or more compared to graphics mode RCU. The serial mode
RCU is currently available to customers, both on the FW CD and on the RCU
floppy that ships with the adapter. The serial mode RCU can be run from
graphics mode AlphaBIOS, however the user interface will suffer. Tests
indiate that using the serial mode RCU with a RAID5 set consisting of 4
RZ29's, initialization time took 16 minutes, compared to over an hour for
the graphics mode RCU.
The serial mode RCU is currently named srlmgr.exe. The image names of
both the serial and graphics mode RCU will change for RCU release V4.27,
which supports the KZPAC (Pluto+). This change goes into effect for the
images on the 3.9 FW CD and the V4.27 RCU floppy. The graphics mode RCU
will change from swxcrmgr.exe to ra200rcu.exe. The serial mode RCU will
change from srlmgr.exe to ra200srl.exe.
mb/tg 01/30/97
|
| 93.34 | SRM Console V4.8-3 | MOVMON::DAVIS | | Mon Feb 03 1997 14:58 | 203 |
|
Request log number: 865
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SRM Console V4.8-3
DATE: February 3rd, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : AlphaServer 4100 - SRM Console V4.8-3
Problem:
--------
SRM Console V4.8-3 is required for mixed B3004-BA and B3002-AB
configurations. It is recommended that sites are updated as soon as
possible.
This new console is required for:
. 300 MHz EV56 Pass1 and Pass2 CPUs and mixed 300 MHz EV5 and EV56 systems
. 466 MHz CPUs
. Durango (AlphaServer 4000 with I/O upgrade)
. Ferret (AlphaServer 4100LP from CSS)
. BOOTP (RIS) installs over FDDI
. BOOTP or MOP loads/boots across subnets
V4.8-3 includes new OpenVMS and Unix PAL code which corrects a byte offset
problem when building soft error machine check frames.
The Readme file is included for your reference.
The new console is not yet available on the World Wide Web, but is available
internally in a public release area with a $README.TXT file to indicate which
files should be used for your particular update preference:
Directory MAY30::FIRM03:[RAWHIDE.INTERIM.V48]
$README.TXT;1 6 3-FEB-1997 09:57:47.00 (RWE,RWE,RE,RE)
AS4X00CP.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
AS4X00FW.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
AS4X00IO.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
CIPCA315.SYS;1 50 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
DFXAA310.SYS;1 168 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
FWREADME.TXT;1 11 31-JAN-1997 13:20:38.00 (RWE,RWE,RE,RE)
KZPSAA10.SYS;1 176 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
RHARCROM.SYS;1 897 31-JAN-1997 13:20:30.00 (RWE,RWE,RE,RE)
RHLFU.SYS;1 2931 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
RHREADME.SYS;1 12 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
RHSRMROM.SYS;1 1727 31-JAN-1997 13:20:31.00 (RWE,RWE,RE,RE)
Within a week or two, V4.8-3 console (or a later version) will be posted on
the Web at the following interim location:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00
V4.8-3 SRM and V5.28 AlphaBIOS consoles (or later versions) will be available
on the V3.9 Alpha Firmware Update CD, which is currently planned to FRS on or
about 3/6/97. At that time, the /interim/as4x00 area will be deleted in favor
of the following Web site (/as4x00):
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/as4x00
V4.8-3 SRM Console Readme File
------------------------------
++++++++++++++++++++++++++++++++++++++
+ AlphaServer 4100/4000 Firmware +
+ README-First !!! +
++++++++++++++++++++++++++++++++++++++
1. When updating console firmware, it is recommended that you update both the
SRM and AlphaBIOS consoles at the same time to insure compatibility between
versions.
2. Helpful Hints on using the UPDATE and LIST commands
UPD> update srm* to update the SRM console firmware.
UPD> update alpha* to update the AlphaBIOS console.
UPD> update * to update all firmware in your system.
UPD> update * -all to update all firmware in your system without having
to confirm each update
UPD> list to display adapters in your system that are supported
by the Loadable Firmware Utility [LFU]
3. Latest Firmware Update Revisions
The latest Firmware Update Bootfile "AS4X00_V4_8.EXE" on the Alpha Firmware
CD V3.9, contains V4.8 SRM Console, which has the following components:
(* = CHANGED since last release)
--> SRM console V4.8 *
--> XSROM V4.8 *
--> OpenVMS PALcode V1.19-5 *
--> Digital UNIX PALcode V1.21-17 *
--> AlphaBIOS console V5.28 *
--> CIPCA FW version A315
--> DEFPA FW version V3.10 *
--> ISP1020 FW version V2.10 (included in SRM console)
--> KZPSA FW version A10
4. Firmware Enhancements and New Features (SRM and AlphaBIOS Consoles)
V4.8 SRM console adds the following new features:
--> Support for AlphaServer 4000 with expanded I/O support (Spring, 1997).
--> Official support for AlphaServer 4100/4000 466 MHz CPUs. Note: V3.0-10
console claimed support for the 466MHz CPUs but qualification of these
CPUs brought to light some power-up and test issues. V4.8 console or
greater must be used on systems with 466 MHz CPUs.
--> Support for the B3004-BA (EV56 300 MHz 2MB cache) CPU. The B3002-AB (EV5
300 MHz 2MB cache) and B3004-BA CPUs can be mixed in the same system. If
mixed, you are required to configure the B3002-AB as the primary CPU -
this is typically CPU0.
--> Support for BOOTP booting (RIS installs) over FDDI (DEFPA).
--> Support for network booting across subnets.
--> Minor enhancements to OpenVMS and Digital UNIX PALcode for slight
improvement in interrupt performance.
--> Support for FAT floppy writes from console.
--> Scripts for saving and restoring NVRAM (used for AlphaBIOS and SRM
environment variable and other parameters, as well as ECU data) to/from
a floppy diskette (script names are SAVE_NVRAM and RESTORE_NVRAM).
--> Version change to V4.8 to synchronize with other AlphaServer platform
console versions which ship on the Alpha Systems Firmware Update CD.
V4.8 SRM console fixes the following bugs (in V3.0-10):
--> Fix for proper handling of I/O-detected, single-bit (CRD) errors detected
while running OpenVMS, Digital UNIX, or console TEST. Previous versions
of PALcode could erroneously report 630 CRD errors as 620s; potentially
with error frames skewed by one byte, thereby making DECevent analysis
quite difficult.
--> Fix for BOOT command hang if BOOTDEF_DEV is set to a device and the
device's adapter gets swapped with a non-boot adapter. For example,
a KZPSA is swapped with a VGA adapter.
--> Fix for CIPCA hang if type a SHOW DEVICE or BOOT command with an HSC70
offline.
--> Fixes for TEST command involving CIPCA or 8 GB memory configurations.
V5.48 AlphaBIOS includes the following changes since AlphaBIOS V5.24:
--> Support for mixed CPU type: B3002-AB and B3004-BA.
--> Native Mylex driver version V4.03.08 included.
--> Native Qlogic driver version V2.22 included.
--> Display the correct SCSI ID for SCSI devices that support adapter
or controller SCSI ID assigment.
--> SCSI ID removed from SCSIBIOS controlled device messages.
--> Correctly quantify secondary processors as Ready.
5. Firmware Anomalies, Restrictions, and Workarounds
--> If running OpenVMS or Digital UNIX, the MEMORY_TEST environment variable
must be set to FULL (default). PARTIAL and NONE are not supported.
--> VGAs configured as console display devices must be in PCI0.
--> The system must be reset prior to running LFU from console. Booting the
LFU off CD/ROM does not require a system reset.
--> A minimum S3 V+ VGA BIOS version of 2.16.07 is required for 1MB boards
(2.36.07 for 2MB boards).
6. AlphaServer 4100/4000 Firmware Release Notes
If you wish to read the complete FW release notes for the AlphaServer
4100/4000 they can be found on the V3.9 Alpha FW Update CD, in the
following directories:
--> On an OpenVMS System:
[DOC]ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
[DOC]ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Digital UNIX System:
/DOC/ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
/DOC/ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Windows NT System:
\DOC\ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
\DOC\ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
bc/tg 02/03/97
|
| 93.35 | CPU Module B3004-BA | MOVMON::DAVIS | | Mon Feb 03 1997 15:05 | 134 |
|
Request log number: 867
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - CPU Module B3004-BA
DATE: February 3rd, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - CPU Module B3004-BA
Affected System: AlphaServer 4000 and 4100, multi-processor configuration
Affected Module: B3002-Ab and B3004-BA 300 MHz 2 MByte cached CPU.
Problem
-------
The 300 MHZ 2 MByte cached CPU based on the EV5 CPU chip, module B3002-AB
is no longer available because no more EV5 chips are being made. The
| B3004-BA is being introduced as a plug in replacement for the B3002-AB.
The B3004-BA uses the EV5/6 CPU chip. In order to ensure complete
compatibility between the B3002 and the B3004, the EV5/6 is operated in
EV5 mode.
The Hardware Restart Parameter Block is used to identify to the Operating
System the type and speed of the processor module. Changes have been made
to the way OpenVMS handle the HWRPB so that mixed configurations will
work.
Customer Letter
---------------
A Customer Letter is being sent with all Systems, CPU and SMP Upgrades, 2
GByte Memory Option upgrades. The letter informs the Customer of the
minimum revision requirements for SRM, AlphaBIOS and VMS patch level.
Mixed CPU Module Support
------------------------
In order to run mixed B3002 and B3004-BA CPU's the following configuration
rule and minimum revisions need to be followed:
1. The Primary CPU **MUST** be a B3002
2. The SRM console must be at a minimum version of V4.8
3. AlphaBIOS needs to be at a minimum version of 5.28
4. For OpenVMS systems, a patch needs to be added
Location of Supporting Firmware and Patches
-------------------------------------------
VMS KIT
The TIMA kit is located at BULOVA::PUBLIC2$:[REMEDIAL_KITS].
ALPCPU1601_071.A - Release notes and KITINSTAL.COM procedure
ALPCPU1601_071.B - V6.2 image
ALPCPU1601_071.C - V7.1 image
There are also 2 text files, the Cover Letter and Submission Form. The
Cover Letter and the Release Notes are the same document and go tothe
customer. The Submission Form stays internal with customer support.
ALHABIOS V5.28
http://www.windows.digital.com/support/Firmware/as4000.htp
(See BLITZ Title AlphaServer 4100 AlphaBios Version 5.28 for Release Notes)
SRM V4.8
The new console is not yet available on the World Wide Web, but is available
internally in a public release area with a $README.TXT file to indicate which
files should be used for your particular update preference:
Directory MAY30::FIRM03:[RAWHIDE.INTERIM.V48]
$README.TXT;1 6 3-FEB-1997 09:57:47.00 (RWE,RWE,RE,RE)
AS4X00CP.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
AS4X00FW.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
AS4X00IO.SYS;1 3 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
CIPCA315.SYS;1 50 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
DFXAA310.SYS;1 168 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
FWREADME.TXT;1 11 31-JAN-1997 13:20:38.00 (RWE,RWE,RE,RE)
KZPSAA10.SYS;1 176 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
RHARCROM.SYS;1 897 31-JAN-1997 13:20:30.00 (RWE,RWE,RE,RE)
RHLFU.SYS;1 2931 31-JAN-1997 13:20:33.00 (RWE,RWE,RE,RE)
RHREADME.SYS;1 12 31-JAN-1997 13:20:32.00 (RWE,RWE,RE,RE)
RHSRMROM.SYS;1 1727 31-JAN-1997 13:20:31.00 (RWE,RWE,RE,RE)
Within a week or two, V4.8-3 console (or a later version) will be posted on
the Web at the following interim location:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00
(See BLITZ Title AlphaServer 4100 SRM Console V4.8 for Release Notes)
============================================================================
Please note the following immediate short term problem:
Some Alphaserver 4100 B3004-BA CPU's have been shipped as spares. This module
was not scheduled to FRS until February 7th. The effects are that VMS will fail
to run SMP because it checks the HWRPB and finds a mismatch in CPU types.
The work around is to request further spares until a matched set of CPU's
is obtained!
If you have a mixed configuration resulting from Field Spares activities, it is
recommended that a request for additional spares be made until all the CPU's
are the same type.
Please note that Unix and Windows NT systems will load and run.
tg 2/03/97
|
| 93.36 | SRM Console Version 4.8-5 | MOVMON::DAVIS | | Wed Feb 12 1997 14:39 | 264 |
|
Request log number: 877
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SRM Console Version 4.8-5
DATE: February 12, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - SRM Console V 4.8-5
*********************************** UPDATE ******************************
* This updates the information in BLITZ Subject *
* Alpha Server 4100 - SRM Console V4.8-3 *
*********************************** UPDATE ******************************
Problem
-------
A problem has been found with versions V4.8-3 and V4.8-4 console. Console
will not start any version of AlphaBIOS when the system is configured with
more than 2 GBs of memory, but less than 4GBs of memory. V4.8-X console
will start AlphaBIOS with 4GBs or more of memory, but SRM passes a bad
pointer to the ARC memory descriptors that it builds, thereby causing ECU,
RCU, and Windows NT 4.0 to not work.
The code bug was introduced when the SRM builds were switched from the VAX
C Compiler to the Alpha 64-bit C compiler.
The primary purpose of the console was to support mixed CPU types, 466
MHz (B3004-DA) CPUs, and 2 GB memory upgrades. A small number of B3004-BA
CPU's are already in Field Spares and a low number of upgrade kits have
been shipped with the V4.8-3 version. Between 25 to 50 systems and upgrade
kits have shipped with the V4.8-3 SRM console.
Resolution
----------
The V4.8-5 console version should be used on all systems, the earlier
versions will work correctly providing there is 2 Gbyte or less memory on
the system. It is recommended that earlier versions of V4.8 be replaced
at the earliest opportunity.
Manufacturing are currently shipping systems under waiver with V4.8-3
console. This means removal of memory above 2GBs to run ECU, RCU, etc.
and then restoration of the system's proper memory config prior to
shipping the unit. If the V4.8-3 Console is used on systems with more
than 2 GBytes Memory AND you need to use the ECU and RCU you will need to
follow the same procedures of reducing the memory configuration to 2
GBytes or less.
The V4.8-4 console, which contained the work-around for the "VMS MCHK
crash dump if VGA installed" problem will be obsoleted. It was posted on
the Web in an /interim/as4x00 subdirectory. If you obtained a copy of
this console, please replace it as soon as possible with the new V4.8-5
bits in this same /interim/as4x00 subdirectory. The problem that V4.8-4
and V4.8-5 worked around is detailed at the end of this message.
V4.8-5 Availability
-------------------
The SRM console is available from the following locations:
MAY30::FIRM03:[RAWHIDE.INTERIM.V48]*.* (see $README.TXT)
(files available immediately)
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00/
(files available at this Web site by end of day 2/12/97)
Alpha Firmware Update CD V3.9
(still on target to ship on 3/3/97)
V4.8-5 LFU Update README File
-----------------------------
++++++++++++++++++++++++++++++++++++++
+ AlphaServer 4100/4000 Firmware +
+ README-First !!! +
++++++++++++++++++++++++++++++++++++++
1. When updating console firmware, it is recommended that you update both the
SRM and AlphaBIOS consoles at the same time to insure compatibility between
versions.
2. Helpful Hints on using the UPDATE and LIST commands
UPD> update srm* to update the SRM console firmware.
UPD> update alpha* to update the AlphaBIOS console.
UPD> update * to update all firmware in your system.
UPD> update * -all to update all firmware in your system without having
to confirm each update
UPD> list to display adapters in your system that are supported
by the Loadable Firmware Utility [LFU]
3. Latest Firmware Update Revisions
The latest Firmware Update Bootfile "AS4X00_V4_8.EXE" on the Alpha Firmware
CD V3.9, contains V4.8-5 SRM Console, which has the following components:
(* = CHANGED since last release)
--> SRM console V4.8-5 *
--> XSROM V4.8 *
--> OpenVMS PALcode V1.19-5 *
--> Digital UNIX PALcode V1.21-18 *
--> AlphaBIOS console V5.28-0 *
--> CIPCA FW version A315
--> DEFPA FW version V3.10 *
--> ISP1020 FW version V2.10 (included in SRM console)
--> KZPSA FW version A10
4. Firmware Enhancements and New Features (SRM and AlphaBIOS Consoles)
V4.8 SRM console adds the following new features:
--> The FRU_TABLE environment variable default has been changed to ON. FRU
Table Version 4.0 support is implemented in the DECevent Knowledge
Library (.KNL files ) update to DECevent V2.3. If you are not running
with this version of DECevent then you should either update DECevent
(web site for DECevent: http://www.service.digital.com/decevent/) or set
the environment variable to OFF. Please read the V4.8 firmware release
notes for more details.
--> Support for AlphaServer 4000 with expanded I/O support (Spring, 1997).
--> Official support for AlphaServer 4100/4000 466 MHz CPUs. Note: V3.0-10
console claimed support for the 466MHz CPUs but qualification of these
CPUs brought to light some power-up and test issues. V4.8 console or
greater must be used on systems with 466 MHz CPUs.
--> Support for the B3004-BA (EV56 300 MHz 2MB cache) CPU. The B3002-AB (EV5
300 MHz 2MB cache) and B3004-BA CPUs can be mixed in the same system. If
mixed, you are required to configure the B3002-AB as the primary CPU -
this is typically CPU0.
--> Support for BOOTP booting (RIS installs) over FDDI (DEFPA).
--> Support for network booting across subnets.
--> Minor enhancements to OpenVMS and Digital UNIX PALcode for slight
improvement in interrupt performance.
--> Support for FAT floppy writes from console.
--> Scripts for saving and restoring NVRAM (used for AlphaBIOS and SRM
environment variable and other parameters, as well as ECU data) to/from
a floppy diskette (script names are SAVE_NVRAM and RESTORE_NVRAM).
--> Version change to V4.8 to synchronize with other AlphaServer platform
console versions which ship on the Alpha Systems Firmware Update CD.
V4.8 SRM console fixes the following bugs (in V3.0-10):
--> Fix for proper handling of I/O-detected, single-bit (CRD) errors
detected while running OpenVMS, Digital UNIX, or console TEST.
Previous versions of PALcode could erroneously report 630 CRD errors
as 620s; potentially with error frames skewed by one byte, thereby
making DECevent analysis quite difficult.
--> Fix for the problem on systems running OpenVMS where a machine check
660 or 670 results in the system stopping at an XDELTA breakpoint and
not continuing with a crash dump. This problem occurs on OpenVMS
systems configured with a VGA adapter in the PCI backplane and is
independent of the CONSOLE setting (SERIAL or GRAPHICS).
--> Fix for BOOT command hang if BOOTDEF_DEV is set to a device and the
device's adapter gets swapped with a non-boot adapter. For example,
a KZPSA is swapped with a VGA adapter.
--> Fix for CIPCA hang if type a SHOW DEVICE or BOOT command with an HSC70
offline.
--> Fixes for TEST command involving CIPCA or 8 GB memory configurations.
--> Support for handling SCSI bus resets in the middle of booting. Fixes
a hang problem seen with simultaneous boots and crash dumps in a SCSI
cluster with a shared KZPSA bus.
V5.48 AlphaBIOS includes the following changes since AlphaBIOS V5.24:
--> Support for mixed CPU type: B3002-AB and B3004-BA.
--> Native Mylex driver version V4.03.08 included.
--> Native Qlogic driver version V2.22 included.
--> Display the correct SCSI ID for SCSI devices that support adapter
or controller SCSI ID assigment.
--> SCSI ID removed from SCSIBIOS controlled device messages.
--> Correctly quantify secondary processors as Ready.
5. Firmware Anomalies, Restrictions, and Workarounds
--> If running OpenVMS or Digital UNIX, the MEMORY_TEST environment variable
must be set to FULL (default). PARTIAL and NONE are not supported.
--> VGAs configured as console display devices must be in PCI0.
--> The system must be reset prior to running LFU from console. Booting the
LFU off CD/ROM does not require a system reset.
--> A minimum S3 V+ VGA BIOS version of 2.16.07 is required for 1MB boards
(2.36.07 for 2MB boards).
6. AlphaServer 4100/4000 Firmware Release Notes
If you wish to read the complete FW release notes for the AlphaServer
4100/4000 they can be found on the V3.9 Alpha FW Update CD, in the
following directories:
--> On an OpenVMS System:
[DOC]ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
[DOC]ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Digital UNIX System:
/DOC/ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
/DOC/ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Windows NT System:
\DOC\ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
\DOC\ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
OpenVMS Failure to Write CrashDump on Unrecoverable System Machine Check
------------------------------------------------------------------------
V4.8-5 (and V4.8-4) console also fix a failure to dump on OpenVMS systems
when a VGA graphics adapter is installed in the PCI backplane (even if the
SRM CONSOLE environment variable is set SERIAL). This problem has existed
since 4100/4000 product introduction. An OpenVMS patch may be issued which
will fix this problem, but the console has been updated to work around the
issue since there is no guarantee that a VMS patch will be issued.
The inability to crash is caused by the following sequence of events:
1. A 660 or 670 or other system fatal MCHK occurs (e.g. fan failure, DTAG
parity error, fill error, etc.)
2. VMS eventually calls CB_OPEN to begin the process of writing the crash.
3. To regain control of the I/O, we reset the PCIs, including a VGA re-init,
if VGA is present.
4. Since we use the BIOS emulator for VGA init, we take MCHKs while the BIOS
option ROM code probes the PCI. We normally handle/dismiss these MCHKs via
a handler we install. On a UNIX dump, we handle the MCHKs gracefully since
MCES is clear, and then go on to successfully dump. However, during a VMS
dump, PAL sees MCES set and throws up its hands with a double error halt
(as it should) rather than dispatching to the console's MCHK handler.
5. Console eventually regains control, but can find no valid context (as
expected) since it has been "consumed" as part of the callback entry.
6. Console has nowhere to go so it restarts its krn$_idle flow (basically a
console restart) versus it's halt entry flow. Upon realizing that there's
no valid context, console throws up its hands and breakpoints in XDELTA.
7. Meanwhile, secondaries are coming back through krn$_idle and printing
messages like "console starting on CPU n" which only further adds to the
confusion (and can hang the console terminal since these messages are
issued via pprintfs versus printfs and are normally staggered by node ID).
The problem described is specific to OpenVMS only, and only if a VGA card
is present in the system.
bc/tg 02/12/97
|
| 93.37 | Windows NT 4.0 | MOVMON::DAVIS | | Mon Feb 17 1997 09:38 | 105 |
|
Request log number: 880
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 2000/4000 Families - Windows NT 4.0
DATE: February 17, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : AlphaServer 2000/4000 Family Products, Windows NT 4.0
Affected System: Alpha Server 2000/4000 running Windows NT 4.0
There is a bug in Windows NT 4.0, Windows NT 4.0 Service Pack 1 and
Windows NT 4.0 Service Pack 2 on multiprocessor Alpha systems, e.g.
AlphaServers 2000, 2100, 2100A, 4000 and 4100. This bug causes memory
pool corruption that causes the system to crash, typically with a "System
Service Exception" bug check.
This problem will be resolved in Windows NT 4.0 Service Pack 3. As an
interim solution, customers may upgrade their Windows NT 4.0
multiplrocessor AlphaServers to Windows NT 4.0 Service Pack 2, and apply
the "hot fix" (QFE) available from Microsoft via anonymous FTP from
ftp://ftp.microsoft.com
/bussys/winnt/winnt-public/fixes/usa/nt40/hotfixes-postSP2/Alpha-fix/
>> Please note that I split the path name to make it fit 80 columns <<
>> If you go direct please type the complete path on one line. <<
There are 2 files in this direectory:
ALPHA40.EXE 1462 KB Sat Feb 15 00:17:00 1997
README.1ST
The README.1ST file is appended to the end of this blitz.
AlphaServer 4100 and the HCL
----------------------------
Please note that the availability of the QFE does NOT mean that the
Alphaserver 4100 is on the Microsoft Hardware Compatibility List. It does
mean that the QFE will now allow the 4100 to run the Hardware
Compatibility Tests. It is estimated to take two more weeks before the
4100 is listed on the HCL.
README.1ST Contents
-------------------
NOTE: This update is to be applied only to multi-processor Alpha machines
running Windows NT 4.0 with Service Pack 2 installed.
Installation Instructions:
* Download one of the self-extracting executables from the list below, and
place it into an empty temporary directory on the computer to be hotfixed.
- Alpha40.EXE Hotfix for the Alpha platform
* Type the name of the hotfix (Alpha40, for instance). The hotfix will
self extract as shown below:
C:\ALPHA-FIX>ALPHA40
---
PKSFX (R) FAST! Self Extract Utility Version 2.04g 02-01-93
Copr. 1989-1993 PKWARE Inc. All Rights Reserved. Registered version
PKSFX Reg. U.S. Pat. and Tm. Off.
Searching EXE: C:\ALPHA-FIX\ALPHA40.EXE
Inflating: HALRAWMP.DLL
Inflating: HOTFIX.EXE
Inflating: HOTFIX.INF
Inflating: NTKRNLMP.EXE
Inflating: NTOSKRNL.EXE
Inflating: Q156410.TXT
Inflating: README.TXT
---
* Follow the instructions in the extracted Readme.txt file.
mb/tg 02/17/97
|
| 93.38 | SRM V4.8-5, Memory Test EV | MOVMON::DAVIS | | Thu Feb 20 1997 16:05 | 62 |
|
Request log number: 883
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SRM V4.8-5, Memory Test EV
DATE: February 20th, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - SRM V4.8-5, Memory Test EV
Affected System: AlphaServer 4000 and 4100, all Operating Systems
Problem
-------
A re-occuring problem in the field and in benchmark centres is that the
SRM MEMORY_TEST environment variable is set to other than FULL. There
seems to be an increase in these reports resulting from the installation
of SRM Version 4.8-5. If this environment variable is not set to full
symptoms ranging from failure to load Unix to system crashes in NT will be
observed.
The Release Notes that describe the need to set the MEMORY_TEST
environment variable to FULL may not have been included with all copies
of the upgrade documentation. There are also unconfirmed reports of the EV
being set to a value other than FULL by the LFU.
Resolution
----------
For ALL OPERATING SYSTEMS please ensure that the MEMORY_TEST environment
variable is set to FULL.
The environment variable setting may be verified at the SRM Console Prompt
using the following command sequence:
>>>show memory_test
>>>set memory_test Full
>>>init
tg 02/20/97
|
| 93.39 | Errorlog Decode Byte Offset | MOVMON::DAVIS | | Wed Feb 26 1997 10:03 | 79 |
|
Request log number: 886
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - Errorlog Decode Byte Offset
DATE: February 26, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 2
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - Errorlog Decode Byte Offset
Problem
-------
A bug has been found in the Digital Unix and OpenVMS PAL code which
causes, under certain circumstances, the errorlog to be offset by a byte
in Correctable Read Data (MChk 620/630) handling. The potential for the
problem to occur is present in all AlphaServer 4100 SRM Console Code prior
to release 4.8-5.
If you encounter entries in the errorlog indicating a Machine Check code
of 400, an unassigned code, that record may be offset by a byte. Please
note that this only affects individual records, other entries in the same
log file will be correctly recorded and reported.
Description
-----------
1. An I/O-detected 620 CRD error is delivered as a device IPL (21)
interrupt by the IOD.
2. PAL is supposed to raise IPL to MCHK IPL at this point. In all
versions of SRM console prior to V4.8-X, IPL is not raised..
3. During the course of handling the 620 error, PALcode will scrub
the location if the 620 was a memory CRD error. When PAL reads
the bad location in order to write it back (scrub it), if the
error was not a transient, the CPU takes a 630 CRD error since
it sees the same bad ECC.
4. If IPL is at MCHK IPL, which it should be at, the 630 will pend
until the 620 can be fully serviced. The bug in PAL is such that
the 630 can potentially come in on top of the 620. [Software CRD
handlers typically raise IPL to MCHK IPL (31), but there's still
a window between PAL dispatching to the interrupt service routine
(ISR) and when IPL is actually raised by the handler.]
5. The net effect of the 630 on top of the 620 is that PAL passes a
minus one (FFFFFFFF) pointer to the ISR and when this pointer is
added to various other hard-coded offsets, it results in the CRD
frame passed by PAL to the upper level software being off by one
byte. This causes the CRD entry to the screen (if at console) or
the system error log entry (if at UNIX/VMS level) to be shifted
by one byte.
Resolution
----------
Upgrade to the V4.8-5 SRM console if you are experiencing this problem.
Occurrences have been rare and the only documented and analysed case was
from a site being monitored by DPP that was experiencing greater than 15
CRD's per hour.
bc/tg 02/26/97
|
| 93.40 | Rack Mount Cabinet Electrical Distribution | MOVMON::DAVIS | | Mon Mar 03 1997 09:49 | 54 |
|
Request log number: 890
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - Rack Mount Cabinet Electrical
Distribution
DATE: February 28, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 2
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - Rack Mount Cabinet Electrical Distribution
Problem
-------
The AlphaServer 4100 Rackmount Cabinet fitted with Input Box Part Number
30-54353-01 uses 208 to 240 Volt AC for internal power distribution. The
power is made available through IEC sockets. If you obtain an appropriate
IEC cable, it is possible to connect electrical devices to the cabinet
distribution that are not universal power safe. The results are fatal to
the device that only expect to operate from 100 to 120 Volts.
Resolution
----------
Do not connect service of other devices to the internal electrical
distribution. If you need to connect a device to the internal
distribution, please ensure it will accept universal power before
connecting and using the device.
If the Customer wants 110 Volt internal distribution, AC Inpu Box H7600-AA
is approved for use. Please note that the output is NEMA and a NEMA to
IEC cable will be needed to connect to the internal distribution strip.
tg 2/28/97
|
| 93.41 | Customer Letter & Instructions for 4100 Upgrades | MOVMON::DAVIS | | Tue Mar 04 1997 14:35 | 292 |
| From: POBOXB::GENT
Subj: COPY - Customer Letter & Instructions for 4100 Upgrades
Hello All,
This is a text copy of the letter that accompanies CPU upgrades. The original
letter was a DOC file number AV-R34LD-TE.
I have heard problems with the field not having this info.
ted.
============================================================================
Before starting an upgrade, be sure to read the AlphaServer 4100/4000 Read
Me First attachment, which describes enhancements to the latest SRM and
AlphaBIOS console firmware versions as well as bug fixes and workarounds.
Firmware Requirements for CPU Upgrades
The following CPU upgrades require the minimum SRM and/or AlphaBIOS console
firmware revision shown below.
SMP Upgrades CPU Number Description Minimum
SRM AlphaBIOS
------------+-----------+-------------------------------+-------+-------
KN302-BC B3002-AB 5/300 (2 MB) CPU for Windows NT 4.8-5 5.28
B3004-BA
KN304-DD B3004-DA 5/466 (4 MB) CPU for Windows NT 4.8-6 5.28
KN302-BA B3002-AB 5/300 (2 MB) CPU DIGITAL UNIX 4.8-5 NA
B3004-BA
KN304-DB B3004-DA 5/466 (4 MB) CPU DIGITAL UNIX 4.8-6 NA
KN302-BB B3002-AB 5/300 (2 MB) CPU for OpenVMS 4.8-5 NA
B3004-BA
KN304-DC B3004-DA 5/466 (4 MB) CPU for OpenVMS 4.8-6 NA
Before you install any of these processors, make sure your firmware is at
or above the minimum level. Failure to update the firmware to this level
can result in system problems. If you need to update your firmware, refer
to the Read Me First attachment and then follow the Console Firmware
Update Instructions.
SMP Upgrade or Speed Upgrade
If you are performing an SMP upgrade or speed upgrade on a system running
OpenVMS, update the SRM console first. Then install the enclosed OpenVMS
CPU Update Kit, as described in the attached OpenVMS CPU Update Kit
instructions.
If you are performing an SMP upgrade or speed upgrade on a system running
Windows NT, update the SRM console first, then update the AlphaBIOS
console.
Firmware Support for 5/466 MHz 4-MB CPUs (B3004-DA)
The 5/466 MHz 4-MB CPU is fully supported by Version 4.8-6 of the SRM
console firmware. This firmware version corrects a problem that existed
in earlier versions of the SRM firmware. Refer to the Read Me First
attachment for complete information.
Firmware Requirements for Memory Upgrades
If you are upgrading your AlphaServer 4100 or 4000 system with the
MS330-GA 2-gigabyte memory option, the SRM console must be at minimum
revision V4.8-6. If you need to update your SRM firmware, refer to the
Read Me First attachment and then follow the Console Firmware Update
Instructions.
Configuration Requirements for Mixing 300 MHz CPUs
SRM console V4.8-6 supports mixing of the B3002-AB and B3004-BA CPUs
within an AlphaServer 4100 or 4000 system. If you mix modules, you must
configure the system such that a B3002-AB is the primary CPU. The primary
CPU is always installed in slot CPU0 unless CPU0 has failed.
Changes to fru_table and memory_test Environment Variables
The following changes to environment variables apply to AlphaServer 4100
or 4000 systems running either DIGITAL UNIX or OpenVMS at SRM console
V4.8-6. Refer to the Read Me First attachment for details.
The default for the fru_table environment variable has been changed to ON.
This change has implications for running DECevent. The memory_test
environment variable must be set to FULL prior to booting your system.
PARTIAL and NONE are not supported.
Thank you for your cooperation on these issues.
Yours sincerely,
Ron Woodcock
AlphaServer 4000/4100 Engineering Program Manager
Attachments:
AlphaServer 4100/4000 Read Me First
Console/AlphaBIOS Update Instructions
OpenVMS CPU Update Kit Instructions
AlphaServer 4100/4000 Read Me First
Carefully read this read-me first information in its entirety. It
describes several issues you should be aware of to ensure that you
configure your system correctly:
Changes to the memory_test and fru_table environment variable settings
An important fix in SRM console firmware V4.8-6 for systems running with
5/466 MHz CPUs (B3004-DA) Configuration rule for mixing 300 MHz CPUs
within a system (B3002-AB, B3004-BA) Release of SRM Console V4.8-6 Version
4.8-6 of the SRM console is not available on V3.9 of the Alpha Systems
Firmware Update CD-ROM. The V4.8-6 firmware files and complete release
notes are available from the World Wide Web as follows:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00/
The V4.8-6 and V4.8-5 consoles are different in only one way: V4.8-6
adjusts critical b-cache initialization settings to fix a problem
described in more detail in the next section.
Firmware Enhancements and New Features (SRM and AlphaBIOS Consoles)
The V4.8-6 SRM console adds the following new features:
Support for the AlphaServer 4000 system with expanded I/O support (from 8
PCI slots to 16 PCI slots).
You can obtain update files for DECevent from the World Wide Web at:
http://www.service.digital.com/decevent/
Support for BOOTP booting (RIS installations) over FDDI (DEFPA).
Support for network booting across subnets.
Minor enhancements to OpenVMS and Digital UNIX PALcode for slight
improvement in interrupt performance.
Support for FAT floppy writes from console.
Scripts for saving and restoring NVRAM (used for AlphaBIOS and SRM
environment variables and other parameters, as well as ECU data) to and
from a diskette. The script names are SAVE_NVRAM and RESTORE_NVRAM.
Version change to SRM console V4.8 to synchronize with other AlphaServer
platform console versions that are shipped on the Alpha Systems Firmware
Update CD.
Bug Fixes
The V4.8 SRM console fixes the following bugs (in V3.0-10):
Fixes handling of I/O-detected, single-bit (CRD) errors observed while
running OpenVMS, DIGITAL UNIX, or the SRM test command. Previous versions
of PALcode could erroneously report 630 CRD errors as 620 errors;
potentially with error frames skewed by one byte, thereby making analysis
with DECevent difficult.
Fixes a problem on systems running OpenVMS whereby a machine check 660 or
670 results in the system stopping at an XDELTA breakpoint and not
continuing with a crash dump. This problem occurs on OpenVMS systems
configured with a VGA adapter in the PCI backplane and is independent of
the setting of the console environment variable (serial or graphics).
Fixes a boot command hang that occurs if the bootdef_dev environment
variable is set to a device and the device's adapter is swapped with a
non-boot adapter -- for example, a KZPSA SCSI adapter swapped with a VGA
adapter.
Fixes a hang that occurs with the CIPCA PCI-CI adapter if you type a show
device or boot command and an HSC70 storage controller is off-line.
Fixes a problem with the SRM test command that occurs with the CIPCA
PCI-CI adapter or 8 GB memory configurations.
Provides support for handling SCSI bus resets in the middle of booting.
Fixes a hang problem seen with simultaneous boots and crash dumps in a
SCSI cluster with a shared KZPSA bus.
Changes to AlphaBIOS Console
V5.28 of the AlphaBIOS console includes the following changes since
AlphaBIOS V5.24:
Supports mixing KN302-Bx and KN304-Fx CPUs in the same system.
Includes native Mylex driver version V4.03.08.
Includes native Qlogic driver version V2.22.
Displays the correct SCSI ID for SCSI devices that support adapter or
controller SCSI ID assignment.
Removes SCSI ID from SCSIBIOS controlled device messages.
Correctly quantifies secondary processors as Ready.
Firmware Anomalies, Restrictions, and Workarounds
VGA adapters configured as console display devices must be installed in PCI0.
You must reset the system before running LFU from the SRM console.
However, no system reset is required if you boot the LFU from the CD-ROM.
A minimum S3 V+ VGA BIOS version of 2.16.07 is required for 1-MB boards.
Console Firmware Update Instructions
P00>>> lfu
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: dva0
Please enter the name of the firmware files list, or
Press <return> to use the default filename [AS4X00IO,(AS4X00CP)]: as4x00cp
Copying AS4X00CP from DVA0 .
Copying RHREADME from DVA0 .
Copying RHSRMROM from DVA0 ...........................
Copying RHARCROM from DVA0 ...............
------------------------------------------------------------------------------
Function Description
------------------------------------------------------------------------------
Display Displays the system's configuration table.
Exit Done exit LFU (reset).
List Lists the device, revision, firmware name, and update revision.
Lfu Restarts LFU.
Readme Lists important release information.
Update Replaces current firmware with loadable data image.
Verify Compares loadable and hardware images.
? or Help Scrolls this function table.
------------------------------------------------------------------------------
UPD> list
Device Current Revision Filename Update Revision
AlphaBIOS V5.24-0 arcrom V5.28-0
srmflash V3.0-10 srmrom V4.8-6
UPD> update srm*
WARNING: updates may take several minutes to complete for each device.
Confirm update on: srmflash [Y/(N)] y
DO NOT ABORT!
srmflash Updating to V4.8-6............. Verifying V4.8-6... PASSED.
UPD> update alp*
WARNING: updates may take several minutes to complete for each device.
Confirm update on: AlphaBIOS [Y/(N)] y
DO NOT ABORT!
AlphaBIOS Updating to V5.28-0... ....... Verifying V5.28-0... PASSED.
UPD> exit
Initializing...
OpenVMS CPU Update Kit Instructions
Kit Name: ALPCPU1601_071
Kit Description:
Version(s) of OpenVMS to which this kit may be applied:
OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, V7.1
Files patched or replaced for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3:
[SYS$LDR]SYS$CPU_ROUTINES_1605.EXE (new image)
Files patched or replaced for OpenVMS Alpha V7.1:
[SYS$LDR]SYS$CPU_ROUTINES_1605.EXE (new image)
Installation Instructions
Install this kit with the VMSINSTAL utility by logging into the SYSTEM
account and typing the following at the DCL prompt:
$ @SYS$UPDATE:VMSINSTAL ALPCPU1601_071 [location of the saveset]
The saveset location may be a tape drive or a disk directory that contains
the kit saveset.
Reboot the system after successful installation of the kit. Also reboot
any other nodes in your OpenVMS cluster in order to make use of the new
image(s).
|
| 93.42 | Memory Test Environmental Variable | MOVMON::DAVIS | | Tue Mar 04 1997 15:03 | 52 |
|
Request log number: 892
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - Memory Test Environment Variable
DATE: March 4th, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - Memory Test Environment Variable
Problem
-------
AlphaBIOS and the SRM console share the MEMORY_TEST environment variable.
Digital Unix and OpenVMS depend on the console to pass memory descriptors
based on a FULL memory test. If the MEMORY_TEST environment variable is
not set to FULL, all operating systems (Unix, VMS and Windows NT) will
behave unpredictably.
AlphaBIOS will change the MEMORY_TEST EV setting (shared between SRM and
AlphaBIOS consoles) when one saves/exits from the AlphaBIOS CMOS set-up,
even when the memory test enabled/disabled and partial/full menu items are
not touched or altered in any way.
Resolution
----------
If you use the AlphaBIOS CMOS Set-up feature, please ensure that the
MEMORY_TEST environment variable is set to FULL.
bc/tg 03/04/97
|
| 93.43 | Location of Firmware | MOVMON::DAVIS | | Wed Mar 05 1997 11:09 | 44 |
| From: POBOXB::GENT
To: @LAB_STATUS.DIS, @SUPP.DIS
CC:
Subj: AphaServer 4100 - Location of Firmware
Hello All,
There seems to be some confusion in the field concerning the physical location
of the firmware for Rawhide. I sent a blitz out a while back on the B3050
Saddle Module replacement. It now seems like a number of field personnel are
starting to work on Rawhides that have had no training or the training course
is omitting this information. The problem appears to originate from field
familiarity with TurboLaser.
I have received a few calls which initially puzzled me because the Field
Technician 'insisted' on updating the CPU's firmware! Hans has seen this
behaviour as well - see attached note.
How can we get a low level message out to the field that the firmware is on the
Saddle and that there is no work needed on the CPU's?
Thanks ted
=============== Attached note from Hans ===============================
Subj: B3004-DA and new Firmware.
Ted,
As it happens, not everyone in MCS seems to know the Firmware, needed to
fix the problem with B3004-DA (cache timing), is located on B3050-AA.
Some people, also some responsible for service strategies, have the impression
that the FW is on the CPU (like it is with TLASER).
Since not every B3050-AA in the stock and in the Field is automatically updated
it may be advisable to inform the MCS world that to prevent B3004-DA problem
after an upgrade or after a B3050-AA replacement people should check the
Firmware on the B3050-AA to be at least V4.8-6. I already issued a waiver to
update the B3050-AA currently in repair to this version.
Thanks for your help
Hans
|
| 93.44 | V4.0 FRU Table and DECevent | MOVMON::DAVIS | | Thu Mar 06 1997 09:47 | 92 |
|
Request log number: 893
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - V4.0 FRU Table and DECEevent
DATE: March 5th, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : AlphaServer 4100 - V4.0 FRU table support and DECevent
Problem:
--------
The AlphaServer 4100 SRM Console implements the Version 4.0 FRU Table
specification. V4.0 adds the entire SRM console's power up event log
together with other features and changes from previous versions. Versions
of DECEvent prior to V2.3 will hang or possibly crash the operating system
when reading a system error log file's V4.0 FRU table entry.
The V3.0-10 SRM console release implements V4.0 FRU table entries. An
environment variable called FRU_TABLE was added in this release to control
the build of the FRU table. The default setting in V3.0-10 was "OFF".
V4.8-xx SRM console (and later versions) enable V4.0 FRU table building by
default (FRU_TABLE = "ON"). FRU table entries in the system error log are
important, and indeed are often necessary, to properly determine the field
replaceable unit (FRU) in the event of a system hardware error.
Resolution:
-----------
The recommended DECevent version for complete and proper AlphaServer 4000
and 4100 support for Configuration Entries containing a V4.0 FRU Table is
DECevent V2.3, which also has the DECevent V2.3.3 .KNL update kit added. A
major DECevent V2.4 release is expected to be available shortly, and when
available, will replace V2.3 and the V2.3.x .KNL updates. DECevent kits,
and updates can be obtained from the DECevent web site at:
http://www.service.digital.com/decevent/
If you do not update to V2.3 (plus KNL update kit) DECevent or greater,
then you must disable FRU table configuration entries by setting FRU_TABLE
to "OFF". Still, it is HIGHLY recommended that you update DECevent rather
than disable V4.0 FRU table entries. In addition to the importance of FRU
table entries in diagnosing faulty machines, DECevent V2.3 (plus update)
corrects several problems that existed in V2.2 DECevent and additionally
adds improved machine check decode support.
The DECevent "SHOW KNL" command can be used to display the current version
of DECevent and its associated .KNL files installed. If DECevent V2.3,
with the V2.3.3 .KNL update kit is installed, the "SHOW KNL" command will
show some of the .knl files as version KNL023.3. If you have installed the
soon-to-beavailable DECevent V2.4 kit, the .KNL files will show KNL024.0.
If OpenVMS, type: "dia show knl". If Digital UNIX, type: "dia shw knl".
Note that the UNIX command is slightly different.
A matrix of SRM console versions, with corresponding FRU table version
implemented, FRU_TABLE environment variable default (if applicable), and
minimum DECevent version required (if V4.0 FRU table is built by console)
is provided below..
+------------+----------------+----------------+---------------------------+
| Console | FRU Version | FRU_TABLE EV | Minimum DECevent Version |
+------------+----------------+----------------+---------------------------+
| V1.0-9 | N/A | N/A | V2.2 |
| V1.2-3, -4 | N/A | N/A | V2.2 |
| V2.0-3 | V3.0 FRU table | N/A | V2.2 |
| V3.0-10 | V4.0 FRU table | Default = OFF | V2.3 + V2.3.3 .KNL Update |
| V4.8-xx | V4.0 FRU table | Default = ON | V2.3 + V2.3.3 .KNL Update |
+------------+----------------+----------------+---------------------------+
N/A = Not Applicable
bc/tg 03/05/97
|
| 93.45 | SRM V4.8-6, 466 MHz CPU's | MOVMON::DAVIS | | Thu Mar 06 1997 10:09 | 263 |
|
Request log number: 895
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SRM V4.8-6, 466 MHz CPU's
DATE: March 6th, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - V4.8-6 Console, 466 MHZ Cpu's
Problem:
--------
The B3004-DA, 466 MHz CPU's require the V4.8-6 console to operate error
free. If the 4.8-5 version is used, BCache soft error machine checks will
be reported in the errorlog. The 4.8-6 version was released too late for
inclusion in the V3.9 CD. A few systems may have shipped with the
incorrect 4.8-5 version installed.
A typing error has been found on the label of the floppy diskette included
with some systems. The diskette label lists AlphaBIOS version 5.8, this
is incorrect, the firmware image is correct, it is AlphaBIOS Version 5.28
and the label should be corrected.
Location of Firmware
--------------------
The SRM FIRMWARE is stored on the B3050 (Saddle) module. THERE IS NO NEED
TO REPLACE THE CPU, THE FIRMWARE FOR THE SRM AND ALPHABIOS IS NOT STORED
ON THE CPU MODULES. The 4100 family design is DIFFERENT from the 8400, I
STRONGLY RECOMMEND using your SUPPORT RESOURCES in the SUPPORT CENTRES if
you have not worked on a 4100 family product before. PLEASE DO NOT MAKE
ASSUMPTIONS ABOUT THE DESIGN OF THE 4100 FAMILY PRODUCTS BASED ON YOUR
EXPERIENCE WITH OTHER PLATFORMS.
Resolution:
-----------
For installations using or upgrading to the B3004-DA 466 MHz processor
modules, please upgrade the firmware to 4.8-6. Please do not assume that
a newly delivered machine has the correct firmware, please verify the
version. The release notes are appended for your reference.
V4.8-6 Notes
------------
V4.8-6 console is now being factory-installed on all AlphaServer 4100/4000
systems (as of ~3/5/97). These systems are also being shipped with a QZ
kit which contains a V4.8-6 SRM console (and V5.28 AlphaBIOS) update
floppy diskette with instructions for its use. This same QZ kit is being
shipped with 466 MHz CPU upgrades as well and can/should be used to
upgrade the PCI motherboard's system flash ROM during CPU upgrades.
The V4.8-6 console will also be available on the WWW on or before 3/6/97,
and can be found at:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00/
Note that V4.8-5 is currently posted at this site as of today (3/5/97).
When the Web's /interim/as4x00 directory is updated with the new V4.8-6
bits, the V4.8-5 images will be moved to the V3.9 FW CD release area:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/v3.9/as4x00/
You should therefore check dates on files pulled from the /interim/as4x00
area during the next couple of days (since the new files will have the
same names as the V4.8-5 files..)
++++++++++++++++++++++++++++++++++++++
+ AlphaServer 4100/4000 Firmware +
+ README-First !!! +
++++++++++++++++++++++++++++++++++++++
1. Please CAREFULLY read this readme file IN ITS ENTIRETY. There are several
issues you should be aware of, including:
--> MEMORY_TEST and FRU_TABLE environment variable (EV) settings; you must
understand the impact of these EVs upon system behavior.
--> An important fix in V4.8-6 for customers running with 466 MHz CPUs.
--> Info about mixed 300 MHz CPU (B3004-BA and B3002-AB) configurations.
Version V4.8-6 was released after the V3.9 FW CD submission date, so is not
available on the V3.9 CD. The V4.8-6 and V4.8-5 consoles are different in
only one way: V4.8-6 adjusts critical b-cache initialization settings to fix
a problem described in more detail below. V4.8-6 must be used on AlphaServer
4100 and 4000 5/466 4MB systems.
2. When updating console firmware, it is recommended that you update both the
SRM and AlphaBIOS consoles at the same time to insure compatibility between
versions.
3. Helpful Hints on using the UPDATE and LIST commands
UPD> update srm* to update the SRM console firmware.
UPD> update alpha* to update the AlphaBIOS console.
UPD> update * to update all firmware in your system.
UPD> update * -all to update all firmware in your system without having
to confirm each update
UPD> list to display adapters in your system that are supported
by the Loadable Firmware Utility [LFU]
UPD> readme to display this readme file you are reading now
4. Latest Firmware Update Revisions
The latest Firmware Update Bootfile "AS4X00_V4_8.EXE" on the Alpha Firmware
CD V3.9, contains V4.8-5 SRM Console, which has the following components:
[ * = CHANGED since V3.0-10 SRM console release (V3.8 FW Update CD) ]
--> SRM console V4.8-5 *
--> XSROM V4.8 *
--> OpenVMS PALcode V1.19-5 *
--> Digital UNIX PALcode V1.21-18 *
--> AlphaBIOS console V5.28-0 *
--> CIPCA FW version A315
--> DEFPA FW version V3.10 *
--> ISP1020 FW version V2.10 (included in SRM console)
--> KZPSA FW version A10
Again, note that V4.8-6 did not make it onto the V3.9 FW Update CD/ROM. It
is or will very soon be available at the following Web site, however:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/as4x00/
5. Firmware Enhancements and New Features (SRM and AlphaBIOS Consoles)
V4.8 SRM console adds the following new features:
--> Support for AlphaServer 4000 with expanded I/O support.
--> Official support for AlphaServer 4100/4000 466 MHz CPUs. Note: V3.0-10
console claimed support for the 466MHz CPUs but qualification of these
CPUs brought to light some power-up/test issues. In addition, V4.8-6
SRM console fixes a HW issue discovered after earlier versions of V4.8
console (V4.8-3, V4.8-5) were shipped. All versions of console prior to
V4.8-6 initialize the 466 MHz CPUs' b-caches with values that can lead
to 630 single-bit cache errors (and possibly uncorrectable errors) on
certain configs. V4.8-6 console adjusts the cache settings to resolve
this problem, and does so with zero performance impact.
--> Support for the B3004-BA (EV56 300 MHz 2MB cache) CPU. The B3002-AB (EV5
300 MHz 2MB cache) and B3004-BA CPUs can be mixed in the same system. If
mixed, you MUST configure the system such that a B3002-AB is the primary
CPU - this is typically CPU0.
--> The FRU_TABLE environment variable default has been changed to ON. FRU
Table Version 4.0 support is only implemented in the DECevent Knowledge
Library (.KNL files ) update to DECevent V2.3. If you are not running
with V3.0-10 consoel or above then you should either update DECevent
(web site for DECevent: http://www.service.digital.com/decevent/) or set
the FRU_TABLE environment variable to OFF. Earlier versions of DECevent
can hang or possibly crash the system when reading an OpenVMS or Digital
UNIX system error log that has a V4 FRU table in it. A FRU_TABLE setting
of ON (now the default) will result in a V4 FRU table entry being copied
to your UNIX/VMS system error log on every operating system boot.
--> Support for BOOTP booting (RIS installs) over FDDI (DEFPA).
--> Support for network booting across subnets.
--> Minor enhancements to OpenVMS and Digital UNIX PALcode for slight
improvement in interrupt performance.
--> Support for FAT floppy writes from console.
--> Scripts for saving and restoring NVRAM (used for AlphaBIOS and SRM
environment variable and other parameters, as well as ECU data) to/from
a floppy diskette (script names are SAVE_NVRAM and RESTORE_NVRAM).
--> Version change to V4.8 to synchronize with other AlphaServer platform
console versions which ship on the Alpha Systems Firmware Update CD.
V4.8 SRM console fixes the following bugs (in V3.0-10):
--> Fix for proper handling of I/O-detected, single-bit (CRD) errors
detected while running OpenVMS, Digital UNIX, or console TEST.
Previous versions of PALcode could erroneously report 630 CRD errors
as 620s; potentially with error frames skewed by one byte, thereby
making DECevent analysis quite difficult.
--> Fix for the problem on systems running OpenVMS where a machine check
660 or 670 results in the system stopping at an XDELTA breakpoint and
not continuing with a crash dump. This problem occurs on OpenVMS
systems configured with a VGA adapter in the PCI backplane and is
independent of the CONSOLE setting (SERIAL or GRAPHICS).
--> Fix for BOOT command hang if BOOTDEF_DEV is set to a device and the
device's adapter gets swapped with a non-boot adapter. For example,
a KZPSA is swapped with a VGA adapter.
--> Fix for CIPCA hang if type a SHOW DEVICE or BOOT command with an HSC70
offline.
--> Fixes for TEST command involving CIPCA or 8 GB memory configurations.
--> Support for handling SCSI bus resets in the middle of booting. Fixes
a hang problem seen with simultaneous boots and crash dumps in a SCSI
cluster with a shared KZPSA bus.
V5.48 AlphaBIOS includes the following changes since AlphaBIOS V5.24:
--> Support for mixed CPU type: B3002-AB and B3004-BA.
--> Native Mylex driver version V4.03.08 included.
--> Native Qlogic driver version V2.22 included.
--> Display the correct SCSI ID for SCSI devices that support adapter
or controller SCSI ID assigment.
--> SCSI ID removed from SCSIBIOS controlled device messages.
--> Correctly quantify secondary processors as Ready.
6. Firmware Anomalies, Restrictions, and Workarounds
--> If using OpenVMS or Digital UNIX, the MEMORY_TEST environment variable
must be set to FULL (default). PARTIAL and NONE are not supported. The
default value is FULL. However, saving/exiting from the AlphaBIOS' CMOS
setup menu can result in the shared MEMORY_TEST environment variable
being changed to PARTIAL. Anything less than FULL is not supported by
OpenVMS. UNIX supported partial memory testing prior to SRM console
version V3.0-10. However, a requested change to the way in which the
SRM builds memory descriptors was implemented in V3.0-10 and beyond,
and this has aggravated a latent bug in all versions of UNIX which can
lead to panics during booting and other unpredictable system behavior.
Until the UNIX issue has been resolved, both OpenVMS and UNIX customers
must insure that MEMORY_TEST is set to FULL prior to booting.
--> VGAs configured as console display devices must be in PCI0.
--> The system must be reset prior to running LFU from console. Booting the
LFU off CD/ROM does not require a system reset.
--> A minimum S3 V+ VGA BIOS version of 2.16.07 is required for 1MB boards
(2.36.07 for 2MB boards).
7. AlphaServer 4100/4000 Firmware Release Notes
If you wish to read the complete FW release notes for the AlphaServer
4100/4000 they can be found on the V3.9 Alpha FW Update CD, in the
following directories:
--> On an OpenVMS System:
[DOC]ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
[DOC]ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Digital UNIX System:
/DOC/ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
/DOC/ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
--> On a Windows NT System:
\DOC\ALPHA4100_V48_FW_RELNOTE.PS (PostScript file)
\DOC\ALPHA4100_V48_FW_RELNOTE.TXT (Text file)
ps/tg 03/06/97
|
| 93.46 | Errors on SCSI Busses | MOVMON::DAVIS | | Mon Apr 28 1997 12:24 | 79 |
| From: POBOXA::GENT
To: @LAB_STATUS.DIS, @SUPP.DIS
CC:
Subj: BLITZ - AlphaServer 4100 Errors on SCSI Busses sent to distribution
Subject : BLITZ - AlphaServer 4100 Errors reported on SCSI busses
Received from : POBOXA::GENT
Request log number: 927
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SCSI Bus and Related Errors
DATE: April 24, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 2
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - SCSI Bus and Related Errors
AlphaServer 4100 - Errors on SCSI Busses
1. Problem:
Test coverage on the B3040 'Horse' module has been found marginal in
identifying problems in the 'Scatter-Gather' mapping. The result is that
some modules have been shipped which may have latent defects.
2. Susceptibility:
Scatter-Gather mode use varys depending on the adapter type. The NCR810
based controllers - KZPAA and the On-Board SCSI controller for the CD-ROM
always use Scatter-Gather mode. Unix uses Scatter-Gather mode for other
SCSI controllers if the memory configuration exceeds 1 GByte.
3. Symptoms:
Symptoms of the problem will vary, some of the problems seen include:
a) Excessive SCSI errors on NCR810 based devices
b) SCSI (CAM) errors reported during the system boot
c) System crashes (panics) with Bus Faults
d) Performance degradation accessing disk subsystems or CDROM
e) Occasional Power Up Self Test failures indicating an IOD failure
f) Failure to initialise graphics correctly
g) Moving all of the PCI adapters to one (of the) PCI bus makes the system
function properly.
4. Fault Finding:
If you are involved in trouble shooting a system where you are experiencing
any of the symptoms listed above, the B3040 may be the problem module.
5. Prevention:
A screen is being implemented in Stage 1 and Stage 2 Manufacturing to
remove defective B3040 modules. The screen went into effect in April. This
means that any systems currently in the field may have this problem
6. Severity:
Screening indicates that this problem may be seen on as high as 10% of the
population of B3040's
tg 4/22/97
|
| 93.47 | AlphaServer 4100 B3020-CA sync memory failures | HARMNY::CUMMINS | | Wed May 14 1997 09:37 | 103 |
| +---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: AlphaServer 4100 B3020-CA sync memory failures.
{{Product Model #(s)} - {Symptom Summary} (Max. total 65
char. spaces)}
PRIORITY LEVEL: {1 = Time Critical, 2 = Non-Time Critical}
DATE:
TD #: {Generated by MCS}
AUTHOR: Bruce Alford
DTN: 223-6862
EMAIL: proxy::alford
DEPARTMENT: RSE
============================================================
PRODUCT NAME(S): AlphaServer 4100
PRODUCT FAMILY(IES): {Check all that apply}
Storage ___
Systems/OS _x_
Networks ___
PC/Peripherals ___ {includes printers, monitors, etc.}
Software Apps. ___
BLITZ TYPE: {Check all that apply}
Maintenance Tip _X_ {Info. will assist servicing
the product}
Service Action Requested ___ {MCS is requested to perform
an activity}
IF SERVICE ACTION IS REQUESTED: (Check all that apply.)
Labor Support Required ___ {Requires MCS to provide
service labor}
Material Support Required ___ {Requires MCS to provide
material}
Estimated time to complete activity (in hours):
Will this require a change in the field's inventory:
Yes ___ No ___
Will an FCO be associated with this advisory? Yes ___ No _X_
DESCRIPTION OF SERVICE ACTIVITY REQUESTED (if applicable):
"Inform customer that the configuration is not supported."
"Have customer contact the PBU at ____ to obtain
replacement
***********************************************************
PROBLEM STATEMENT:
AlphaServer 4100 systems using B3020-CA (sync) memories may
experiences system crashes with failure information pointing
to uncorrectable memory errors.
SYMPTOM:
The problem can manifest it self as either 620 or 660 MCHK
errors, with a footprint simular, to those caused by bad
memory. The configurations that is susceptible to this
problem is a 3 or 4 CPU AlphaServer 4100 systems with 6 or more
B3020-CA and a Rev B06 54-23803-01 mother board installed.
The errorlog information will usually indicate a uncorrect-
able memory failure in one of the B3020-CA (sync) memories.
In some instances this failure has caused the AS4100 to drop
into the console XDELTA prompt. Swapping in new B3020-CAs
does not fix the problem.
Note: AS4100 systems using EDO memories (B3030-EA/FA/GA) with
the a Rev B06 motherboard will not encounter this problem.
Also, AlphaServer 4000 systems with 54-23803-02's or
54-23805-01s (any Rev) will not encounter this problem.
SOLUTION:
AlphaServer 4100 systems using B3020-CA memories, exhibiting
these types of failures, and replacing the B3020-CA does not
fix the problem, should replaced the motherboard with a
minimum Rev. B07 (54-23803-01).
*** DIGITAL INTERNAL USE ONLY ***
|
| 93.48 | SCSI Bus CAM and Related Errors | MOVMON::DAVIS | | Tue Jun 03 1997 15:10 | 62 |
| Subject : BLITZ AlphaServer 4100 CAM errors
Received from : POBOXA::GENT
Request log number: 965
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Alpha Server 4100 - SCSI Bus and Related Errors
DATE: June 03, 1997
AUTHOR:Ted Gent TD #:
DTN:223-6530
ENET:POBOXA::GENT CROSS REFERENCE #'s:
DEPARTMENT:SBU Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S/EUROPE/GIA PRIORITY LEVEL: 1
(1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
Subject : Alpha Server 4100 - SCSI Bus and Related Errors
AlphaServer 4100 - Errors on SCSI Busses
1. Problem:
When a KZPDA is configured on PCI Bus 1, which has the embedded controller
for the CD/ROM, and simultaneous transfers from CD/ROM and disks connected
to the KZPDA are occurring, SCSI Bus errors may occur. This problem has
been reproduced using Unix, SCSI error rate is higher with V3.2F and G and
lower with V4.0A and V4.0B. An error rate high enough to cause builds to
fail has been observed.
2. Discussion
A test script which generates simultaneous traffic from the CD/ROM and the
KZPDA will effectively simulate this problem. Different types of adapters
have been tested and the only adapter exhibiting this problem is the KZPDA.
3. Work Around
If the KZPDA is moved to PCI Bus 0 the problem will not occur.
Please note this has ONLY been reproduced using the Unix operating system
and the KZPDA connected to PCI 1. If you move the KZPDA to PCI Bus 0 the
symptoms will not occur.
4. Long Term
We are continuing investigations on this problem. A follow up BLITZ will be
generated when a final solution has been found.
tg 06/03/97
|
| 93.49 | How to Recognize & Recover from AdvFS corruption | MOVMON::DAVIS | | Wed Jun 04 1997 18:03 | 78 |
|
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: How To Recognize & Recover from AdvFS corruption.
DATE:
AUTHOR: John Donovan TD #:
DTN: 381-1344
ENET: guru::donovan CROSS REFERENCE #'s:
DEPARTMENT: UNIX Support Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: All PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
INTRODUCTION:
Recently several customer escalations to DIGITAL UNIX have been sent
to engineering regarding data corruption in AdvFS.
PROBLEM:
After careful examination, it became apparent that recovery procedures
were not adequately documented resulting in undue escalations
RESOLUTION/WORKAROUND:
This has resulted in DIGITAL UNIX documenting how to recover from
AdvFS failures. The new "AdvFS How to recover from failure" web pages
can be found at:
http://www.zk3.dec.com/useg/tech_info/filesystem/advfs_howto.html
Note: This is Under construction and will be updated every so often!
ADDITIONAL COMMENTS:
The above web page should be checked every so often for changes so
that current methods will always be in use.
*** DIGITAL INTERNAL USE ONLY ***
\\ GRP=TIME_DEPENDENT CAT=HARDWARE DB=CSSE_TIME_CRITICAL
\\ TYPE=KNOWN_PROBLEM TYPE=BLITZ STATUS=CURRENT
------- End of Forwarded Message
|