Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754575AbZLAUoJ (ORCPT ); Tue, 1 Dec 2009 15:44:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754474AbZLAUoJ (ORCPT ); Tue, 1 Dec 2009 15:44:09 -0500 Received: from mail2.racsa.co.cr ([196.40.31.26]:30505 "EHLO barracuda4.racsa.co.cr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751352AbZLAUoI (ORCPT ); Tue, 1 Dec 2009 15:44:08 -0500 X-ASG-Debug-ID: 1259700258-7bd401500000-xx1T2L X-Barracuda-URL: http://172.16.1.13:8000/cgi-bin/mark.cgi X-Barracuda-Envelope-From: osobosque@racsa.co.cr Date: Tue, 01 Dec 2009 14:44:05 -0600 (CST) From: Joseph Parmelee X-X-Sender: jparmele@bruno To: Thomas Gleixner Cc: Darren Hart , Peter Zijlstra , Ingo Molnar , Eric Dumazet , Dinakar Guniguntala , linux-kernel@vger.kernel.org X-ASG-Orig-Subj: Re: futex_cmpxchg_enabled not set in futex_init on pentium3 Subject: Re: futex_cmpxchg_enabled not set in futex_init on pentium3 In-reply-to: Message-id: References: <4B143AE8.5090608@us.ibm.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-version: 1.0 Content-type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Barracuda-Connect: UNKNOWN[172.16.7.12] X-Barracuda-Start-Time: 1259700258 X-Barracuda-Virus-Scanned: by Barracuda Spam & Virus Firewall at racsa.co.cr X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.16044 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 787 Lines: 29 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/