Folks, it's me again with beagleboard RT problem. I recompiled the kernel and got some statistics on locks, but I'm not sure how to interpret it. Searching on google didn't help, probably, not asking right question. Here are stats from /proc after running cyclictest. If you could take a look at it, it would be great. Thanks, Maksym. On 15 June 2010 09:34, Maksym Parkachov <lazy.gopher@xxxxxxxxx> wrote: > Hi folks, > > thanks for all suggestions. > I'll try with lock validation and see if I could come with more details. > > Thanks, > Maksym. > > On 14 June 2010 13:27, Sven-Thorsten Dietrich > <thebigcorporation@xxxxxxxxx> wrote: >> On Mon, 2010-06-14 at 13:05 +0200, John Kacur wrote: >>> >>> On Mon, 14 Jun 2010, Sujit K M wrote: >>> >>> > > CONFIG_PREEMPT_RCU=y >> %< >>> His problem is not with the config. >>> -- >> >> Nope - the config is just fine. >> >> Turn on the lock validator and >> recompile the Kernel. >> >> Then repeat the test that produced the latency spike. >> >> If that doesn't produce any locking issues, >> turn on latency tracing and repeat. >> >>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >> >> >
Attachment:
lock_stat.gz
Description: GNU Zip compressed data
Attachment:
lockdep_stats.gz
Description: GNU Zip compressed data
Attachment:
lockdep.gz
Description: GNU Zip compressed data
