From: Daniel Andersen <kernel-list@majorstua.net>
To: Alexander Hoogerhuis <alexh@ihatent.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-rc2-mm1 (Breakage?)
Date: Fri, 30 Jan 2004 02:08:39 +0100 [thread overview]
Message-ID: <20040130020839.0775de2e.kernel-list@majorstua.net> (raw)
In-Reply-To: <87r7xiba2k.fsf@lapper.ihatent.com>
> > > Hello, Andrew, I've switched from 2.6.2-rc1-mm1 to 2.6.2-rc1-mm1, and I've
> > > encountered this:
> > >
> > [snip]
> >
> > Decided to build my first kernel with preempt since the early 2.5 days. I'm
> > seeing the same warnings in 2.6.2-rc2-mm1.
> >
> > gkrellm 0 waking gkrellm: 897 1485
> > Badness in try_to_wake_up at kernel/sched.c:722
> > Call Trace:
> > [<c011a6a7>] try_to_wake_up+0x97/0x1d0
> > [<c011b0b0>] __wake_up_common+0x30/0x60
> > [<c011b109>] __wake_up+0x29/0x50
> > [<c0131f1b>] wake_futex+0x2b/0x70
> > [<c013259a>] do_futex+0x3fa/0x6e0
> > [<c011d9d0>] copy_process+0x7b0/0x10a0
> > [<c011e3a9>] do_fork+0xe9/0x179
> > [<c011a142>] schedule+0x1d2/0x640
> > [<c0132988>] sys_futex+0x108/0x130
> > [<c03e1b9e>] sysenter_past_esp+0x43/0x65
> >
> > Every five seconds. This is when it reads the sensor information from /sys, I
> > think. And during boot, similar messages to those already reported (from
> > kern.log this time).
> >
As Zephaniah E. Hull suggested earlier, the message will disappear by reverting this patch:
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
Daniel Andersen
next prev parent reply other threads:[~2004-01-30 1:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 7:34 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 7:55 ` 2.6.2-rc2-mm1 Mike Fedyk
2004-01-28 8:18 ` ALSA noise (was: Re: 2.6.2-rc2-mm1) Joshua Kwan
2004-01-28 8:36 ` 2.6.2-rc2-mm1 Han Boetes
2004-01-30 2:51 ` 2.6.2-rc2-mm1 Adrian Bunk
2004-01-30 6:00 ` 2.6.2-rc2-mm1 Han Boetes
2004-02-04 8:22 ` 2.6: Voyager requires SMP? Adrian Bunk
2004-02-04 17:04 ` James Bottomley
2004-01-28 9:41 ` 2.6.2-rc2-mm1 Christoph Hellwig
2004-01-28 19:38 ` 2.6.2-rc2-mm1 David S. Miller
2004-01-28 12:08 ` 2.6.2-rc2-mm1 Ramon Rey Vicente
2004-01-28 12:08 ` 2.6.2-rc2-mm1 Ralf Hildebrandt
2004-01-28 12:13 ` 2.6.2-rc2-mm1 (Breakage?) David Martínez Moreno
2004-01-28 12:25 ` Alistair John Strachan
2004-01-28 13:33 ` Fix sleep_on abuse in XFS, Was: " Christoph Hellwig
2004-01-28 14:28 ` David Woodhouse
2004-01-28 15:02 ` Christoph Hellwig
2004-01-29 6:20 ` Nathan Scott
2004-01-29 23:37 ` Alexander Hoogerhuis
2004-01-30 1:08 ` Daniel Andersen [this message]
2004-01-28 12:17 ` 2.6.2-rc2-mm1 Nikita Danilov
2004-01-28 13:08 ` 2.6.2-rc2-mm1 Stian Jordet
2004-01-28 15:32 ` 2.6.2-rc2-mm1 Randy.Dunlap
2004-01-28 21:25 ` 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 17:02 ` [BUG] [2.6.2-rc2-mm1] Badness in try_to_wake_up at kernel/sched.c:722 (was Re: 2.6.2-rc2-mm1) Ramon Rey Vicente
2004-01-28 19:55 ` 2.6.2-rc2-mm1 Torrey Hoffman
2004-01-28 20:04 ` 2.6.2-rc2-mm1 Olaf Hering
2004-01-29 0:34 ` 2.6.2-rc2-mm1 Adrian Bunk
2004-01-29 16:15 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 10:48 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 11:02 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 11:18 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
2004-01-30 11:20 ` 2.6.2-rc2-mm1 Vojtech Pavlik
2004-01-30 12:41 ` 2.6.2-rc2-mm1 Zephaniah E. Hull
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=20040130020839.0775de2e.kernel-list@majorstua.net \
--to=kernel-list@majorstua.net \
--cc=alexh@ihatent.com \
--cc=daniel@majorstua.net \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome