From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Cc: Horacio de Oro <hgdeoro@yahoo.com>, mingo@redhat.com
Subject: Re: [2.6.1-mm2] Badness in futex_wait at kernel/futex.c:509
Date: Thu, 15 Jan 2004 09:46:45 +1100 [thread overview]
Message-ID: <20040115013723.33EF22C21C@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 13 Jan 2004 22:36:12 -0800." <20040113223612.4fe709d9.akpm@osdl.org>
In message <20040113223612.4fe709d9.akpm@osdl.org> you write:
> Horacio de Oro <hgdeoro@yahoo.com> wrote:
> >
> > Hi!
> >
> > This happen every time I switch from X to console:
> >
> > Badness in futex_wait at kernel/futex.c:509
> > Call Trace:
> > [futex_wait+434/448] futex_wait+0x1b2/0x1c0
> > [default_wake_function+0/32] default_wake_function+0x0/0x20
> > [default_wake_function+0/32] default_wake_function+0x0/0x20
> > [do_futex+112/128] do_futex+0x70/0x80
> > [sys_futex+292/320] sys_futex+0x124/0x140
> > [syscall_call+7/11] syscall_call+0x7/0xb
> >
>
> /* A spurious wakeup should never happen. */
> WARN_ON(!signal_pending(current));
>
> (looks at Rusty)
You were the one who said spurious wakeups shouldn't happen 8)
This implies that the console code decided to do wake_up_process() on
us. We returned -EINTR to userspace, but there was no signal, which
is odd.
Anyone have any ideas *why*?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2004-01-15 1:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 5:42 Horacio de Oro
2004-01-14 6:36 ` Andrew Morton
2004-01-14 22:46 ` Rusty Russell [this message]
2004-01-15 2:06 ` Andrew Morton
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=20040115013723.33EF22C21C@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®