From: Alexander Hoogerhuis <alexh@ihatent.com>
To: s0348365@sms.ed.ac.uk
Cc: linux-kernel@vger.kernel.org,
"David Martínez Moreno" <ender@debian.org>,
"Andrew Morton" <akpm@osdl.org>,
linux-mm@kvack.org
Subject: Re: 2.6.2-rc2-mm1 (Breakage?)
Date: 30 Jan 2004 00:37:39 +0100 [thread overview]
Message-ID: <87r7xiba2k.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <200401281225.37234.s0348365@sms.ed.ac.uk>
Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> On Wednesday 28 January 2004 12:13, David Martínez Moreno wrote:
> > El Miércoles, 28 de Enero de 2004 08:34, Andrew Morton escribió:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2
> > >.6 .2-rc2-mm1/
> > >
> > >
> > > - From now on, -mm kernels will contain the latest contents of:
> > >
> > > Linus's tree: linus.patch
> > > The ACPI tree: acpi.patch
> > > Vojtech's tree: input.patch
> > > Jeff's tree: netdev.patch
> > > The ALSA tree: alsa.patch
> > >
> > > If anyone has any more external trees which need similar treatment,
> > > please let me know.
> > >
> > > - Various fixes. Nothing stands out.
> >
> > 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).
>
I'm getting this from many different sources not doing polling in
/sys:
Jan 30 00:31:30 lapper kernel: mozilla-bin 0 waking mozilla-bin: 10599 10641
Jan 30 00:31:30 lapper kernel: Badness in try_to_wake_up at kernel/sched.c:722
Jan 30 00:31:30 lapper kernel: Call Trace:
Jan 30 00:31:30 lapper kernel: [try_to_wake_up+145/457] try_to_wake_up+0x91/0x1c9
Jan 30 00:31:30 lapper kernel: [<c011e9d5>] try_to_wake_up+0x91/0x1c9
Jan 30 00:31:30 lapper kernel: [__wake_up_common+49/80] __wake_up_common+0x31/0x50
Jan 30 00:31:30 lapper kernel: [<c011fa0f>] __wake_up_common+0x31/0x50
Jan 30 00:31:30 lapper kernel: [__wake_up+50/87] __wake_up+0x32/0x57
Jan 30 00:31:30 lapper kernel: [<c011fa60>] __wake_up+0x32/0x57
Jan 30 00:31:30 lapper kernel: [wake_futex+49/91] wake_futex+0x31/0x5b
Jan 30 00:31:30 lapper kernel: [<c0135f3d>] wake_futex+0x31/0x5b
Jan 30 00:31:30 lapper kernel: [futex_wake+209/223] futex_wake+0xd1/0xdf
Jan 30 00:31:30 lapper kernel: [<c0136038>] futex_wake+0xd1/0xdf
Jan 30 00:31:30 lapper kernel: [do_futex+123/125] do_futex+0x7b/0x7d
Jan 30 00:31:30 lapper kernel: [<c01367de>] do_futex+0x7b/0x7d
Jan 30 00:31:30 lapper kernel: [sys_futex+278/303] sys_futex+0x116/0x12f
Jan 30 00:31:30 lapper kernel: [<c01368f6>] sys_futex+0x116/0x12f
Jan 30 00:31:30 lapper kernel: [sysenter_past_esp+67/101] sysenter_past_esp+0x43/0x65
Jan 30 00:31:30 lapper kernel: [<c029131e>] sysenter_past_esp+0x43/0x65
Jan 30 00:31:30 lapper kernel:
And:
Jan 30 00:32:26 lapper kernel: emacs 256 waking mozilla-bin: 10599 10641
Jan 30 00:32:26 lapper kernel: Badness in try_to_wake_up at kernel/sched.c:722
Jan 30 00:32:26 lapper kernel: Call Trace:
Jan 30 00:32:26 lapper kernel: [try_to_wake_up+145/457] try_to_wake_up+0x91/0x1c9
Jan 30 00:32:26 lapper kernel: [<c011e9d5>] try_to_wake_up+0x91/0x1c9
Jan 30 00:32:26 lapper kernel: [process_timeout+0/12] process_timeout+0x0/0xc
Jan 30 00:32:26 lapper kernel: [<c012b605>] process_timeout+0x0/0xc
Jan 30 00:32:26 lapper kernel: [wake_up_process+30/34] wake_up_process+0x1e/0x22
Jan 30 00:32:26 lapper kernel: [<c011eb2b>] wake_up_process+0x1e/0x22
Jan 30 00:32:26 lapper kernel: [run_timer_softirq+212/456] run_timer_softirq+0xd4/0x1c8
Jan 30 00:32:26 lapper kernel: [<c012b34e>] run_timer_softirq+0xd4/0x1c8
Jan 30 00:32:26 lapper kernel: [do_softirq+152/154] do_softirq+0x98/0x9a
Jan 30 00:32:26 lapper kernel: [<c0127138>] do_softirq+0x98/0x9a
Jan 30 00:32:26 lapper kernel: [do_IRQ+271/324] do_IRQ+0x10f/0x144
Jan 30 00:32:26 lapper kernel: [<c010c9e2>] do_IRQ+0x10f/0x144
Jan 30 00:32:26 lapper kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Jan 30 00:32:26 lapper kernel: [<c0291d58>] common_interrupt+0x18/0x20
Jan 30 00:32:26 lapper kernel:
With acpid running, which actually does some polling in /sys, the
machine will go out like a light within two seconds logging into gnome
and getting the acpi-based power-applet running.
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Hoogerhuis <alexh@ihatent.com>
To: s0348365@sms.ed.ac.uk
Cc: linux-kernel@vger.kernel.org,
"David Martínez Moreno" <ender@debian.org>,
"Andrew Morton" <akpm@osdl.org>,
linux-mm@kvack.org
Subject: Re: 2.6.2-rc2-mm1 (Breakage?)
Date: 30 Jan 2004 00:37:39 +0100 [thread overview]
Message-ID: <87r7xiba2k.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <200401281225.37234.s0348365@sms.ed.ac.uk>
Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> On Wednesday 28 January 2004 12:13, David Martinez Moreno wrote:
> > El Miercoles, 28 de Enero de 2004 08:34, Andrew Morton escribio:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.2-rc2/2
> > >.6 .2-rc2-mm1/
> > >
> > >
> > > - From now on, -mm kernels will contain the latest contents of:
> > >
> > > Linus's tree: linus.patch
> > > The ACPI tree: acpi.patch
> > > Vojtech's tree: input.patch
> > > Jeff's tree: netdev.patch
> > > The ALSA tree: alsa.patch
> > >
> > > If anyone has any more external trees which need similar treatment,
> > > please let me know.
> > >
> > > - Various fixes. Nothing stands out.
> >
> > 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).
>
I'm getting this from many different sources not doing polling in
/sys:
Jan 30 00:31:30 lapper kernel: mozilla-bin 0 waking mozilla-bin: 10599 10641
Jan 30 00:31:30 lapper kernel: Badness in try_to_wake_up at kernel/sched.c:722
Jan 30 00:31:30 lapper kernel: Call Trace:
Jan 30 00:31:30 lapper kernel: [try_to_wake_up+145/457] try_to_wake_up+0x91/0x1c9
Jan 30 00:31:30 lapper kernel: [<c011e9d5>] try_to_wake_up+0x91/0x1c9
Jan 30 00:31:30 lapper kernel: [__wake_up_common+49/80] __wake_up_common+0x31/0x50
Jan 30 00:31:30 lapper kernel: [<c011fa0f>] __wake_up_common+0x31/0x50
Jan 30 00:31:30 lapper kernel: [__wake_up+50/87] __wake_up+0x32/0x57
Jan 30 00:31:30 lapper kernel: [<c011fa60>] __wake_up+0x32/0x57
Jan 30 00:31:30 lapper kernel: [wake_futex+49/91] wake_futex+0x31/0x5b
Jan 30 00:31:30 lapper kernel: [<c0135f3d>] wake_futex+0x31/0x5b
Jan 30 00:31:30 lapper kernel: [futex_wake+209/223] futex_wake+0xd1/0xdf
Jan 30 00:31:30 lapper kernel: [<c0136038>] futex_wake+0xd1/0xdf
Jan 30 00:31:30 lapper kernel: [do_futex+123/125] do_futex+0x7b/0x7d
Jan 30 00:31:30 lapper kernel: [<c01367de>] do_futex+0x7b/0x7d
Jan 30 00:31:30 lapper kernel: [sys_futex+278/303] sys_futex+0x116/0x12f
Jan 30 00:31:30 lapper kernel: [<c01368f6>] sys_futex+0x116/0x12f
Jan 30 00:31:30 lapper kernel: [sysenter_past_esp+67/101] sysenter_past_esp+0x43/0x65
Jan 30 00:31:30 lapper kernel: [<c029131e>] sysenter_past_esp+0x43/0x65
Jan 30 00:31:30 lapper kernel:
And:
Jan 30 00:32:26 lapper kernel: emacs 256 waking mozilla-bin: 10599 10641
Jan 30 00:32:26 lapper kernel: Badness in try_to_wake_up at kernel/sched.c:722
Jan 30 00:32:26 lapper kernel: Call Trace:
Jan 30 00:32:26 lapper kernel: [try_to_wake_up+145/457] try_to_wake_up+0x91/0x1c9
Jan 30 00:32:26 lapper kernel: [<c011e9d5>] try_to_wake_up+0x91/0x1c9
Jan 30 00:32:26 lapper kernel: [process_timeout+0/12] process_timeout+0x0/0xc
Jan 30 00:32:26 lapper kernel: [<c012b605>] process_timeout+0x0/0xc
Jan 30 00:32:26 lapper kernel: [wake_up_process+30/34] wake_up_process+0x1e/0x22
Jan 30 00:32:26 lapper kernel: [<c011eb2b>] wake_up_process+0x1e/0x22
Jan 30 00:32:26 lapper kernel: [run_timer_softirq+212/456] run_timer_softirq+0xd4/0x1c8
Jan 30 00:32:26 lapper kernel: [<c012b34e>] run_timer_softirq+0xd4/0x1c8
Jan 30 00:32:26 lapper kernel: [do_softirq+152/154] do_softirq+0x98/0x9a
Jan 30 00:32:26 lapper kernel: [<c0127138>] do_softirq+0x98/0x9a
Jan 30 00:32:26 lapper kernel: [do_IRQ+271/324] do_IRQ+0x10f/0x144
Jan 30 00:32:26 lapper kernel: [<c010c9e2>] do_IRQ+0x10f/0x144
Jan 30 00:32:26 lapper kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Jan 30 00:32:26 lapper kernel: [<c0291d58>] common_interrupt+0x18/0x20
Jan 30 00:32:26 lapper kernel:
With acpid running, which actually does some polling in /sys, the
machine will go out like a light within two seconds logging into gnome
and getting the acpi-based power-applet running.
mvh,
A
--
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-29 23:38 UTC|newest]
Thread overview: 52+ 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:34 ` 2.6.2-rc2-mm1 Andrew Morton
2004-01-28 7:55 ` 2.6.2-rc2-mm1 Mike Fedyk
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 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 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:13 ` David Martínez Moreno
2004-01-28 12:25 ` Alistair John Strachan
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 13:33 ` Christoph Hellwig
2004-01-28 14:28 ` David Woodhouse
2004-01-28 14:28 ` David Woodhouse
2004-01-28 15:02 ` Christoph Hellwig
2004-01-28 15:02 ` Christoph Hellwig
2004-01-29 6:20 ` Nathan Scott
2004-01-29 6:20 ` Nathan Scott
2004-01-29 23:37 ` Alexander Hoogerhuis [this message]
2004-01-29 23:37 ` Alexander Hoogerhuis
2004-01-30 1:08 ` Daniel Andersen
2004-01-28 12:17 ` 2.6.2-rc2-mm1 Nikita Danilov
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 13:08 ` 2.6.2-rc2-mm1 Stian Jordet
2004-01-28 15:32 ` 2.6.2-rc2-mm1 Randy.Dunlap
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 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 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: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 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=87r7xiba2k.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=akpm@osdl.org \
--cc=ender@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=s0348365@sms.ed.ac.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.