So here's my problem:
Performance, especially when switching/launching/killing apps is awful,
and dmesg spits out:
Badness in try_to_wake_up at kernel/sched.c:722
Call Trace:
[<c011aac5>] try_to_wake_up+0x91/0x1c9
[<c0126fea>] schedule_timeout+0xb5/0xb7
[<c013aa84>] __get_free_pages+0x1f/0x41
[<c011bae1>] __wake_up_common+0x31/0x50
[<c011bb32>] __wake_up+0x32/0x57
[<c01311ef>] wake_futex+0x30/0x5b
[<c01314a8>] futex_requeue+0x1c3/0x1c8
[<c0131a03>] do_futex+0x48/0x80
[<c0131b47>] sys_futex+0x10c/0x124
[<c0311f13>] syscall_call+0x7/0xb
I'm attaching my .config.
--
Adam Koszela <[email protected]>
On Wed, 2004-01-28 at 18:55, Adam Koszela wrote:
> So here's my problem:
> Performance, especially when switching/launching/killing apps is awful,
> and dmesg spits out:
>
> Badness in try_to_wake_up at kernel/sched.c:722
> Call Trace:
> [<c011aac5>] try_to_wake_up+0x91/0x1c9
C'mon people, this has been reported at least four times ;-)
I'm sure Andrew is looking into it right now.
> On Wed, 2004-01-28 at 18:55, Adam Koszela wrote:
> > So here's my problem:
> > Performance, especially when switching/launching/killing apps is awful,
> > and dmesg spits out:
> >
> > Badness in try_to_wake_up at kernel/sched.c:722
> > Call Trace:
> > [<c011aac5>] try_to_wake_up+0x91/0x1c9
>
> C'mon people, this has been reported at least four times ;-)
> I'm sure Andrew is looking into it right now.
I get the same message myself when using xmms.
AFAICS this is not much to worry about. It is only a new debug message which did not exist in 2.6.2-rc2 or earlier.
Daniel Andersen