This is the mail archive of the
mailing list for the glibc project.
Re: Discrepancy between /proc/cpuinfo and glibc are suspend
- From: Allan McRae <allan at archlinux dot org>
- To: Kyle McMartin <kmcmarti at redhat dot com>, Richard Henderson <rth at twiddle dot net>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Tue, 11 Nov 2014 09:20:24 +1000
- Subject: Re: Discrepancy between /proc/cpuinfo and glibc are suspend
- Authentication-results: sourceware.org; auth=none
- References: <545B703B dot 8050803 at archlinux dot org> <545B8D5B dot 6020903 at twiddle dot net> <20141109165851 dot GB14680 at redacted dot bos dot redhat dot com>
On 10/11/14 02:58, Kyle McMartin wrote:
> On Thu, Nov 06, 2014 at 04:01:47PM +0100, Richard Henderson wrote:
>> How a microcode update could get lost, I've no idea, since I don't
>> know how that interacts with cpus that the kernel decides to power
>> down. But I can't imagine except that this is a kernel bug.
> That's quite unusual, the kernel goes to some lengths to ensure that
> microcode is reprogrammed on resume from suspend (and also from
> hibernate... see syscore_resume() in kernel/power/*.c)
> Dropping the default loglevel to debug should get some messages printed
> about which cpus got reprogrammed on resume, which would be useful
> (also, to find out if it's unique to Intel or AMD, since they're
> separate codepaths.)
For those that are interested, we have filed a kernel bug report with
all the debug details.