From: microcai@fedoraproject.org
To: gentoo-user@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-user] glibc-2.20 and intel microcode
Date: Tue, 11 Nov 2014 11:49:17 +0800 [thread overview]
Message-ID: <2152323.9pxBxE1bey@gentoo> (raw)
I've finnally detected the root cause of glibc-2.20 broken my system:
glibc-2.20 start using TLX instruction which is disabled by microcode update.
disabling microcode update brings my system back to live!
so, there is either a bug in CPU , nor glibc has borken CPU feature detection.
next reply other threads:[~2014-11-11 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 3:49 microcai [this message]
2014-11-11 5:38 ` [gentoo-user] glibc-2.20 and intel microcode Samuli Suominen
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=2152323.9pxBxE1bey@gentoo \
--to=microcai@fedoraproject.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-user@lists.gentoo.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