[SUMMARY] : CPU Exception errors

From: Lee, Hank <hank.lee_at_vta.org>
Date: Fri, 04 Jun 1999 12:46:37 -0700

Thanks very much to the quick response from the following people. I was
recommended to use DECevent to gather more information:

http://www1.service.digital.com/svctools/decevent/decevent-kits.htm

I had called Compaq support and provided them information gathered with
DECevent. It turns out that one of the memory modules on this 4100 may have
become bad. The hardware tries to correct itself constantly, and it's
growing my binary.errlog pretty rapidly. I'm getting a Compaq field engineer
to come in today. In the mean time, I will follow the recommendation of
stopping binlogd to prevent the log from growing. Thanks again for your
help!


Roberto Romani [roberto.romani_at_digital.com]
Bryan Lavelle [Bryan.Lavelle_at_digital.com]
John J. Francini [francini_at_progress.com]
alan_at_nabeth.cxo.dec.com
Dr. Tom Blinn [tpb_at_doctor.zk3.dec.com]

--
Hank Lee <hank.lee_at_vta.org>
UNIX Systems Administrator
SAP Basis Administrator
Santa Clara County Transit District
> -----Original Message-----
> From:	Lee, Hank [SMTP:hank.lee_at_vta.org]
> Sent:	Friday, June 04, 1999 10:17 AM
> To:	tru64-unix-managers_at_ornl.gov
> Subject:	CPU Exception errors
> 
> Hello Managers,
> 
> I got paged this morning when /var went past 95% (thank god for that AdvFs
> feature), and I tracked down the problem to be the /var/adm/binary.errlog
> file. Using uerf, I was able to see its contents. As far as I can tell
> (the
> file was > 975MB), all the entries were similar to the following:  
> 
> ----- UNIT INFORMATION -----
> 
> UNIT CLASS                              CPU 
> 
> ********************************* ENTRY   174.
> *********************************
> 
> ----- EVENT INFORMATION -----
> 
> EVENT CLASS                             ERROR EVENT 
> OS EVENT TYPE                  100.     CPU EXCEPTION 
> SEQUENCE NUMBER                  3.
> OPERATING SYSTEM                        DEC OSF/1 
> OCCURRED/LOGGED ON                      Fri Jun  4 00:02:27 1999
> OCCURRED ON SYSTEM                      yoda
> SYSTEM ID                 x00070016
> SYSTYPE                   x00000000
> PROCESSOR COUNT                  2.
> PROCESSOR WHO LOGGED      x00000001
> 
> 
> Running a uerf -o terse showed me the following:
> 
> CPU EXCEPTION:      UNKNOWN SYS TYP  
> 
> 
> Does anyone know what might be causing it?  By the rate of growth of the
> /var/adm/binary.errlog file, I project that it started some time late last
> night. How can I fix this problem?  What do I look for to prevent it from
> happening again?  The log continues to grow, and I am catting /dev/null to
> it every few hours.  This is a Alpha 4100, 2CPU, 2GB RAM, running Tru64
> UNIX
> 4.0D.  Any points are appreciated.
> 
> 
> 
> 
> 
> --
> Hank Lee <hank.lee_at_vta.org>
> UNIX Systems Administrator
> SAP Basis Administrator
> Santa Clara County Transit District

Received on Fri Jun 04 1999 - 19:46:07 NZST