Boot failure on V6.2-1H2

Hi,

I have a setup that worked fine on Personal Alpha. I tried running it on the latest version (Beta 271) and got the following error:

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>%RUN-S-PROC_ID, identification of created process is 00000112
**** OpenVMS (TM) Alpha Operating System V6.2-1H2 - BUGCHECK ****
** Code=000001CC: INVEXCEPTN, Exception while above ASTDEL
** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000001
** Current Process = LATACP
** Image Name =
**** Starting Memory Dump...
....
**** Memory Dump complete - not all processes saved
halted CPU 0
halt code = 5
HALT instruction executed
PC = ffffffff8004a1c4
CPU 0 booting<br><br><br></code>

Here is the config:
< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>cp = control
{
cp_log = logfile
{
filename = "C:&#92;test&#92;test.log&quot
}

alpha = alpha
{
memory=128M;
image = "C:&#92;test&#92;test.nvr&quot
pcibus = dc21071da
{
data = "C:&#92;test&#92;test.toy&quot
serial0 = i16550
{
s0_tn = telnet
{
port = 9000;
wait = true;
action = """C:&#92;Program Files&#92;FreeAXP&#92;putty.exe"" telnet://localhost:9000&quot
}
}

pci7 = i82378
{
}

pci6 = symbios
{

disk0.2 = file
{
image = "C:&#92;test&#92;dka200.img&quot
}

disk0.4 = file
{
image = "C:&#92;test&#92;dka400.img&quot
}
}

pci11 = de500
{
adapter="ask&quot
}
}
}
}<br><br><br></code>

I'm running 32-bit Windows Server 2003 on Dual-Core E6500 @ 2.93GHz with 2.99 GB of RAM.

Thanks for any help.<hr>

This is a software crash in LATACP.

Please take into account, that FreeAXP emulates a different network adapter (EWA instead of ESA in PersonalAlpha).

A system dumpfile has been written, so boot again with PersonalAlpha and you should automatically get a CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS file being created during startup. Feel free to mail this file to me.

Then try to first boot FreeAXP without starting LAT, TCPIP, DECnet. And change your LAN device names in all those procedures and configurations from using ESA to using EWA.

Volker.

I'm using a fresh copy of the image backup that I had made from a working AlphaStation 255. So I assume it is still using the EWA interface.

I'll try to disable LAT and DECnet and see if the system boots. I'm a VMS Noob so this might take a while.

Also, I searched for any CLUE*.LIS but there was none.

Kinsa

Kinsa,

a system dump should have been written. Please check, if you have a SYS$SYSTEM:SYSDUMP.DMP file. If so, try:

$ ANAL/CRASH
SDA&gt; CLUE CRASH
SDA&gt; CLUE REGISTER
SDA&gt; CLUE CONFIG
SDA&gt; CLUE STACK
SDA&gt; EXIT

and post the data.

There should be a SYS$MANAGER:CLUE$STARTUP_node.LOG file from the first boot after the crash. Look into that file for error messages to find out, why no CLUE file might have been created.

Volker.

Volker,

Thanks for the tips.

I used a different image, this time V6.2-1H3 and got the following error:

< class='quote' style='width:400px;white-space:nowrap;overflow:auto'><code style='white-space:nowrap'>**** OpenVMS (TM) Alpha Operating System V6.2-1H3 - BUGCHECK ****
** Code=000001CC: INVEXCEPTN, Exception while above ASTDEL
** Crash CPU: 00 Primary CPU: 00 Active CPUs: 00000001
** Current Process = UCX$INET_ACP<br><br><br></code>

I'll send the dumps of both systems later.

Kinsa.<hr>

Kinsa,

if posting console output, please consider to cut & paste the data from the Putty console terminal - it's more readable - or even use the Putty logfile option to create a Putty log file.

Volker.