From: Ramon Rey Vicente <rrey@ranty.pantax.net>
To: Andrew Morton <akpm@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Peter Lieverdink <peter@cc.com.au>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: [BUG] [2.6.2-rc2-mm1] Badness in try_to_wake_up at kernel/sched.c:722 (was Re: 2.6.2-rc2-mm1)
Date: Wed, 28 Jan 2004 18:02:26 +0100 [thread overview]
Message-ID: <1075309345.1652.5.camel@debian> (raw)
In-Reply-To: <20040127233402.6f5d3497.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
I get this:
swapper 256 waking epiphany: 1261 1266
Badness in try_to_wake_up at kernel/sched.c:722
Call Trace:
[<c0118379>] try_to_wake_up+0x79/0x1c0
[<c01242c9>] update_process_times+0x29/0x40
[<c01246e0>] process_timeout+0x0/0x20
[<c01184cd>] wake_up_process+0xd/0x20
[<c01243cf>] run_timer_softirq+0xcf/0x1c0
[<c010bfd0>] handle_IRQ_event+0x30/0x60
[<c012056c>] do_softirq+0x8c/0xa0
[<c010c30f>] do_IRQ+0xef/0x120
[<c0107000>] rest_init+0x0/0x60
[<c023f588>] common_interrupt+0x18/0x20
[<c0108bc0>] default_idle+0x0/0x40
[<c0107000>] rest_init+0x0/0x60
[<c0108be3>] default_idle+0x23/0x40
[<c0108c65>] cpu_idle+0x25/0x40
[<c02ca6eb>] start_kernel+0x12b/0x140
and this:
gthumb 0 waking gthumb: 1626 1643
Badness in try_to_wake_up at kernel/sched.c:722
Call Trace:
[<c0118379>] try_to_wake_up+0x79/0x1c0
[<c0119404>] __wake_up_common+0x24/0x60
[<c011945c>] __wake_up+0x1c/0x40
[<c012e96d>] wake_futex+0x2d/0x60
[<c012ea59>] futex_wake+0xb9/0xc0
[<c012f1a7>] do_futex+0x67/0x80
[<c012f2a8>] sys_futex+0xe8/0x120
[<c023f367>] syscall_call+0x7/0xb
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
GPG public key ID 0xBEBD71D5 -> http://pgp.escomposlinux.org/
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-28 17:02 UTC|newest]
Thread overview: 25+ 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 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: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-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 ` Ramon Rey Vicente [this message]
2004-01-28 19:55 ` 2.6.2-rc2-mm1 Torrey Hoffman
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=1075309345.1652.5.camel@debian \
--to=rrey@ranty.pantax.net \
--cc=akpm@osdl.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peter@cc.com.au \
--cc=ramon.rey@hispalinux.es \
/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