DS20 System Crash

From: Todd Seeleman (todds_at_wal9116.gse.upenn.edu)
Date: 01/20/05

  • Next message: Richard Zoller: "Re: Problems cloning servers with vdump-vrestore"
    Date: Thu, 20 Jan 2005 09:35:26 -0500
    
    
    

    Greetings,

            This is my last desperate attempt at solving this problem. I have a
    Compaq DS20/Tru64 5.1b system which has a history of crashing. I
    rebuilt it and put it back in service however the problem remains. I've
    appended what appeared on the console during the last crash and I've
    attached the crash-data file. Can anybody help me figure this out?

    Todd Seeleman

    *************************************************************
    Todd Seeleman, Systems Analyst
    Penn Graduate School of Education
    3440 Market Street, Rm 477 email: seeleman@gse.upenn.edu
    Philadelphia, PA. 19104-3325 phone: 215-573-8378
    *************************************************************

    login: Machine Check SYSTEM Fatal Abort
    Machine check code = 0x100000202
            Ibox Status = 0000000000000000
            Dcache Status = 0000000000000000
            Cbox Address = 0000000000000000
            Fill Syndrome 1 = 0000000000000000
            Fill Syndrome 0 = 0000000000000000
            Cbox Status = 0000000000000000
            EV6 captured status of Bcache mode = 0000000000000000
            EV6 Exception Address = ffffffff000bc320
            EV6 Interrupt Enablement and Current Processor mode =
    0000003ee0000000
            EV6 Interrupt Summary Register = 0000000200000000
            EV6 TBmiss or Fault status = 0000000000000000
            EV6 PAL Base Address = 0000000000018000
            EV6 Ibox control = fffffe0003304396
            EV6 Ibox Process_context = 0000000000000000
            O/S Summary flag = 0000000000000006
            Cchip Base Address (phys) = 00000f01a0000000
            Cchip Device Raw Interrupt Request = 2000000000000000
                DRIR Register Decode:
                    Bit 61: Error from Pchip 1
                    PCI Device Interrupt Mask = 0000000000000000
            Cchip Miscellaneous Register = 0000000100000000
                Misc Register Decode:
                    Bit 32: CChip Rev (Bit<32>)
                    Cchip Revision: 01
                    ID of CPU performing read: 00
            Pchip 0 Base Address (phys) = 00000f0180000000
            Pchip 0 Error Register = 0000000000000000
                Pchip Error Register Decode:
                    PCI Xaction Start Address = 0000000000000000
                    PCI Command: Interrupt Acknowledge
            Pchip 1 Base Address (phys) = 00000f0380000000
            Pchip 1 Error Register = 9b001ebf91800801
                Pchip Error Register Decode:
                    Bit 0: Lost Error
                    Bit 11: Correctable ECC Error
                    System Address = 000000001ebf9180
                    Command: DMA Read
                    ECC Syndrome: 9b
    panic (cpu 0): System Uncorrectable Machine Check
    syncing disks... 16227 15910 15422 15062 14699 14243 13867 13423 13093
    12613 122
    58 11824 11423 11000 10640 10212 9899 9334 9045 8996 8918 8559 8162 7755
    7518 74
    25 7071 6637 6192 5821 5427
    boot: buffers busy time limit exceeded - continuing
     5204 failed

    DUMP: blocks available: 5061290
    DUMP: blocks wanted: 165362 (partial compressed dump) [OKAY]
    DUMP: Device Disk Blocks Available
    DUMP: ------ ---------------------
    DUMP: 0x1300008 3800062 - 5061287 (of 5061288) [primary swap]
    DUMP.prom: Open: dev 0x5300003, block 1572864: RAID 1 7 0 0 0 0 0
    waiting for dra.0.0.7.1 to start...
    waiting for dra.0.0.7.1 to start...
    DUMP: Writing header... [1024 bytes at dev 0x1300008, block 5061288]
    DUMP: Writing data............................... [31MB]
    DUMP: Writing header... [1024 bytes at dev 0x1300008, block 5061288]
    DUMP: crash dump complete.
    halted CPU 1

    halted CPU 0

    halt code = 5
    HALT instruction executed
    PC = ffffffff0035a170
    P00>>>

    
    



  • Next message: Richard Zoller: "Re: Problems cloning servers with vdump-vrestore"

    Relevant Pages