On Sat, Jan 16, 2010 at 7:02 AM, Nagaprabhanjan Bellari <nagp.knb@xxxxxxxxx> wrote: > Hi, > > We had a problem where we were trying to debug why events/0 was taking 98% > of CPU time. I found that writing a ‘t’ to /proc/sysrq-trigger will dump the > stack traces of all processes. Unfortunately, events/0 was shown as running > and no stack trace was dumped for it: > > events/0 R running 0 3 1 4 2 > (L-TLB) <===== no stack trace for this. :-( > Can one of you tell me how to get the stack trace of a running process? Or > any other ideas/suggestions to see what events/0 is up to? try another way, such as: 1. pgrep -f events 2. notice the output...they're PIDs of all events processes. Take one, let's say "9" 3. cat /proc/9/stack should display the content of stack frame PS: make sure you enable kernel debugging option in kernel, especially CONFIG_FRAME_POINTER. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
