[c-nsp] 7200 Bus error crash and strange disk error

Sun Oct 10 10:21:56 EDT 2004

I went through the output interpreter's candidate bugs and none of the 
apply. I read the suggested document "Troubleshooting Bus Error Crashes".
Given that "System returned to ROM by bus error at PC 0x80007D98, 
address 0x7DE8" and the show region output, the address 0x7DE8 does not 
fall within the range of a valid virtual address. Indicating a software 
failure.

The document recommends copying the output of show stacks or show 
technical-support into the output interpreter. Which I did, and I got 
the same error notification as I did before. Pointing to the same 
"Troubleshooting Bus Error Crashes" document and the same likely bug 
candidates. (Circular reference)

I don't know where to go from here. Any suggestion anyone? How do I stop 
it from crashing? Another upgrade?

-Osama

Luan Nguyen wrote:

>i don't think the two errors related.  use the output interpreter and
>go from there
>https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl?locale=en
>pasting show context come back with some sort of memory problem which
>seems to correspond to the show region.
>
>STACK DECODE NOTIFICATIONS (if any)
>
>ERROR: This router was last restarted by a bus error.
>The system encounters a bus error when the processor tries to access a
>memory location
>that either does not exist (a software error) or does not respond
>properly (a hardware
>problem).
>TRY THIS: A Stack decode will occur (see below), and will assume this
>is a software
>error. If the result is not accurate, try pasting an enabled 'show tech-support'
>into Output Interpreter to confirm if the cause is software or hardware related.
>NOTE: The enabled 'show tech-support' must contain the 'show region'
>command. 'show
>region' was first included in 'show tech-support' in IOS 12.0(9). Use
>the Troubleshooting
>Bus Error Crashes document to assist in troubleshooting
>
>The failure was caused by a software defect.Note that this is a bus error crash
>and can also be hardware related.Please read Troubleshooting Bus Error Crashes
>for more details,especially if no bug from the list seems to match your issue.
>
>The stack trace decoded symbols are:
>	std_console_putc
>
>Possible bug matches are listed below.  Bugs with a score of .90 or more
>are the most likely candidates:
>
>
>Score Bugid  Status  Fixed In  Duplicate  Title  
>0.89 CSCec38312 R 12.3(7)XI 12.0(27)SV 12.3(5.5)T 12.3(5.2)
>12.0(26.3)S CSCea07154 6PE: problem in initializing the TFIB
>
>0.78 CSCee88746 A 12.3(7)XI 12.0(27)SV 12.3(5.5)T 12.3(5.2)
>12.0(26.3)S CSCea07154 ggsn is displaying gprs charging cdr-option
>sgsn-plmn configuratio
>
>0.62 CSCin65445 V  None CMFB:%IPPHONE-6-UNREGISTER_ABNORMAL msg found
>when 7935 is restarted
>
>0.62 CSCee54226 D  CSCee26662 Memory corruption when AAA DNIS map configured 
>
>0.62 CSCee79396 D  CSCdy87265 CPUHOG at net_input 
>
>0.62 CSCef25361 O 12.2(15)BX 12.2(15)ZN 12.2(15)BZ 12.2(15)BW
>12.2(13.3)B 12.2(13.7)T1 12.2(13.1)PI6a CSCea07154 Nextports start
>dropping calls after working fine for some days
>
>0.62 CSCeb45793 D  CSCea07154 c2650xm resarted by a SegV exception 
>
>0.62 CSCed65912 C  CSCea07154 %ERR-1-GT64010: Fatal error, PCI Master abort 
>
>Luan
>
>On Sun, 10 Oct 2004 14:21:02 +0300, Osama I. Dosary <oid at saudi.net.sa> wrote:
>
>>Hello,
>>We have a 7200 that keeps on crashing, giving the error "System returned
>>to ROM by bus error at PC 0x80007D98, address 0x7DE8 at 12:13:17 AST Sun
>>Oct 10 2004".
>>I couldn't find anything on the web or Cisco's site and tools to explain
>>it.
>>
>>We were running IOS 12.2-7a, when it a crashed a couple times and
>>couldn't find any reason, I thought there might be an undocumented bug,
>>so I set it to load 12.3-5d if it crashes again. It crashed again and
>>took on the new IOS (12.3-5a.) And it also crashed twice when running
>>the 12.3-5d.
>>
>>I also noticed this error message in the loggs:
>>"Oct 10 14:00:57: %PCMCIAFS-5-DIBERR: PCMCIA disk 0 is formatted from a
>>different router or PC. A format in this router is required before an
>>image can be booted from this device" Yet it still boots from this disk.
>>
>>By the way, we haven't changed anything on the router. It has been the
>>same IOS and disk for the past year.
>>
>>Any clues as to what is going on here? Might these two errors be related?
>>
>>(I've attached the show ver, show context and show region.)
>>
>>thanks,
>>Osama I. Al-Dosary
>>
>>show ver:
>>System returned to ROM by bus error at PC 0x80007D98, address 0x7DE8 at
>>12:13:17 AST Sun Oct 10 2004
>>System restarted at 12:15:47 AST Sun Oct 10 2004
>>System image file is "sup-slot0:/c7200-js-mz.123-5d.bin"
>>
>>cisco 7206VXR (NPE300) processor (revision B) with 122880K/40960K bytes
>>of memory.
>>Processor board ID 16073835
>>R7000 CPU at 262MHz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
>>6 slot VXR midplane, Version 2.0
>>
>>Last reset from power-on
>>Channelized E1, Version 1.0.
>>Bridging software.
>>X.25 software, Version 3.0.0.
>>SuperLAT software (copyright 1990 by Meridian Technology Corp).
>>TN3270 Emulation software.
>>Primary Rate ISDN software, Version 1.1.
>>
>>PCI bus mb0_mb1 has 200 bandwidth points
>>PCI bus mb2 has 0 bandwidth points
>>
>>1 FastEthernet/IEEE 802.3 interface(s)
>>5 Serial network interface(s)
>>8 Channelized E1/PRI port(s)
>>125K bytes of non-volatile configuration memory.
>>
>>46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
>>4096K bytes of Flash internal SIMM (Sector size 256K).
>>Configuration register is 0x102
>>
>>show context:
>>
>>System was restarted by bus error at PC 0x80007D98, address 0x7DE8 at
>>12:13:17 AST Sun Oct 10 2004
>>7200 Software (C7200-JS-M), Version 12.3(5d), RELEASE SOFTWARE (fc1)
>>Compiled Tue 08-Jun-04 20:09 by kellythw
>>Image text-base: 0x60008AF4, data-base: 0x61FB6000
>>
>>Stack trace from system failure:
>>FP: 0x80007D28, RA: 0x80007D98
>>FP: 0x80007D98, RA: 0x60798574
>>
>>Fault History Buffer:
>>7200 Software (C7200-JS-M), Version 12.3(5d), RELEASE SOFTWARE (fc1)
>>Compiled Tue 08-Jun-04 20:09 by kellythw
>>Signal = 10, Code = 0x8, Uptime 03:32:28
>>$0 : 00000000, AT : 63150000, v0 : 622A0000, v1 : 634E0000
>>a0 : 634A5FA0, a1 : 000073DB, a2 : 0000001C, a3 : BE83F48C
>>t0 : 634D3D70, t1 : 00000013, t2 : A0000000, t3 : 00000000
>>t4 : 000C2869, t5 : 001373DB, t6 : 60000000, t7 : 634D98A8
>>s0 : C69B85AC, s1 : 634A84F0, s2 : 70576CAD, s3 : 622A0000
>>s4 : 622A0000, s5 : 622A0000, s6 : 634B0000, s7 : 634B0000
>>t8 : 0D0D0D0D, t9 : 634D8574, k0 : 3040D001, k1 : BE840244
>>gp : 63159308, sp : 80007D28, s8 : 00000000, ra : 80007D40
>>EPC : 80007D98, SREG : 3400FF03, Cause : 00000008
>>Error EPC : AFC9BF07, BadVaddr : 00007DE8
>>
>>sh region:
>>
>>Region Manager:
>>
>>     Start         End     Size(b)  Class  Media  Name
>>0x07800000  0x07FFFFFF     8388608  Iomem  R/W    iomem2
>>0x20000000  0x21FFFFFF    33554432  Iomem  R/W    iomem
>>0x57800000  0x57FFFFFF     8388608  Iomem  R/W    iomem2:(iomem2_cwt)
>>0x60000000  0x677FFFFF   125829120  Local  R/W    main
>>0x60008AF4  0x61FB57EF    33213692  IText  R/O    main:text
>>0x61FB6000  0x63152C1F    18467872  IData  R/W    main:data
>>0x63152C20  0x6364FA5F     5230144  IBss   R/W    main:bss
>>0x6364FA60  0x677FFFFF    68879776  Local  R/W    main:heap
>>0x70000000  0x71FFFFFF    33554432  Iomem  R/W    iomem:(iomem_cwt)
>>0x80000000  0x877FFFFF   125829120  Local  R/W    main:(main_k0)
>>0xA0000000  0xA77FFFFF   125829120  Local  R/W    main:(main_k1)
>>
>>_______________________________________________
>>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-nsp
>>archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>>