public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cedric.bail at free dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/17351] No hardware with functional lock elision available
Date: Fri, 05 Sep 2014 17:28:00 -0000	[thread overview]
Message-ID: <bug-17351-131-9YMzBYGBYi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17351-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Cedric BAIL <cedric.bail at free dot fr> ---
Did you choose to force the microcode update on Redhat ? If not how do you
advise  user who have random crash and have absolutely no clue where to look ?

I don't know if you know, but rust has build a work around this bug to prevent
bug from happening on software build with it :
https://github.com/rocallahan/rr/commit/d389eb724a9b5f895f813600d9276e00dc063068
.

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


  reply	other threads:[~2014-09-05 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 12:12 [Bug nptl/17351] New: " cedric.bail at free dot fr
2014-09-05 17:28 ` cedric.bail at free dot fr [this message]
2014-09-05 17:42 ` [Bug nptl/17351] " carlos at redhat dot com
2014-09-06  9:19 ` cedric.bail at free dot fr
2014-09-06 17:35 ` carlos at redhat dot com
2014-09-06 19:36 ` cedric.bail at free dot fr

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=bug-17351-131-9YMzBYGBYi@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).