linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kevin.b.stanton@intel.com, Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>
Subject: Re: commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073 seems to break with intel-ucode 20180425
Date: Mon, 14 May 2018 14:15:44 +0200	[thread overview]
Message-ID: <CAEJqkgh2C_t+pq72Y8uOLYk7nCCtFRnrt1La0hsJL2taa4k35g@mail.gmail.com> (raw)
In-Reply-To: <20180514072355.GB12198@hirez.programming.kicks-ass.net>

2018-05-14 9:23 GMT+02:00 Peter Zijlstra <peterz@infradead.org>:
> On Sat, May 12, 2018 at 12:55:35PM +0200, Gabriel C wrote:
>> Hi Peter,
>>
>> after updating ucode to 20180425 on my laptop I always hit the
>> 'TSC_DEADLINE disabled' error and so early microcode update from
>> inird breaks.
>>
>> Also I'm able to late load the microcode from command line but
>> not from initrd.
>>
>> Going back to ucode 20180312 make things work again.
>>
>> I've tested on latest 4.16.8 kernel for now.
>>
>> lscpu output:
>
> Please provide /proc/cpuinfo (a single cpu is sufficient) for both
> firmwares.
>
> lscpu (whatever that is) lacks useful information, like the microcode
> version.

ucode 20180312:

http://ftp.frugalware.org/pub/other/people/crazy/ucode/dmesg-ucode-20180312
http://ftp.frugalware.org/pub/other/people/crazy/ucode/cpuinfo-ucode-20180312

ucode 20180425:

http://ftp.frugalware.org/pub/other/people/crazy/ucode/dmesg-ucode-20180425
http://ftp.frugalware.org/pub/other/people/crazy/ucode/cpuinfo-ucode-20180425

Loading microcode manually is working

http://ftp.frugalware.org/pub/other/people/crazy/ucode/reload-late-working-ucode-20180425

Also initramfs is made with dracut and his early microcode option.

Please let me know if you need more infos or want me to test different kernels.

Best Regards,

Gabriel C

  reply	other threads:[~2018-05-14 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 10:55 commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073 seems to break with intel-ucode 20180425 Gabriel C
2018-05-14  7:23 ` Peter Zijlstra
2018-05-14 12:15   ` Gabriel C [this message]
2018-05-14 12:58     ` Peter Zijlstra
2018-05-14 14:16       ` Gabriel C

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=CAEJqkgh2C_t+pq72Y8uOLYk7nCCtFRnrt1La0hsJL2taa4k35g@mail.gmail.com \
    --to=nix.or.die@gmail.com \
    --cc=kevin.b.stanton@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).