Hi,
On Fri, 15 Jan 2010 16:02:02 -0800, Nagaprabhanjan Bellari
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
On Sat, Jan 16, 2010 at 7:02 AM, Nagaprabhanjan Bellari
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 r
On Fri, Jan 15, 2010 at 6:02 PM, Nagaprabhanjan Bellari
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 r
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:
==
ksoftirqd/0 S
