[nsp] TMS affects ssh?

[Hank Nussbacher]

Within 2 minutes of defining TMS on a Cisco 7500 (IOS 12.0(21)S4) I 
received the following errors:

May 14 13:08:49: %SCHED-3-THRASHING: Process thrashing on watched message 
event.
-Process= "SSH Process", ipl= 6, pid= 32
-Traceback= 602EDD10 602EE09C 607F6ED8 607F7404 6030F034 60309280 6031020C 
60319388 602856B4 602917C4 60A71674 60A71C14 602D837C 602D8368
May 14 13:09:18: %ALIGN-3-SPURIOUS: Spurious memory access made at 
0x60262E44 reading 0x0
May 14 13:09:18: %ALIGN-3-TRACE: -Traceback= 60262E44 60262FA4 6026332C 
602EDD10 602EE09C 607F6ED8 607F7404 6030F034
May 14 13:10:40: %SCHED-3-THRASHING: Process thrashing on watched message 
event.
-Process= "SSH Process", ipl= 6, pid= 32
-Traceback= 602EDD10 602EE09C 607F6ED8 607F7404 6030F034 60309280 6031020C 
60319388 602856B4 602917C4 60A71674 60A71C14 602D837C 602D8368
May 14 13:25:36: %SCHED-3-THRASHING: Process thrashing on watched message 
event.
-Process= "SSH Process", ipl= 6, pid= 32
-Traceback= 602EDD10 602EE09C 607F6ED8 607F7404 6030F034 60309280 6031020C 
60319388 602856B4 602917C4 60A71674 60A71C14 602D837C 602D8368

and then the errors messages stopped.

TMS background:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1834/products_feature_guide09186a0080080593.html

You turn it on via a single command:
ip cef accounting non-recursive

You can then see stats aggregated per prefix via the little known system 
files Cisco maintains at:

more system:/vfiles/tmstats_ascii

Example:

BIU-GP0#more system:/vfiles/tmstats_ascii
VERSION 1|ADDR 128.139.188.2|AGGREGATION TrafficMatrix.ascii|SYSUPTIME 
2913415|routerUTC 3261895866|NTP synchronized|DURATION 0|
p|0.0.0.0/0|2913155|20152|1469439|0|0
p|128.139.0.0/16|2913155|0|0|0|0
p|128.139.0.0/19|2913155|30063|9487597|0|0
p|128.139.34.0/24|2913155|99|7163|0|0
p|128.139.189.0/24|2913155|66787|51791047|0|0
p|128.139.193.2/32|2913155|49506|4449239|0|0
...etc...
p|132.64.0.0/13|2913155|0|0|0|0
p|132.64.0.0/15|2913155|4584017|1976531023|0|0
p|132.66.0.0/16|2913155|1458326|1099186177|0|0
p|132.66.4.0/25|2913155|13045|14695855|0|0
p|132.66.222.142/32|2913155|0|0|0|0
...etc...

I just don't see how TMS should affect ssh.  Any clues?

-Hank