Real Cache Error Detected System Will Be Halted
Contents |
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Parity Errors Troubleshooting Guide Download Print Available Languages Download Options PDF (259.4 KB) View with what is parity error Adobe Reader on a variety of devices Updated:Jul 15, 2013 Document ID:116135
Parity Error Cisco
Document ID: 116135 Updated: Jul 15, 2013 Contributed by Shawn Wargo, Cisco Engineering. Download PDF Print Feedback parity error fix Related ProductsCisco Catalyst 6500 Series Switches ContentsIntroductionBackgroundSoft ErrorsHard ErrorsCommon Error MessagesProcessorRAMASICLatest AdvancementsProcessorRAMASICSoftwareMSFC IBC Reset6700 Series 'Single-Bit Parity Error' ResetRecommendationsSoft Errors (SEU)Environmental AuditLatest Firmware (Rommon)Thumb ScrewsHard Errors (Malfunction)Hardware (MTBF and
System Returned To Rom By Processor Memory Parity Error At Pc
EOL) AuditHardware DiagnosticsRelated Cisco Support Community DiscussionsIntroductionThis document describes soft and hard parity 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) parity error detected in vram in order to represent the parity (odd or even) of a small amount of computer data (typically one byte) while that 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), e
Cisco Bug: CSCsu32277 - MC28X crash because of Cache parity exception, ID_MGR_INVALID_HANDLE Last Modified Oct 01, 2011
High Correctable Ecc Error Rate Detected Cisco
Product Cisco uBR7200 Series Universal Broadband Routers Known Affected Releases 12.3(21a)BC5
Parity Error Checking
Description (partial) Symptom: Cable line card MC28X crashed with following messages in crashinfo Real cache error tm_data_parity_error detected. System will be halted. Error: primary instr cache, fields: tag, Interrupt exception, CPU signal 20, PC = 0x604E5D00 Conditions: MC28X card crash has been observed on http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116135-trouble-6500-parity-00.html UBR7246VXR with NPE-G1 running IOS 12.3(21a)BC5. uBR7246VXR NPE-G1 has also crashed because of following, followed by Line Card crash "System returned to ROM by error - a Software forced crash, PC 0x6098E23C" View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account https://quickview.cloudapps.cisco.com/quickview/bug/CSCsu32277 to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability
Post #1 of 5 (5925 views) Permalink 6500 sup720-3bxl http://www.gossamer-threads.com/lists/cisco/nsp/108171 crash Has anyone seen this reload cause before? Sounds like bad memory but the memory addresses are pretty non machine sounding some I am wondering if it is a software bug. Cache error detected! CPO_ECC (reg 26/0): 0x000000F3 CPO_CACHERI (reg 27/0): 0x84000000 CP0_CAUSE (reg 13/0): 0x00004400 Real parity error cache error detected. System will be halted. Error: Primary data cache, fields: , 1st dword Actual physical addr 0x00000000, virtual address is imprecise. Imprecise Data Parity Error Software version is: s72033_sp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI, RELEASE SOFTWARE (fc2) Thanks, John _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp real cache error archive at http://puck.nether.net/pipermail/cisco-nsp/ oles at ovh Apr26,2009,2:23PM Post #2 of 5 (5793 views) Permalink Re: 6500 sup720-3bxl crash [In reply to] Hmmm ... same today morning !? Cache error detected! CPO_ECC (reg 26/0): 0x0000009F CPO_CACHERI (reg 27/0): 0xA0000000 CP0_CAUSE (reg 13/0): 0x00000800 Real cache error detected. System will be halted. Error: Primary data cache, fields: data, Actual physical addr 0x00000000, virtual address is imprecise. Imprecise Data Parity Error Imprecise Data Parity Error Interrupt exception, CPU signal 20, PC = 0x40E7BE6C ========= Start of Crashinfo Collection (07:05:17 GMT Sun Apr 26 2009) ========= IOS (tm) s72033_sp Software (s72033_sp-IPSERVICESK9-M), Version 12.2(18)SXF14, RELEASE SOFTWARE (fc1) On Sun, Apr 26, 2009 at 01:13:05PM -0700, John van Oppen wrote: > Has anyone seen this reload cause before? Sounds like bad memory but > the memory addresses are pretty non machine sounding some I am wonderi