[c-nsp] NPE-G1 with 12.2(25)S reload

[Rodney Dunn]

Do that and attach the crashinfo files to
the case.

If you look at the file you can see the
command logs just before the crash and
you can correlate the timestamps to
see if anything was changing such as
a link flap, etc...

On Fri, Feb 18, 2005 at 04:43:14PM -0600, Brian Feeny wrote:
> 
> Yes I got 2 crashfiles, it had reloaded once early this morning as  
> well.  Nothing that I can tell was going on that may have caused this.
> I can open a TAC case with the sh stack.
> 
> Brian
> 
> On Feb 18, 2005, at 4:36 PM, Rodney Dunn wrote:
> 
> > Did it save a crashinfo file in bootflash?
> >
> > If so look at it and see if anything was
> > going on just about the time of the crash.
> >
> > Otherwise you need to give the 'sh stack'
> > so someone with access to the code
> > can decode it.
> >
> > Rodney
> >
> > On Fri, Feb 18, 2005 at 04:30:15PM -0600, Brian Feeny wrote:
> >>
> >> Thanks for the heads up.
> >> We are not compiling ACL's on that box.
> >> However, I did install some QoS the other day, policy maps, and thats  
> >>  really the only change that has been made.I am searching Bug  
> >> Navigator now to see if there are any hits on QoS  reload bugs in  
> >> this version of IOS.
> >>
> >> Brian
> >> On Feb 18, 2005, at 4:11 PM, ¨©ukasz Bromirski wrote:
> >>> Brian Feeny wrote:>> I realize I should be on S2 and I am working on  
> >>> that right now,>> but I want to make sure that the problem I had  
> >>> isn't possibly in>> S2 as well.  Here is what I got:>> Cisco IOS  
> >>> Software, 7200 Software (C7200-K91P-M), Version 12.2(25)S,>> System  
> >>> returned to ROM by error - a Software forced crash, PC>> 0x6083F730  
> >>> at 21:10:30 UTC Fri Feb 18 2005>> Is anyone aware of what this could  
> >>> be?  I am not running RPF.>> If you by chance were resequencing the  
> >>> ACLs (compiled), You hit the> same bug I hit few days ago - just  
> >>> look in the archives. I don't> know for sure if it's fixed in S2  
> >>> that I'm running now, but> resequencing and other various operations  
> >>> doesn't seem to trigger it.>> And, of course, You should get the  
> >>> newer version. crashinfo can be> used to further debug the cause of  
> >>> the problem, and You can always> open a case on TAC.>> --  > this  
> >>> space was intentionally left blank    |            ¨©ukasz  >  
> >>> Bromirski> you can insert your favourite quote here   !
> >   |         > lukasz:bromirski,net>  
> > _______________________________________________> 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/------------------------------------------------------------------- 
> > ----- ------Brian Feeny, CCIE #8036, CISSP    	e:  
> > signal at shhreve.netNetwork Engineer           			p:  
> > 318.213.4709ShreveNet Inc.             			f: 318.221.6612
> >>
> >> _______________________________________________cisco-nsp mailing list  
> >>   
> >> cisco-nsp at puck.nether.nethttps://puck.nether.net/mailman/listinfo/ 
> >> cisco-nsparchive at http://puck.nether.net/pipermail/cisco-nsp/
> >>
> ------------------------------------------------------------------------ 
> ------
> Brian Feeny, CCIE #8036, CISSP    	e: signal at shreve.net
> Network Engineer           			p: 318.213.4709
> ShreveNet Inc.             			f: 318.221.6612