From: "Raj, Ashok" <email@example.com> To: Borislav Petkov <firstname.lastname@example.org> Cc: Vitezslav Samel <email@example.com>, Greg Kroah-Hartman <firstname.lastname@example.org>, email@example.com, Ashok Raj <firstname.lastname@example.org> Subject: Re: 4.15.17 regression: bisected: timeout during microcode update Date: Wed, 18 Apr 2018 06:53:30 -0700 [thread overview] Message-ID: <20180418135330.GA23580@araj-mobl1.jf.intel.com> (raw) In-Reply-To: <20180418122212.GA4290@pd.tnic> On Wed, Apr 18, 2018 at 02:22:12PM +0200, Borislav Petkov wrote: > On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote: > > I switched to firmware-in-kernel early loading and that works OK. firmware-in-kernel means you compile your microcode image in linux? Can you tell me which distro you are using? The ones we used doesn't do late-loading (i.e echo 1 > /sys/devices/system/cpu/microcode/reload) I suspect that might be the problem. - Can you remove your builtin microcode, - rename the /lib/firmware/intel-ucode so we don't find it during late loading. - let the system boot completely - then rename the intel-ucode back for this test. - write 1 to reload and see if that update succeeds or fails? > > Ok, and keep using that from now on. > > People should all move away from that late loading dance. I'm saying > that in case someone else reads this on lkml. > > > But still, the reported issue is regression in 4.15.17 and 4.16+. > > Oh, I know it is a regression. > > @Ashok: anything particular about his microcode revision not being able > to stomach late loading? nothing about the microcode itself comes to mind. I'm wondering if this similar to the Arch linux that used late-load during booting might be an issue.
next prev parent reply other threads:[~2018-04-18 13:53 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-18 8:11 Vitezslav Samel 2018-04-18 10:07 ` Borislav Petkov 2018-04-18 12:08 ` Vitezslav Samel 2018-04-18 12:22 ` Borislav Petkov 2018-04-18 13:53 ` Raj, Ashok [this message] 2018-04-18 16:14 ` Borislav Petkov 2018-04-19 5:35 ` Vitezslav Samel 2018-04-19 7:22 ` Raj, Ashok 2018-04-19 10:48 ` Borislav Petkov 2018-04-19 12:02 ` Vitezslav Samel 2018-04-19 12:18 ` Borislav Petkov 2018-04-19 12:32 ` Raj, Ashok 2018-04-19 13:48 ` Vitezslav Samel 2018-04-19 13:46 ` Vitezslav Samel 2018-04-19 16:37 ` Borislav Petkov 2018-04-20 6:20 ` Vitezslav Samel 2018-04-20 9:52 ` Borislav Petkov 2018-04-20 10:01 ` Vitezslav Samel 2018-04-20 10:32 ` Borislav Petkov 2018-04-20 10:34 ` [PATCH 1/2] x86/microcode/intel: Save microcode patch unconditionally Borislav Petkov 2018-04-20 10:54 ` Vitezslav Samel 2018-04-20 15:59 ` Raj, Ashok 2018-04-20 10:37 ` [PATCH 2/2] x86/microcode: Do not exit early from __reload_late() Borislav Petkov 2018-04-20 10:54 ` Vitezslav Samel 2018-04-20 16:00 ` Raj, Ashok 2018-04-21 8:19 ` [PATCH 1/2] x86/microcode/intel: Save microcode patch unconditionally Borislav Petkov 2018-04-21 8:19 ` [PATCH 2/2] x86/microcode: Do not exit early from __reload_late() Borislav Petkov 2018-04-24 7:52 ` [tip:x86/urgent] " tip-bot for Borislav Petkov 2018-04-24 7:51 ` [tip:x86/urgent] x86/microcode/intel: Save microcode patch unconditionally tip-bot for Borislav Petkov
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=20180418135330.GA23580@araj-mobl1.jf.intel.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: 4.15.17 regression: bisected: timeout during microcode update' \ /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
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.