From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-26094-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 29325 invoked by alias); 5 Sep 2014 12:12:39 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Received: (qmail 29215 invoked by uid 48); 5 Sep 2014 12:12:29 -0000
From: "cedric.bail at free dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/17351] New: No hardware with functional lock elision available
Date: Fri, 05 Sep 2014 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nptl
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cedric.bail at free dot fr
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-17351-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-09/txt/msg00016.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=17351

            Bug ID: 17351
           Summary: No hardware with functional lock elision available
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: cedric.bail at free dot fr
                CC: drepper.fsp at gmail dot com

Intel has found an issue in the lock elision micro code and is rolling out a
microcode that disable it apparently for older haswell.

http://techreport.com/news/26911/errata-prompts-intel-to-disable-tsx-in-haswell-early-broadwell-cpus
http://anandtech.com/show/8376/intel-disables-tsx-instructions-erratum-found-in-haswell-haswelleep-broadwell
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e3-1200v3-spec-update.pdf

People who did not update their microcode will have some weird/random issue
most likely when using a glibc build with elision. Arch Linux has concluded it
is not a software bug and it doesn't require to change their packaging
(https://bugs.archlinux.org/task/39631).

Please advise what is the proper solution to this problem, as it potentially
affect a lot of people who wont know where the problem come from.

-- 
You are receiving this mail because:
You are on the CC list for the bug.