From: Andrew Morton <akpm@osdl.org>
To: Peter Lieverdink <peter@cc.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc2-mm1 naughtiness
Date: Wed, 28 Jan 2004 22:04:23 -0800 [thread overview]
Message-ID: <20040128220423.747ca762.akpm@osdl.org> (raw)
In-Reply-To: <1075293718.1810.4.camel@kahlua>
Peter Lieverdink <peter@cc.com.au> wrote:
>
> When I run evolution to check/send mail my kern.log gets spammed. (see
> below) Debian unstable, config attached. This didn't happen with 2.6.
> vanilla.
>
> --
> Jan 28 23:23:17 kahlua kernel: evolution 0 waking evolution: 1696 1700
> Jan 28 23:23:17 kahlua kernel: Badness in try_to_wake_up at
> kernel/sched.c:722
> Jan 28 23:23:17 kahlua kernel: Call Trace:
> Jan 28 23:23:17 kahlua kernel: [try_to_wake_up+145/448]
> try_to_wake_up+0x91/0x1c0
> Jan 28 23:23:17 kahlua kernel: [__wake_up_common+49/96]
> __wake_up_common+0x31/0x60
> Jan 28 23:23:17 kahlua kernel: [__wake_up+49/96] __wake_up+0x31/0x60
> Jan 28 23:23:17 kahlua kernel: [wake_futex+49/96] wake_futex+0x31/0x60
> Jan 28 23:23:17 kahlua kernel: [futex_wake+207/224]
> futex_wake+0xcf/0xe0
> Jan 28 23:23:17 kahlua kernel: [do_futex+121/128] do_futex+0x79/0x80
> Jan 28 23:23:17 kahlua kernel: [sys_futex+278/304]
> sys_futex+0x116/0x130
> Jan 28 23:23:17 kahlua kernel: [sys_write+89/96] sys_write+0x59/0x60
> Jan 28 23:23:17 kahlua kernel: [syscall_call+7/11] syscall_call+0x7/0xb
> Jan 28 23:23:17 kahlua kernel:
> Jan 28 23:23:17 kahlua kernel: evolution 0 waking evolution: 1696 1700
yeah, sorry, it's bogus debugging code. Please ignore it, or do a `patch
-p1 -R' of
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2.6.2-rc2-mm1/broken-out/futex-wakeup-debug.patch
prev parent reply other threads:[~2004-01-29 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 12:41 Peter Lieverdink
2004-01-28 14:05 ` Felipe Alfaro Solana
2004-01-29 6:04 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040128220423.747ca762.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cc.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®