Cisco Cisco IGX 8400 Modules Fehlerbehebungsanleitung

Seite von 2
            3015 109A = program counter
            7         = stack frame type (access error)
            0 08      = vector offset (8 = bus error)
            3032 FDC0 = effective address
            0101      = special status word
            0001      = writeback 3 status
            0001      = writeback 2 status
            0001      = writeback 1 status
            A422 C388 = fault address
            3032 FDBC = writeback 3 address
            0000 000A = writeback 3 data
The most important information in this stack is the location of the abort (program counter) and the address
that cannot be accessed, which is the fault address.
You can check the Nmemmap.h file to determine if the fault address is a valid hardware register. In this
example, the address 0xA422C388 is not a valid hardware register, so the software attempts to access an
invalid address. One example of a hardware failure is the failure of one of the parallel port registers to
respond. The base address of PAR_PTS is 0xA0000000.
You can use the program counter to determine the location that the software attempts to access. The expected
assembly instruction is to move to a memory location that an address register specifies. This might not be the
instruction at the program counter because the processor reads instructions ahead of the execution of the
instructions. It has a pipelined architecture.
This instruction sequence generates a 1M3 abort error when an attempt is made to read from address 1:
        cmp.w   #1234,Abort_Now
        BNE     CK_PSOS
        move.l  #1,A0
        move.l  (A0),D0             ;generate a bus error
Related Information
Cisco WAN Switching Solutions − Cisco Documentation
• 
Guide to New Names and Colors for WAN Switching Products
• 
Downloads − WAN Switching Software (
 registered customers only
)
• 
Technical Support & Documentation − Cisco Systems
• 
Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Feb 02, 2007
Document ID: 10796