From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Michael Geithe <warpy@gmx.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Florian Schmidt <mista.tapas@gmx.net>
Subject: Re: 2.6.10-rc1-bk4 and kernel/futex.c:542
Date: Tue, 26 Oct 2004 20:50:44 +0200 [thread overview]
Message-ID: <20041026185044.GA10894@elte.hu> (raw)
In-Reply-To: <417E3D4C.2010909@yahoo.com.au>
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >Oct 26 11:02:19 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
> Hi,
> Can you try the following patch and see what it says?
i found the bug that most likely caused the PREEMPT_REALTIME one
reported by Florian - it was a spurious wakeup caused by that patch, so
upstream is not affected.
Ingo
next prev parent reply other threads:[~2004-10-26 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 9:35 2.6.10-rc1-bk4 and kernel/futex.c:542 Michael Geithe
2004-10-26 11:31 ` Florian Schmidt
2004-10-26 11:24 ` Ingo Molnar
2004-10-26 11:38 ` Michael Geithe
2004-10-26 12:04 ` Nick Piggin
2004-10-26 18:50 ` Ingo Molnar [this message]
2004-10-26 17:21 ` Michal Schmidt
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=20041026185044.GA10894@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=nickpiggin@yahoo.com.au \
--cc=warpy@gmx.de \
/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