In the last episode (Jul 19), Doug Barton said: > On Sun, 18 Jul 2010, Dan Nelson wrote: > > You can also use dtrace to get a count of callouts and their time spent. > > Run this for a few seconds then hit ^C: > > Okey dokey, here you go: > > http://people.freebsd.org/~dougb/normal-dtrace.txt > http://people.freebsd.org/~dougb/bad-dtrace.txt
I don't see any real difference between those two runs, so maybe it's not a callout eating your CPU. How about running this for a few seconds, which will print all the stack traces seen during the sampling period: dtrace -n 'profile:::profile-276hz { @pc[stack()]=count(); }' On an otherwise idle system, you should see most of the counts in cpu_idle, with the remainder clustered in whatever code is eating your CPU. -- Dan Nelson dnel...@allantgroup.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"