lkml.org 
[lkml]   [2004]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

* Ingo Molnar <mingo@elte.hu> wrote:

> > jackd:1507 userspace BUG: scheduling in user-atomic context!
> > [<c01069fc>] dump_stack+0x1c/0x20 (20)
> > [<c02834d0>] schedule+0x70/0x100 (24)
> > [<c010639b>] work_resched+0x6/0x17 (-8124)

> > jackd:1507 userspace BUG: scheduling in user-atomic context!
> > [<c01069fc>] dump_stack+0x1c/0x20 (20)
> > [<c02834d0>] schedule+0x70/0x100 (24)
> > [<c028465d>] down_write_mutex+0xbd/0x180 (36)
> > [<c012cbf6>] __mutex_lock+0x36/0x40 (16)
> > [<c012cc75>] _mutex_lock_irqsave+0x15/0x20 (16)
> > [<c01f1237>] tty_ldisc_try+0x17/0x50 (20)
> > [<c01f1287>] tty_ldisc_ref_wait+0x17/0xc0 (88)

> this too i'd consider a false positive, because this particular
> printout happened due to a mutex, and a mutex blockage we can consider
> involuntary blockage. [...]

i've uploaded -V0.5.15 with these two false positives fixed, could you
retry your Jackd workload and see whether any other type of scheduling
gets detected? Please also chrt the watchdog thread to a lower priority
than the main thread's priority.

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.124 / U:2.344 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site