05-30-2013 07:38 AM - edited 03-07-2019 01:38 PM
Hi,
I got various error about memory allocation failure. I user sup720 with IOS 12.2(18)SXD7b. Should it be software issuue?
-Process= "Pool Manager", ipl= 0, pid= 6
-Traceback= 2037F160 20380CCC 20315D0C 2031A18C 2031A2D0
May 29 18:38:13.603 BKK: %SYS-DFC10-2-MALLOCFAIL: Memory allocation of 4256 bytes failed from 0x20315D04, alignment 8
Pool: Processor Free: 1546776 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
-Process= "Pool Manager", ipl= 0, pid= 6
-Traceback= 2037F160 20380CCC 20315D0C 2031A18C 2031A2D0
May 29 18:38:43.623 BKK: %SYS-DFC10-2-MALLOCFAIL: Memory allocation of 4256 bytes failed from 0x20315D04, alignment 8
Pool: Processor Free: 1546776 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
Show memory stat
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 43B45DC0 407577152 43745160 363831992 359998216 249113808
I/O 8000000 67108864 12978696 54130168 46441696 53383032
Show process memory sorted
Total: 407577152, Used: 43753120, Free: 363824032
PID TTY Allocated Freed Holding Getbufs Retbufs Process
0 0 59520848 9800224 46245760 0 0 *Init*
122 0 15560648 14424592 1254264 0 0 HWIF QoS Process
5 0 4107381056 4122593288 1225992 2933855080 2946473036 Pool Manager
0 0 3579103824 3576103048 1220032 12214668 0 *Dead*
159 0 958424 37554736 863624 0 0 FM core
141 0 623960 2040 595664 0 0 CEF process
06-02-2013 10:20 AM
Has this sup720 been running for a while and then this happened? Or did this error happen shortly after the sup720 booted up?
I see that there are traceback messages in your output. Traceback error messages are almost always an indication that there is a software problem rather than a hardware problem.
HTH
Rick
06-02-2013 03:38 PM
If you open a TAC Case, the first thing they'll ask you is post the output to the "sh module". This'll help determine WHY you are still using a very ancient IOS version, a significant part of the TAC were still in their diapers.
06-02-2013 08:19 PM
Hi Rojer
The error logs are generic indicating MALLOC failure, as its a old code there could be any bug hitting and could be causing the memory leak. so recommend you to upgrade to the latest code.
# show mem debug leak
#sh memory debug leaks chunks
- These commands will help you identify in case any memory leak is there.
Thanks & Regards
Sandeep.
06-02-2013 09:55 PM
Hi all,
Thanks for sharing information and command. The command look like are not available for 12.2(18)SXD release. I noticed the error identify about DFC10 so i will try to reseat card first. I understand the IOS is quiet old (since 2006), but need to upgrade flash memory (current 64MB).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide