On 10/29/09 6:12 PM, [email protected] wrote: > michael rodriguez: >> here is a partial kernel stack trace from when the problem is occuring. >> Is there an easy way to avoid this bottleneck? > ::: >> Call Trace: >> [<ffffffff8122d260>] 0xffffffff8122d260 >> [<ffffffff8104c479>] 0xffffffff8104c479 > ::: >> Trace; ffffffff8122d260<gr_learn_resource+40/210> >> Trace; ffffffff8104c479<remove_wait_queue+19/60> > > While I am unsure the stacktrace is reliable, it shows > gr_learn_resource() is called. Simple translating shows, > > Call Trace: > [< <gr_learn_resource+40/210> >] 0xffffffff8122d260 > [< <remove_wait_queue+19/60> >] 0xffffffff8104c479 > > And gr_learn_resource() may print some log messages. > If you have grsecurity message, could you check it?
I am using: echo w > /proc/sysrq-trigger to output a trace of currently waiting processes to console. is that a reliable method? thanks, michael ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
