The only suspicious thing so far is 100% CPU during "time-schedule" test
from LTP:
[...]
pth_str03 0 INFO : thread 0 exiting, depth=4, status=0, addr=0xf2b010
pth_str03 0 INFO : The sum of tree (breadth 4, depth 3) is 3570
pth_str03 1 PASS : Test passed
<<<execution_status>>>
duration=0 termination_type=exited termination_id=0 corefile=no
cutime=0 cstime=3
<<<test_end>>>
<<<test_start>>>
tag=time-schedule01 stime=1217504927
cmdline=" time-schedule"
[100% CPU here, reproducible]
"strace -p" kicks the test to completion, and shows plenty of
sched_yield() calls, IIRC.
--