Greetings -
A quick question regarding the upgrade from 3.2g through 4.0a to get to 4.0b.
We have an assortment of alpha machines: 3000-300, 2100, 2100A, 4100, 8400
and I have been unable to get a sucessful 4.0a install on the 2100s, but was
able to on the 3000-300s. Has anybody else seen this? Is it a bad 4.0A
CD? Has anybody done this upgrade on an 8400 successfully? Looming on the
horizon is our main production machine (24x7), it's an 8400 and our window
for the upgrade doesn't allow rebuilding the entire system disk from scratch.
We have tried using firmware from the v5.0CD (same results), and are
currently using the supported-under-4.0B firmware from the v3.9CD:
Firmware revision: 4.7
VMS PALcode V5.56-6, OSF PALcode X1.45-12
Here's the problem ( Machine Check SYSTEM Fatal Abort
panic (cpu 0): System Uncorrectable Machine Check 660):
single user# /sbin/installupdate /dev/rz6c
...
The Digital UNIX V4.0A (Rev. 464) Update Installation will update the
following Digital UNIX products:
Digital UNIX V3.2G
Digital UNIX V4.0
...
****** Updating system to Digital UNIX V4.0A (Rev. 464)
84 subset(s) will be installed.
...
Loading 1 of 84 subset(s)....
...
84 of 84 subset(s) installed successfully.
...
*** Merging new file ./.new..DXsession into
existing ./.proto..DXsession
...
Merge completed successfully.
Update Installation complete with loading of subsets.
Rebooting system with Digital UNIX V4.0A (Rev. 464)
generic kernel for configuration phase...
Exiting Update Installation...
syncing disks... done
rebooting.... (transferring to monitor)
...
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x4000600010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x4000c0002012d>
Sizes:
text = 5135776
data = 1295920
bss = 3387904
Starting at 0xfffffc000045e0e0
Alpha boot: available memory from 0x207a000 to 0x4ffee000
Digital UNIX V4.0A (Rev. 464); Mon Aug 19 23:30:25 EDT 1996
physical memory = 1280.00 megabytes.
available memory = 1247.45 megabytes.
using 4907 buffers containing 38.33 megabytes of memory
...
psiop0 at pci0 slot 1
Loading SIOP: script 888b00, reg 81222000, data 8a8a88
Machine Check SYSTEM Fatal Abort
ptr[0-1] = 000000010000008a 0000000000000000
ptr[2-3] = 000002f800000004 0000000200000000
ptr[4-5] = 0000000000000680 0000000000000030
ptr[6-7] = 0000000000000240 0000000000004200
ptr[8-9] = 0000000000000400 0000000000000000
...
panic (cpu 0): System Uncorrectable Machine Check 660 (retry set)
DUMP: No primary swap, no explicit dumpdev.
Nowhere to put header, giving up.
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc000045fb40
P00>>>
Digital has acknowledged problems with 2100As sometimes yielding this result,
but stated this was not seen on 2100s. Any ideas?
Randy Hayman
Received on Mon Nov 10 1997 - 19:10:27 NZDT