All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Daniel J Blueman <daniel@quora.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lockup when C1E and high-resolution timers enabled
Date: Mon, 15 Jun 2015 10:01:41 +0200	[thread overview]
Message-ID: <1434355301.3719.7.camel@googlemail.com> (raw)
In-Reply-To: <20150615075437.GC4255@pd.tnic>

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 :-(



  reply	other threads:[~2015-06-15  8:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14  3:13 lockup when C1E and high-resolution timers enabled Daniel J Blueman
2015-06-14  4:39 ` Christoph Fritz
2015-06-14  7:54   ` Daniel J Blueman
2015-06-14 14:49     ` Christoph Fritz
2015-06-14 15:24       ` Daniel J Blueman
2015-06-14 23:38         ` Christoph Fritz
2015-06-14 16:47   ` Borislav Petkov
2015-06-14 23:05     ` Christoph Fritz
2015-06-15  7:54       ` Borislav Petkov
2015-06-15  8:01         ` Christoph Fritz [this message]
2015-06-15  8:10           ` Borislav Petkov
2015-07-13  7:32             ` Christoph Fritz
  -- strict thread matches above, loose matches on Subject: below --
2015-06-13 19:53 Christoph Fritz
2015-06-13 20:19 ` Heinz Diehl
2015-06-13 20:58   ` Christoph Fritz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1434355301.3719.7.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --cc=bp@alien8.de \
    --cc=daniel@quora.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.