RE:

From: Przemyslaw Karwasiecki (karwas@xxxxxxxxxxx)
Date: Sun Sep 30 2001 - 23:46:07 GMT-3


   
John,

I agree that 2nd and 3rd crash is "parity error" related.
But the first one (Bus error) can be also caused by accessing
memory which hasn't been allocated. For instance by using
pointer which is not pointing anywhere.

And about parity: Why faulty memory was not caught at bootstrap
on Power On Self Test by BIOS? I had a faulty memory once
(nasty, because it was only faulty when router was physically warm)
and it was always causing an error on POST when I was rebooting warm
router.

Przemek

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
John Elias
Sent: Sunday, September 30, 2001 9:35 PM
To: karwas@ifxcorp.com; klean@mindspring.com; ccielab@groupstudy.com
Subject: RE:

Ken,
   My first instinct tells me that it could be bad memory because of the
parity errors. But do a show flash and make sure the IOS does not says
"invalid chechsum". Then try to download a newer IOS, it shows here that
you are running a 11.2 version, try a 12.x version.

John E.
CCIE #8150

>From: "Przemyslaw Karwasiecki" <karwas@ifxcorp.com>
>Reply-To: "Przemyslaw Karwasiecki" <karwas@ifxcorp.com>
>To: "Kenneth Leon" <klean@mindspring.com>, <ccielab@groupstudy.com>
>Subject: RE:
>Date: Sun, 30 Sep 2001 17:09:20 -0400
>
>Hello Ken,
>
>Do 'sh stack' and try:
>
>http://www.cisco.com/stack/stackdecoder.shtml
>
>
>It will try to match stack info with symbol table
>of your IOS, and then match it to known bugs database.
>
>If you are out of luck, then you possibly have
>faulty hardware :-(
>
>My .002$
>
>Przemek
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>Kenneth Leon
>Sent: Sunday, September 30, 2001 4:34 PM
>To: ccielab@groupstudy.com
>Subject:
>
>
>Hello Gents and Ladies,
>
>I have 2501 router at home lab that reloads itself.
>
>Here are three error messages generated for different instance of self
>reload.
>
>1. System restarted by bus error at PC 0x3196CB8, address 0x108E0C 233
>0930
>
>2. Parity (control reg=0x8318) Error, address: 0x133604 at 0x3185E56 (PC)
>
>3. Parity (control reg=0x8318) Error, address: 0x13B750 at 0x3196CB8 (PC
>
>
>Since the third one above the sh ver display has comment
>
>System restarted by bus error at PC 0x3196A0C, address 0x16760C.
>
>Here is the sh ver since last reboot
>=======================
>Rack03R4#sh ver
>Cisco Internetwork Operating System Software
>IOS (tm) 2500 Software (C2500-JS-L), Version 11.2(18)P, RELEASE SOFTWARE
>(fc1)
>
>Copyright (c) 1986-1999 by cisco Systems, Inc.
>Compiled Mon 12-Apr-99 14:19 by ashah
>Image text-base: 0x0304136C, data-base: 0x00001000
>
>ROM: System Bootstrap, Version 11.0(10c), SOFTWARE
>BOOTFLASH: 3000 Bootstrap Software (IGS-BOOT-R), Version 11.0(10c), RELEASE
>SOFT
>WARE (fc1)
>
>Rack03R4 uptime is 0 minutes
>System restarted by bus error at PC 0x3196CB8, address 0x13B750
>System image file is "flash:c2500-js-l.112-18.P.bin", booted via flash
>
>cisco 2500 (68030) processor (revision A) with 16384K/2048K bytes of
>memory.
>Processor board ID 01173413, with hardware revision 00000000
>Bridging software.
>SuperLAT software copyright 1990 by Meridian Technology Corp).
>X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
>TN3270 Emulation software.
>1 Ethernet/IEEE 802.3 interface(s)
>2 Serial network interface(s)
>32K bytes of non-volatile configuration memory.
>8192K bytes of processor board System flash (Read ONLY)
>
>Configuration register is 0x2102
>======================================
>It will do so while unattended. But also particularly when a save to
>running or save to start is performed.
>
>Any one have an idea what the problem might be?
>
>Making use of th ethernet and serial o ports. Running ip, ospf, bgp and ipx
>rip.
>
>Thank you for any support.
>
>Regards,
>
>Ken Leon
>**Please read:http://www.groupstudy.com/list/posting.html
>**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:10 GMT-3