[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

8962.0. "Error during CTR processing of EVT" by CSC32::BULLION () Tue Feb 25 1997 17:51

    
    
    Can someone provide some info on this decevent error log entry
    
    
    ******************************** ENTRY 2********************************
    
    
    Logging OS                        2. Digital UNIX
    System Architecture               2. Alpha
    Event sequence number            12.
    Timestamp of occurrence              24-FEB-1997 13:04:05
    Host name                            k058u1
    
    System type register      x0000000C  AlphaServer 8x00
    Number of CPUs (mpnum)    x00000004
    CPU logging event (mperr) x00000003
    
    Event validity                    1. O/S claims event is valid
    Event severity                    5. Low Priority
    Entry type                      203. Undefined Entry Type
    
                                         ** Error during CTR processing of
    EVT seg
                                         - Canonical buffer dump follows
    
    Entry# (record in file)           0.
    Canonical buff size             966.
    Canonical event size            252.
    Canonical Event-Buffer:
                        
    
              15--<-12  11--<-08  07--<-04  03--<-00   :Byte Order
     0000:    00000002  00000000  00000000  00000003   *................*
     0010:    00000202  4E454720  33317646  534F0001   *..OSFv13 GEN....*
     0020:    00000000  00000000  00000000  00000000   *................*
     0030:    000C0000  00000000  00000000  00000000   *................*
     0040:    30303530  34303331  34323230  37393931   *1997022413040500*
     0050:    00000000  00000000  00000020  20202020   *     ...........*
     0060:    00000000  00000000  31753835  306B0000   *..k058u1........*
     0070:    00000000  00000000  00000000  00000000   *................*
     0080:    33317646  534F0001  00000000  00000000   *..........OSFv13*
     0090:    000000FF  0000000C  00000000  55504320   * CPU............*
     00A0:    00000000  00000000  00000003  00000004   *................*
     00B0:    00000000  00000000  00000000  00000000   *................*
     00C0:    00000000  00000000  00000000  00000000   *................*
     00D0:    00000000  00000000  00000000  00000000   *................*
     00E0:    00000000  00000000  00000000  00000000   *................*
     00F0:              00000000  00000000  00000700   *    ............*
    
    
T.RTitleUserPersonal
Name
DateLines
8962.1me too!!GIDDAY::HAGANFri Apr 18 1997 03:1310
    Anyone help here?
    I have a customer with an almost identical footprint as .0 running
    DU V4.0 and decevent V2.3
    
    Tks for any help
    Steve Hagan
    Digital CSC
    Sydney.
    
           
8962.2Could be similar to a known problemKEIKI::WHITEMIN(2�,FWIW)Fri Apr 18 1997 21:415
    
    	If you are running LSM then there is a fix see C970122-5777
    for original IPMT case.
    
    					Bill
8962.3CFS or IPMT no. pleaseGIDDAY::HAGANMon Apr 21 1997 02:467
    Bill,
    Could you please explain what "C970122-5777" is? I tried
    to use the IPMT Case Browser and couldn't find a reference to this.
    
    Tks
    Steve Hagan
    
8962.4LocationKEIKI::WHITEMIN(2�,FWIW)Mon Apr 21 1997 21:185
    
    	Just put the seq # into comet 4.3, Comet should find it.
    http://encke.alf.dec.com/cgi/v4.3
    
    					Bill