OSF1 mcgcrc1 V5.1 1885 alpha on DS20
Hello,
On Tuesday I installed PK6 on my Alpha running 5.1A. The entire patching
process seemed to run okay, and it ended with a rebuilding of the kernel.
On reboot, the system panicked and restarted itself. I managed to boot using
the old kernel, and everything is okay now.
Here is the error log of the panic. Anyone know what to make of this? There
were other EVM alerts similar to this one, at least one per boot attempt.
Thanks,
Steven Aponte
Systems Manager
NYU SoM GCRC
-----Original Message-----
From: root_at_gcrc.med.nyu.edu [mailto:root_at_gcrc.med.nyu.edu]
Sent: Tuesday, July 12, 2005 9:47 PM
To: root_at_gcrc.med.nyu.edu
Subject: EVM ALERT [700]: System panic: panic (cpu 0): kernel memory fault
======================= Binary Error Log event =======================
EVM event name: sys.unix.binlog.op.panic._savecore.True
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by kernel components as part of the system panic
process.
Action: Contact your service provider.
======================================================================
Formatted Message:
System panic: panic (cpu 0): kernel memory fault
Event Data Items:
Event Name : sys.unix.binlog.op.panic._savecore.True
Priority : 700
PID : 379
PPID : 1
Event Id : 70
Timestamp : 12-Jul-2005 21:46:32
Host Name : mcgcrc1
User Name : root
Format : System panic: $message
Reference : cat:evmexp.cat:300
Variable Items:
subid_class (INT32) = 302
message (STRING) = "panic (cpu 0): kernel memory fault"
binlog_event (OPAQUE) = [OPAQUE VALUE: 232 bytes]
_savecore (BOOLEAN) = True
============================ Translation =============================
DECevent version: V3.3
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 60.
Timestamp of occurrence 11-JUL-2005 21:30:40
Host name mcgcrc1
System type register x00000022 Systype 34. (Regatta Family)
Number of CPUs (mpnum) x00000002
CPU logging event (mperr) x00000000
Event validity 1. O/S claims event is valid
Event severity 1. Severe Priority
Entry type 302. ASCII Panic Message Type
-1. - (minor class)
SWI Minor class 9. ASCII Message
SWI Minor sub class 1. Panic
ASCII Message panic (cpu 0): kernel memory fault
======================================================================
Received on Fri Jul 15 2005 - 20:31:44 NZST