Messages in this thread | | | Date | Fri, 19 Feb 2016 12:50:45 +0200 | Subject | Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check | From | Andy Shevchenko <> |
| |
On Fri, Feb 19, 2016 at 12:46 PM, Borislav Petkov <bp@alien8.de> wrote: > On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote: >> No, the commit 84aba677f009 as of today's linux-next on which I commented. > > You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused me > as to which commit is the culprit.
Yeah, at least now it's clear I suppose.
>> commit 84aba677f009e20185aea322563389ad56e0ef7e >> Author: Boris Ostrovsky <boris.ostrovsky@oracle.com> >> Date: Tue Feb 16 09:43:19 2016 +0100 >> >> x86/microcode: Remove unnecessary paravirt_enabled check >> >> One more thing: I run this kernel as a second from kexec. It might be >> related as well. For now I have no possibility to run it as a first >> kernel. > > Well, how exactly are you triggering this? Do you have a splat or some > other register dump so that I can try to pinpoint this. I'll need more > info so that I can reproduce it here and debug it.
It stuck at some point during boot. I'm trying to get earlycon or earlyprintk to show me something...
-- With Best Regards, Andy Shevchenko
| |