[nsp] new bug on cat6k?

[Stephen J. Wilcox]

I like to lead the way :)

One annoying thing is why doesnt the stack decoder actually spit out any of the 
decoding! Would be nice to know process we're in to try to work out what the 
problem is

==========================================================================
STACK DECODE NOTIFICATIONS (if any)
==========================================================================

The failure was caused by a software defect.




On Thu, 31 Jul 2003, Robert A. Hayden wrote:

> Same here.  12.1.19E1 has been pretty good to me (about 40 6500s on the
> campus are running it), but I haven't had any crashes or had to do any
> reloads.
> 
> Is there a BugID on this yet?
> 
> On Thu, 31 Jul 2003, Nicholas Ianelli wrote:
> 
> > We are running that release (12.1(19)E1) on some of our production gear. We
> > have not run into any problems with it so far. Uptime is around 1 week.
> >
> > Guess I better go knock on some wood or something.
> >
> > - Nick
> >
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net
> > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jared Mauch
> > Sent: Thursday, July 31, 2003 9:28 AM
> > To: Stephen J. Wilcox
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [nsp] new bug on cat6k?
> >
> > 	I've not seen any issues with 12.1(19)E1 yet.
> >
> > 	It's the software we went to after the PSIRT
> > bugs.
> >
> > 	I have seen that if you reload a router running 12.1(19)E1
> > it can sometimes crash while doing the reload.  We still have a tac
> > case open on that one ...
> >
> > 	- Jared
> >
> > On Thu, Jul 31, 2003 at 02:09:57PM +0100, Stephen J. Wilcox wrote:
> > > hello!
> > >
> > > cat6k running 12.1(19)E1 :
> > > IOS (tm) c6sup1_rp Software (c6sup1_rp-PS-M), Version 12.1(19)E1, EARLY
> > DEPLOYMENT RELEASE SOFTWARE (fc2)
> > > cisco WS-C6006 (R5000) processor (revision 2.0) with 114688K/16384K bytes
> > of
> > > memory.
> > >
> > > crashed with
> > >
> > > SP by error - a Software forced crash, PC 0x6011E3BC
> > >
> > > -Traceback= 6011E3BC 6011C6A8 60205130 60211664 60203BAC 60205D80 60206020
> >
> > > 60207AF8 600F5834 600F5820
> > >
> > > Unexpected exception, CPU signal 23, PC = 0x6011E3BC
> > >
> > > $0 : 00000000, AT : 614F0000, v0 : 60640000, v1 : 4436EBE8
> > > a0 : 61731F74, a1 : 614ECAE8, a2 : 00000000, a3 : 60800000
> > > t0 : 00000028, t1 : 3401FF01, t2 : 34018100, t3 : FFFF00FF
> > > t4 : 60122AA0, t5 : 00000000, t6 : 620C13B0, t7 : 0098812D
> > > s0 : 00000000, s1 : 00000000, s2 : 620F2460, s3 : 60807B94
> > > s4 : 60808074, s5 : 0000000B, s6 : 00000001, s7 : 00000000
> > > t8 : 000060E2, t9 : 00000000, k0 : 3041C001, k1 : 30410000
> > > gp : 614F47E0, sp : 620C1408, s8 : 00000000, ra : 6011C6A8
> > > EPC  : 6011E3BC, ErrorEPC : 00808600, SREG     : 3401FF03
> > > MDLO : 66666673, MDHI     : 00000032, BadVaddr : 82BE1FB7
> > > Cause 00000024 (Code 0x9): Breakpoint exception
> > >
> > >
> > > according to bug toolkit/output interpreter etc all the bugs are multicast
> >
> > > related but none fits what i have (they are wrong platform or are for
> > things I
> > > am not running - specifically multicast, ppoe, gre, ipsec, car, nat etc)
> > >
> > > is this a non-public bug or somethin new and exciting?
> > >
> > > Steve
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > http://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
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>