Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1165064 > unrolled thread

Re: lockup when C1E and high-resolution timers enabled

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: lockup when C1E and high-resolution timers enabled Borislav Petkov <bp@alien8.de> - 2015-06-15 10:00 +0200
    Re: lockup when C1E and high-resolution timers enabled Christoph Fritz <chf.fritz@googlemail.com> - 2015-06-15 10:10 +0200
      Re: lockup when C1E and high-resolution timers enabled Borislav Petkov <bp@alien8.de> - 2015-06-15 10:20 +0200

#1165064 — 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@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

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1165068

On Mon, 2015-06-15 at 09:54 +0200, Borislav Petkov wrote:
> 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 should have mentioned that, I already tested that, it doesn't fix
the described lockup :-(


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1165071

On Mon, Jun 15, 2015 at 10:01:41AM +0200, Christoph Fritz wrote:
> I should have mentioned that, I already tested that, it doesn't fix
> the described lockup :-(

Hmm, can you boot with

 "log_buf_len=16M ignore_loglevel debug initcall_debug apic=debug"

and send me full dmesg from that box?

Privately's fine too.

-- 
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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web