Random Crash/Reboot/Bluescreen of 4.0d clone

From: Robert A. Hayden <rhayden_at_means.net>
Date: Thu, 03 Sep 1998 09:55:04 -0500 (CDT)

We are experiencing a problem with 3 identically configured Alpha clones.
It appears they suddently halt and generate a bluescreen. At this point,
the only recovery method seems to be a reboot via the reset button.

Below is what the screen says when it comes up. You can also find a
digital picture of it at http://rhayden.means.net/bluescreen.jpg.

Looking at the syslogs produces no information.

Aspen systems, where we purchased the machines from, said simply "looks
like software problem to us" and kindly but firmly told us to stick it and
that our $50k purchase didn't mean anything to them...not that I'm bitter
or anything. *grumble*

Anyways, any ideas at all would be appreciated.

Thanks

-- Robert

=-=-=-=-=-=
Robert Hayden rhayden_at_means.net UIN: 3937211
IP Network Administrator http://rhayden.means.net
MEANS Telcom (612) 230-4416

-----

Alpha boot: available memory from 0x7ea000 to 0x7ffe000
Digital UNIX V4.0d (Rev. 878); Thu Jul 16 11:25:24 CDT 1998
physical memory = 128.0 megabytes
available memory = 127.0 megabytes
using 484 buffers containing 3.87 megabytes of memory
Digital AlphaPC 164LX 533 MHz
Firmware revision 5.1
PALcode: Digital UNIX version 1.22
pci0 at nexus
trio0 at pci0 slot 6
trio0: S3 Trio64V+ (SVGA) Plug-N-Play 2.0 Mb
tu0: DECchip 21143: Revision 3.0
tu0: autonegotiation capable device
tu0: at pci0 slot 7
tuo: DEC TULIP (10/100) Ethernet Interface, hardware address:
00-00-F8-1F-FB-9A
tu0: autonegotiation off: selecting 10baseT (UTP) port: half-duplex
isa0 at pci0
gpc0 at isa0
ace0 at isa0
ace1 at isa0
lp0 at isa0
forcing interrupt in t1_do_command
fdi0 at isa0
Received on Thu Sep 03 1998 - 14:52:04 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT