[c-nsp] 7206VXR Crash

[Amol Sapkal]

Hi,

You should be cecking your 'show stack' output to see whether the memory
addresses below reflect in that output. I know this doesn't answer your
question 'Why', but thought would be useful information.




Regards,
Amol Sapkal


On 5/5/06, Paul Stewart <pstewart at nexicomgroup.net> wrote:
>
> Anyone know why a 7206VXR that's been working perfectly for over 2 years
> would all of a sudden do this:
>
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
> %SYS-2-NOTQ: unqueue didn't find 0 in queue 65567CE0
> -Process= "<interrupt level>", ipl= 1
> -Traceback= 0x606F814C 0x61BC6220 0x61BC8DC8 0x604EB780 0x604F2400
>
>
> Thanks,
>
> Paul Stewart
> IP Routing/Switching
> Nexicom Inc.
> http://www.nexicom.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/
>



--
Warm regards,

Amol Sapkal

-------------------------------------------------------------------
"When I'm not in my right mind, my left mind
gets pretty crowded"
-------------------------------------------------------------------