On Tue, 2005-02-01 at 21:44 +0100, Ingo Molnar wrote: > * Lee Revell <[EMAIL PROTECTED]> wrote: > > > OK. So for application triggered tracing you need LATENCY_TRACING > > enabled, as described here: > > > > http://lkml.org/lkml/2004/10/29/312 > > correct, that too should still work fine - with the small change that > there's now a separate flag to active it: > > echo 1 > /proc/sys/kernel/trace_user_triggered # default: 0 > > it is an orthogonal mechanism to atomicity-debugging.
OK. Rereading my old mail, it looks like there were some possibly unresolved false positives with the userspace atomicity debugger. Here's one I get from alsaplayer. Would more information be required to know if this is a false positive? alsaplayer:5718 userspace BUG: scheduling in user-atomic context! [<c0102a97>] dump_stack+0x17/0x20 (20) [<c026268c>] schedule+0x6c/0x100 (24) [<c026330c>] rwsem_down_read_failed+0x9c/0x170 (48) [<c01277f5>] .text.lock.futex+0x7/0xb2 (44) [<c01276bf>] do_futex+0x4f/0x80 (28) [<c01277ba>] sys_futex+0xca/0xe0 (68) [<c0102457>] syscall_call+0x7/0xb (-4028) (gdb) bt #0 0x4117c4ec in __lll_mutex_unlock_wake () from /lib/tls/libpthread.so.0 #1 0x41179a69 in _L_mutex_unlock_26 () from /lib/tls/libpthread.so.0 #2 0x0824d3c0 in ?? () #3 0xb7ef3958 in ?? () #4 0x41179a60 in pthread_mutex_unlock () from /lib/tls/libpthread.so.0 #5 0x41179a60 in pthread_mutex_unlock () from /lib/tls/libpthread.so.0 #6 0x08057a30 in CorePlayer::Read32 (this=0x1, data=0xb7508008, samples=64) at CorePlayer.cpp:1076 #7 0x08057f89 in CorePlayer::streamer_func (arg=0x824d3c0, data=0x824cc80, size=128) at CorePlayer.cpp:1257 #8 0xb7ffcd52 in process (nframes=64, arg=0x824b258) at jack.cpp:350 #9 0xb7ef99f9 in jack_client_thread (arg=0x824bb48) at client.c:1264 #10 0x41177b63 in start_thread () from /lib/tls/libpthread.so.0 #11 0x410f0c4a in clone () from /lib/tls/libc.so.6 The backtrace is incomplete because I was unable to reproduce the problem with the debug glibc. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
