Processor Memory Parity Error At
Contents |
7200 Series RoutersTroubleshoot and AlertsTroubleshooting TechNotes Processor Memory Parity Errors (PMPEs) Download Print Available Languages Download Options PDF (85.5 KB) View with Adobe Reader on a variety of devices what is parity error ePub (74.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, parity error cisco or Windows Phone Mobi (Kindle) (72.7 KB) View on Kindle device or Kindle app on multiple devices Updated:May 25, 2016 parity error fix Document ID:6345 ContentsIntroductionPrerequisitesRequirementsComponents UsedConventionsIdentify a Parity ErrorSoft Versus Hard Parity ErrorsIsolate the ProblemCisco 4500 and 4700 PlatformsRoute/Switch Processor (RSP), Network Processing Engine (NPE), and Route Processor (RP) PlatformsParity Error in DRAM or bcm-4-cor_ecc_high SRAM (MEMD)Parity Error Pulled from SRAMVersatile Interface ProcessorRecommended ActionsInformation to Collect if You Open a TAC Service RequestRelated Information Introduction This document explains what causes parity errors on Cisco routers, and how to troubleshoot them. Prerequisites Requirements Cisco recommends that you have knowledge of how to troubleshoot router crashes. Refer to Troubleshooting Router Crashes for more information. Components Used This document is not restricted to specific
Real Cache Error Detected. System Will Be Halted
software and hardware versions. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Identify a Parity Error Memory parity errors occur in MultiChannel Interface Processor (MIPS)-based processor products such as: Cisco 4500/4700 Series Routers Cisco 7500 Series Routers (RSP1, RSP2, RSP4, RSP8, VIP2-10, VIP2-15, VIP2-20, VIP2-40, VIP2-50) Cisco 7000 Series Routers (RSP 7000) Cisco 7200 Series Routers (NPE-100, NPE-150, NPE-175, NPE-200, NPE-225, NPE-300) Cisco 12000 Series Internet Router Here are some messages, which are all related to the detection of bad parity somewhere in the system (the list is not exhaustive, but contains the most common messages): In the show version command output: System restarted by processor memory parity error at PC 0x6014F7C0, address 0x0 or System restarted by shared memory parity error at PC 0x60130F40 If you have the output of a show version command from your Cisco device, you can use Cisco CLI Analyzerto
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Parity Errors Troubleshooting Guide Download Print Available Languages Download Options PDF (259.4 KB) View with Adobe Reader on a variety of devices
Parity Error Detection
Updated:Jul 15, 2013 Document ID:116135 Document ID: 116135 Updated: Jul 15, 2013 Contributed parity error definition by Shawn Wargo, Cisco Engineering. Download PDF Print Feedback Related ProductsCisco Catalyst 6500 Series Switches ContentsIntroductionBackgroundSoft ErrorsHard ErrorsCommon parity bit Error MessagesProcessorRAMASICLatest AdvancementsProcessorRAMASICSoftwareMSFC IBC Reset6700 Series 'Single-Bit Parity Error' ResetRecommendationsSoft Errors (SEU)Environmental AuditLatest Firmware (Rommon)Thumb ScrewsHard Errors (Malfunction)Hardware (MTBF and EOL) AuditHardware DiagnosticsRelated Cisco Support Community DiscussionsIntroductionThis document describes soft and hard parity http://www.cisco.com/c/en/us/support/docs/routers/7200-series-routers/6345-crashes-pmpe.html errors, explains common error messages, and recommends methods that help you avoid or minimize parity errors. Recent improvements in hardware and software design reduce parity problems as well. BackgroundWhat is a processor or memory parity error?Parity checking is the storage of an extra binary digit (bit) in order to represent the parity (odd or even) of a small amount of computer data (typically one byte) while that http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116135-trouble-6500-parity-00.html data is stored in memory. The parity value calculated from the stored data is then compared to the final parity value. If these two values differ, this indicates a data error, and at least one bit must have been changed due to data corruption.Within a computer system, electrical or magnetic interference from internal or external causes can cause a single bit of memory to spontaneously flip to the opposite state. This event makes the original data bits invalid and is known as a parity error.Such memory errors, if undetected, may have undetectable and inconsequential results or may cause permanent corruption of stored data or a machine crash.There are many causes of memory parity errors, which are classified as either soft parity errors or hard parity errors.Soft ErrorsMost parity errors are caused by electrostatic or magnetic-related environmental conditions.The majority of single-event errors in memory chips are caused by background radiation (such as neutrons from cosmic rays), electromagnetic interference (EMI), or electrostatic discharge (ESD). These events may randomly change the electrical state of one or more memory cells or may interfere with the circuitry used to read and write memory cells.Known as soft parity errors, these events are typical
PC 0x62BAD188dovzz2010-04-06 07:21:00 Hello, gentlemen. Recently, there was a problem with the router 3845. Perezagruzhaetsya He periodically. After restarting: System returned to ROM by processor memory parity http://forum.windowsfaq.ru/archiveen/index.php/t-131232.html error at PC 0x62BAD188, address 0x0 at 00:12:44 EKTSUM Tue Apr June 2010. (This last example). I can not figure out why. Tried different versions of operating systems, now stands c3845-advipservicesk9-mz.124-25c.bin. Does not help. Possible configuration as that affects, but it seems like there is nothing abnormal in it. After performing the show region: Start End Size (b) Class Media Name 0x0FFFFE00 0x0FFFFFFF parity error 512 Iomem R / W BCM region 0x2D300000 0x2FFFFDFF 47,185,408 Iomem R / W iomem 0x60000000 0x6D2FFFFF 221249536 Local R / W main 0x60010E10 0x62BD95FB 45,909,996 IText R / O main: text 0x62BE1620 0x6498E55F 31117120 IData R / W main: data 0x6498E560 0x64E5ECFF 5,048,224 IBss R / W main: bss 0x64E5ED00 0x6D2FFFFF 139072256 Local R / W main: heap 0x70000000 0x7FFFFFFB 268435452 Local processor memory parity R / W Main memory 1 0x7FFFFFFC 0x7FFFFFFF 4 Local R / W Protected region 0x80000000 0x8D2FFFFF 221249536 Local R / W main :( main_k0) 0xA0000000 0xAD2FFFFF 221249536 Local R / W main :( main_k1) 0xC0000000 0xDFFFFFFF 536870912 Local R / W Main memory 2 I note that the memory like as always (if I have never missed) is flagged 0x60010E10 0x62BD95FB 45,909,996 IText R / O main: text - this area. And how could not restart once per day may not occur and 3 times per day. Cisco site but no concrete decisions, only recommendations. Help please, can someone tell me what the problem is. dovzz2010-04-06 07:35:15 Incidentally after show stack (from past reboots): Cache error detected! CPO_ECC (reg 26/0): 0x40000000 CPO_CACHERI (reg 27/0): 0x04001D60 CPO_CACHERD (reg 27/1): 0x04000340 CPO_CCHEDPA (reg 27/3): 0x10A20000 Real cache error detected. System will be halted. 0 spurious cache errors were previously detected. Real cache error detected. System will be halted. Cache error detected! CPO_ECC (reg 26/0): 0x40000000 CPO_CACHERI (reg 27/0): 0x04001D60 CPO_CACHERD (reg 27/1): 0x84000340 CPO_CCHEDPA (reg 27/3): 0x10A20000 Real cache error detected. System will be halted. 0 spurious