From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 61245138825 for ; Tue, 11 Nov 2014 05:40:28 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6569EE08AD; Tue, 11 Nov 2014 05:40:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EFCBBE083D for ; Tue, 11 Nov 2014 05:40:19 +0000 (UTC) Received: from [192.168.1.100] (mobile-internet-5d6a49-115.dhcp.inet.fi [93.106.73.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ssuominen) by smtp.gentoo.org (Postfix) with ESMTPSA id 66E04340020 for ; Tue, 11 Nov 2014 05:40:17 +0000 (UTC) Message-ID: <5461A0D9.2090108@gentoo.org> Date: Tue, 11 Nov 2014 07:38:33 +0200 From: Samuli Suominen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] glibc-2.20 and intel microcode References: <2152323.9pxBxE1bey@gentoo> In-Reply-To: <2152323.9pxBxE1bey@gentoo> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: 739aff11-2107-4310-bc4a-2d3759685ea5 X-Archives-Hash: 2c097f107f3aabf3bf0bce58126a8280 On 11/11/14 05:49, microcai@fedoraproject.org wrote: > 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. > > > See, http://bugs.gentoo.org/show_bug.cgi?id=528712 It's likely you are hitting a kernel bug