Re: lockup when C1E and high-resolution timers enabled

Christoph Fritz
2015-06-14T23:05:19Z

> > 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@aivazian.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