[Info-vax] DCL crashing bug update

[Simon Clubley]

On 2017-07-25, clair.grant at vmssoftware.com <clairgrant71 at gmail.com> wrote:
>
> I may be a little confused here but........I executed your command
> procedure and then the recall commands and got a process crash but the
> system is still up and running.  Are you saying you got a system crash?
>

I may have confused you by using the word crash to describe both
a process level crash and a system level crash. Sorry.

The direct result of running the recall commands with the test data
is just a process level crash and a register dump with the rest of
the system _apparently_ unaffected after the process was terminated.

A process level crash only was the expected result and the rest of
the system apparently continued running ok afterwards.

What was _completely_ unexpected was that I later rebooted the system
for some reason or other and the system crashed during the reboot.

The reboot command is the standard one in the SYSTEM login.com:

$  REBOOT       == "@SYS$SYSTEM:SHUTDOWN 0 SHUTDOWN NO YES LATER YES NONE"

I don't normally reboot this system; I normally just do a straight boot
and then shutdown VMS when I've finished. As such, I don't know if there
is a bug in the version of FreeAXP I am using which can cause a crash
during a reboot.

So far, I have only ever seen a system crash during the reboot process
after I have run my recall tests since the last boot and I only see
those infrequently. The examples I posted earlier are from crashes which
occurred after using the reboot command while logged into SYSTEM.

Given the infrequent and random nature of the system level crashes,
I am going to assume this is merely some emulator artifact until
someone reports they have caused a system crash while rebooting their
physical Alpha system.

> BTW: I am on an i2 running 8.4-2L1.
>

So it affects IA64 as well. Thanks for the report.

Given that it affects IA64, should I notify HPE or is this something
you can pass along to them ?

I'm not fully sure what would be an appropriate email address to
use to make sure HPE's VMS Engineering got the problem report.

It's not a security issue so using the HPE security reporting
mechanism would be inappropriate.

Thanks,

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world