mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Parmelee <jparmele@wildbear.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Darren Hart <dvhltc@us.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Dinakar Guniguntala <dino@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: futex_cmpxchg_enabled not set in futex_init on pentium3
Date: Tue, 01 Dec 2009 14:44:05 -0600 (CST)	[thread overview]
Message-ID: <alpine.LNX.2.00.0912011428350.855@bruno> (raw)
In-Reply-To: <alpine.LFD.2.00.0911302307440.24119@localhost.localdomain>




On Mon, 30 Nov 2009, Thomas Gleixner wrote:

> Could you also please do a quick check in which kernel version this
> got introduced ?
>

I tested by reinstalling the old glibc-2.9, rebooting test kernels, and
rerunning offending mutex tests from the glibc-2.9 test suite.  I needed to
reinstall the old glibc because the new glibc-2.11 wants kernels in the
2.6.31 series or later.

The problem first appears in 2.6.31 and persists through the current
2.6.31.6.

The problem does not appear in 2.6.29 and 2.6.30 versions.



Yours,

Joseph

  parent reply	other threads:[~2009-12-01 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 17:46 Joseph Parmelee
2009-11-30 21:36 ` Darren Hart
2009-11-30 22:26   ` Thomas Gleixner
2009-12-01  4:27     ` Joseph Parmelee
2009-12-01 20:44     ` Joseph Parmelee [this message]
2009-12-01 21:39       ` Thomas Gleixner
2009-12-01 21:52         ` Joseph Parmelee
2009-12-01 22:55           ` H. Peter Anvin
2009-12-02  0:53             ` Joseph Parmelee
2009-12-02  1:40               ` H. Peter Anvin
2009-12-05 23:24         ` Joseph Parmelee
2009-12-05  0:46     ` Joseph Parmelee

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=alpine.LNX.2.00.0912011428350.855@bruno \
    --to=jparmele@wildbear.com \
    --cc=dino@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®