[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiqPHc=BzSYO4N=awucq0td3s9VuBkct=m-B_xZVCgzBg@mail.gmail.com>
Date: Wed, 15 Jan 2020 11:49:42 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jari Ruusu <jari.ruusu@...il.com>, Ashok Raj <ashok.raj@...el.com>
Cc: Andy Lutomirski <luto@...capital.net>,
Luis Chamberlain <mcgrof@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Fenghua Yu <fenghua.yu@...el.com>, johannes.berg@...el.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Hans de Goede <hdegoede@...hat.com>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: Fix built-in early-load Intel microcode alignment
On Wed, Jan 15, 2020 at 11:15 AM Jari Ruusu <jari.ruusu@...il.com> wrote:
>
> No problem at microcode load time.
> Hard lockup after 1-2 days of use.
That is "interesting".
However, the most likely cause is that you have a borderline dodgy
system, and the microcode update then just triggers a pre-existing
problem.
Possibly because of how newer microcode will have things like "VERW
now flushes CPU buffers" etc.
But it might be worth it if the intel people could check up with their
microcode people on this anyway - if there is _one_ report of "my
system locks up with newer ucode", that's one thing. But if Jari isn't
alone...
I don't know who the right intel person would be. There's a couple of
Intel people on the cc (and I added one more at random), can you try
to see if somebody would be aware of or interested in that "ucode
problems with i5-7200U (fam 6 model 142 step 9 pf 0x80)"
Linus
Powered by blists - more mailing lists