[c-nsp] Spurious Memory Access and Traceback

Oliver Boehmer (oboehmer) oboehmer at cisco.com
Mon Aug 9 10:57:35 EDT 2004


rwcrowe at comcast.net <> wrote on Monday, August 09, 2004 4:21 PM:

> Looking through some logs I see a 2620 logged the following error
> messages: 
> 
> Jul  9 19:32:01.716 EST: %ALIGN-3-SPURIOUS: Spurious memory access
> made at 0x805834D4 reading 0x8 
> Jul  9 19:32:01.716 EST: %ALIGN-3-TRACE: -Traceback= 805834D4
> 80393650 803D5820 803D497C 803D5820 803E6F74 8048B5A0 8048EAE8 

> This is an edge 2620 running 12.3(9), 32MB DRAM, 16MB Flash, nothing
> special running on it. It did not reboot from the error, just curious
> on the internals of this error. From what I understand on tracebacks,
> this is just an internal memory error in IOS. Maybe tried to access a
> memory address in use or a non-existant one. Any input ? --   

Unless the alignment errors happen in the forwarding path (i.e. for
every packet), you might as well ignore them.. Your errors were caused
while IOS tried to display an ACL (show ip access-list, or similar),
points to CSCee66832, fixed in 12.3(9a).

	oli

P.S: We issued a software advisory against 12.3(9), you might want to
move to 12.3(9a).. 



More information about the cisco-nsp mailing list