linux-kernel - Re: lockup when C1E and high-resolution timers enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Jun 2015 09:54:37 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Christoph Fritz <chf.fritz@...glemail.com>
Cc:	Daniel J Blueman <daniel@...ra.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: lockup when C1E and high-resolution timers enabled

On Mon, Jun 15, 2015 at 01:05:07AM +0200, Christoph Fritz wrote:
> > > already using latest microcode:
> > > 
> > > [    0.514490] microcode: CPU0: patch_level=0x06000822
> > > [    0.514497] microcode: CPU1: patch_level=0x06000822
> > > [    0.514508] microcode: CPU2: patch_level=0x06000822
> > > [    0.514519] microcode: CPU3: patch_level=0x06000822
> > > [    0.514529] microcode: CPU4: patch_level=0x06000822
> > > [    0.514540] microcode: CPU5: patch_level=0x06000822
> > > [    0.514550] microcode: CPU6: patch_level=0x06000822
> > > [    0.514561] microcode: CPU7: patch_level=0x06000822
> > 
> > This is not the latest microcode.
> 
> > so what changed?
> 
> nice catch, my bad -- forgot to post all microcode messages.
> 
> $ dmesg | grep microcode:
> [    0.514422] microcode: CPU0: patch_level=0x06000822
> [    0.514429] microcode: CPU1: patch_level=0x06000822
> [    0.514440] microcode: CPU2: patch_level=0x06000822
> [    0.514450] microcode: CPU3: patch_level=0x06000822
> [    0.514460] microcode: CPU4: patch_level=0x06000822
> [    0.514493] microcode: CPU5: patch_level=0x06000822
> [    0.514502] microcode: CPU6: patch_level=0x06000822
> [    0.514513] microcode: CPU7: patch_level=0x06000822
> [    0.514557] microcode: Microcode Update Driver: v2.00 <tigran@...azian.fsnet.co.uk>, Peter Oruba
> [    3.909642] microcode: CPU0: new patch_level=0x06000832
> [    3.940694] microcode: CPU2: new patch_level=0x06000832
> [    3.955187] microcode: CPU4: new patch_level=0x06000832
> [    3.963403] microcode: CPU6: new patch_level=0x06000832

Just to rule out the aspect that your issue might be fixed by microcode
but that microcode needs to be loaded early, can you enable the early
microcode loader, put the microcode in initrd as described here:

Documentation/x86/early-microcode.txt

and retry?

I'm working on having it built-in too, in the case where people don't
use initrd, but that's 64-bit only for now.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/