? System booting after fatal error FATAL

by Andrey Ryzho » Thu, 30 Jul 1998 04:00:00

Hello All,

Ultra-2 started crashing 2 days ago with what
doesn't appear like normal nice panic. No core, anyway.
This strange message shows up in dmesg:

System booting after fatal error FATAL

SRDB bigid 4026282 doesn't tell much,
and certainly doesn't offer any workaround.

We have replaced the hardware, and don't see the
error for 20 hours now (it crashed every 5 hours before),
but after running various tests on suspected hardware,
we could not find anything wrong with it.

Any ideas are welcome.

Regards,
Andrey

Top

1. System booting after fatal error FATAL

We have a sun4u 4-slot Sun Enterprise 3000 running SunOS 5.6
Generic_105181-28 and our system apparently booted at 1:00 in the
morning with no intervention. No core file but savecore is enabled.

This is out of /var/adm/messages:

Mar 15 14:12:47 hostname /usr/dt/bin/ttsession[29629]: child (29649)
exited due to signal 1
Mar 16 01:24:55 hostname unix: cpu0: SUNW,UltraSPARC-II (upaid 10 impl
0x11 ver 0x20 clock 336 MHz)
Mar 16 01:24:55 hostname unix: cpu1: SUNW,UltraSPARC-II (upaid 14 impl
0x11 ver 0x20 clock 336 MHz)
Mar 16 01:24:55 hostname unix: cpu2: SUNW,UltraSPARC-II (upaid 15 impl
0x11 ver 0x20 clock 336 MHz)
Mar 16 01:24:55 hostname unix: ^MSunOS Release 5.6 Version
Generic_105181-28 [UNIX(R) System V Releas
e 4.0]
Mar 16 01:24:55 hostname unix: Copyright (c) 1983-1997, Sun
Microsystems, Inc.
Mar 16 01:24:55 hostname unix: mem = 4194304K (0x100000000)
Mar 16 01:24:55 hostname unix: avail mem = 4162453504
Mar 16 01:24:55 hostname unix: System booting after fatal error FATAL
Mar 16 01:24:55 hostname unix: Ethernet address = 8:0:20:89:32:4f
Mar 16 01:24:55 hostname unix: root nexus = 4-slot Sun Enterprise 3000