[lkml]   [2007]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] CFS (Completely Fair Scheduler), v2

* S.Çağlar Onur <> wrote:

> If you want me to test something else just ask please :)

yes, it would be nice to do a:

strace -o kaffine.log -f -tttTTT kaffeine

log. Because in your old log this is visible:

parent_tidptr=0xb0239bd8, {entry_number:6, base_addr:0xb0239b90,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0xb0239bd8) = 11340
futex(0x89ac218, FUTEX_WAKE, 1) = 1

we cloned a task and immediately afterwards we used futex 0x89ac218.
After that point many things happen, but the lockup itself:

futex(0x89ac218, FUTEX_WAIT, 2, NULL) = 0
futex(0x89ac218, FUTEX_WAIT, 2, NULL) = 0
futex(0x89ac218, FUTEX_WAIT, 2, NULL) = 0

is the same futex. Probably related to the same child thread? It would
be nice to also get a gdb backtrace:

gdb kaffine
<reproduce the hang>

this should give you a gdb backtrace of that kaffeine hang. Thanks,

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-04-17 18:05    [W:0.069 / U:5.120 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site