[c-nsp] 7206VXR crashing every day

[Rodney Dunn]

Do 'sh region' and if 0x6083E840 is a valid memory location
you have bad memory.

On Wed, Dec 14, 2005 at 10:04:41AM +0100, Vincent De Keyzer wrote:
> Thanks to all who already replied.
> 
> Yesterday we had also:
> 
> System returned to ROM by bus error at PC 0x6083E840, address 0x6083E840 at
> 13:45:14 CET Tue Dec 13 2005
> 
> Does this give more info on the most likely faulty piece of hardware? I am
> surprised to see so many different types of errors - this router seems to be
> very creative when it comes to coming up with crash causes.
> 
> Vincent
> 
> 
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> > bounces at puck.nether.net] On Behalf Of Vincent De Keyzer
> > Sent: mardi 13 décembre 2005 10:13
> > To: cisco-nsp at puck.nether.net
> > Subject: [c-nsp] 7206VXR crashing every day
> > 
> > Hello,
> > 
> > 
> > 
> > we have a 7206VXR recently installed (luckily not in production yet) that
> > crashes almost nightly.
> > 
> > 
> > 
> > Yesterday morning, we found this:
> > 
> > 
> > 
> >  GENLBBro71 uptime is 23 hours, 19 minutes
> > 
> > System returned to ROM by processor memory parity error at PC 0x6174F640,
> > address 0x0 at 10:42:12 CET Sun Dec 11 2005
> > 
> > System restarted at 10:43:47 CET Sun Dec 11 2005
> > 
> > System image file is "disk0:c7200-p-mz.122-25.S4.bin"
> > 
> > 
> > 
> > Cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of
> > memory.
> > 
> > Processor board ID 23689715
> > 
> > R7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2 Cache
> > 
> > 6 slot VXR midplane, Version 2.3
> > 
> > 
> > 
> > Last reset from watchdog reset
> > 
> > 
> > 
> > and this morning:
> > 
> > 
> > 
> > System returned to ROM by error - an Error Interrupt, PC 0x607F55C0 at
> > 23:08:23 CET Mon Dec 12 2005
> > 
> > System restarted at 23:10:06 CET Mon Dec 12 2005
> > 
> > System image file is "disk0:c7200-p-mz.122-25.S4.bin"
> > 
> > 
> > 
> > Cisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of
> > memory.
> > 
> > Processor board ID 23689715
> > 
> > R7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2 Cache
> > 
> > 6 slot VXR midplane, Version 2.3
> > 
> > 
> > 
> > Last reset from watchdog reset
> > 
> > 
> > 
> > It tried the "troubleshooting router crashes" on CCO, and it pointed me to
> > the crashinfo file, which I couldn't find; but at the end of "sh stacks"
> > it
> > says
> > 
> > 
> > 
> > ***************************************************
> > 
> > ******* Information of Last System Crash **********
> > 
> > ***************************************************
> > 
> > 
> > 
> > 
> > 
> > The last crashinfo failed to be written.
> > 
> > Please verify the exception crashinfo configuration
> > 
> > the filesytem devices, and the free space on the
> > 
> > filesystem devices.
> > 
> > Using crashinfo_FAILED.
> > 
> > 
> > 
> > %Error opening crashinfo_FAILED (File not found)
> > 
> > 
> > 
> > Does anybody know why it couldn't write the crashinfo to bootflash?
> > 
> > 
> > 
> > Vincent
> > 
> > 
> > 
> > PS: There is a bootflash:
> > 
> > 
> > 
> > GENLBBro71#sh file systems | i bootflash
> > 
> >      3407872        3996     flash     rw   bootflash:
> > 
> > GENLBBro71#
> > 
> > _______________________________________________
> > 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/
> 
> 
> _______________________________________________
> 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/