Catalyst 6509 - IOS - CPU High and eventually crashed

Unanswered Question
Jan 20th, 2010
User Badges:


  Recently one of our Cat 6509 started giving the below mentioned error message and eventually crashed.

"No memory availale for asychronous request"

Could some one throw some light and I am happy to give any additional info. on this.

Thanks in advance,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Yudong Wu Wed, 01/20/2010 - 14:03
User Badges:
  • Gold, 750 points or more

Can you provide crash file from both SP and RP if they are available?

If SUP run out of memory, it could cause the crash as well. In general, shortage of memory could be a memory leaking issue.

So, reviewing crash file to see what caused the crash. If it was memory, you can monitor the memory usage to see if you can find a process which kept using more and more memory. You can open a TAC case to let tac engineer to help you .

krishnakumarr Wed, 01/20/2010 - 18:18
User Badges:


Can you provide blow mentioned logs

show tech


krishna kumar

krishnakumarr Thu, 01/21/2010 - 07:24
User Badges:


The Current running IOS is defered release kindly upgrade the image to latest version

Hope this will resolve the issue

latest Image



krishna kumar

subra4u Thu, 01/21/2010 - 08:40
User Badges:

Thanks for the Input.

Will try doing the upgrade but I am wondering why the problem started after 2 years in production.

Thanks in advance


Yudong Wu Thu, 01/21/2010 - 22:01
User Badges:
  • Gold, 750 points or more

SUP crashed after error message "pm failed to send port admin change notification", there were some traceback in the log as well.

There was only 400K memory left and they were fragmented as wel when the issue happened.

-SP-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from 0x40298EFC, alignment 8
Pool: Processor  Free: 431936  Cause: Memory fragmentation   <<<<<<<<
Alternate Pool: None  Free: 0  Cause: No Alternate pool

-Process= "LTL MGR cc", ipl= 0, pid= 226
-Traceback= 40280AB4 402866EC 40298F04 405C8000 405C84D8 405C85F8 405CDEA0 405CE770 405CCA4C

It could be a bug. If you would like to find out what the bug might be, you can open a TAC case for help.


This Discussion