public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Using CONFIG_FUNCTION_TRACE
@ 2007-12-14  6:11 Darren Hart
  0 siblings, 0 replies; only message in thread
From: Darren Hart @ 2007-12-14  6:11 UTC (permalink / raw)
  To: linux-rt-users; +Cc: lkml, 

I was trying to use CONFIG_FUNCTION_TRACE with the example trace-it.c in 
linux/scripts.  On both 2.6.23.9-rt13 and 2.6.24-rc2-rt1 the system 
slower becomes less responsive (measured by typing in ssh and a serial 
console) until after a couple minutes it doesn't respond to anything 
including sysrq, requiring a power cycle.

The trace-it.c program defaults to 10 seconds of tracing, I even tried 
dropping that to 100 us in case it just added so much overhead that 10 
seconds of idle turned into minutes.  But the 100us sleep hung too.

I tested on a 4 way (2x2) opteron.  

I enabled:

CONFIG_EVENT_TRACE
CONFIG_FUNCTION_TRACE

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-12-14  6:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-14  6:11 Using CONFIG_FUNCTION_TRACE Darren Hart

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox