On Mon, 14 Jun 2021 at 19:27, Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: > > On Mon, Jun 14, 2021 at 08:07:33PM +0300, Andy Shevchenko wrote: > > On Mon, Jun 14, 2021 at 06:38:30PM +0300, Andy Shevchenko wrote: > > > On Sat, Jun 12, 2021 at 12:40:57PM +0800, Dave Young wrote: > > > > > Probably it is doable to have kexec on 32bit efi working > > > > > without runtime service support, that means no need the trick of fixed > > > > > mapping. > > > > > > > > > > If I can restore my vm to boot 32bit efi on this weekend then I may provide some draft > > > > > patches for test. > > > > > > > > Unfortunately I failed to setup a 32bit efi guest, here are some > > > > untested draft patches, please have a try. > > > > > > Thanks for the patches. > > > > > > As previously, I have reverted my hacks and applied your patches (also I > > > dropped patches from previous mail against kernel and kexec-tools) for both > > > kernel and user space on first and second environments. > > > > > > It does NOT solve the issue. > > > > > > If there is no idea pops up soon, I'm going to resend my series that > > > workarounds the issue. > > > > Hold on, I may have made a mistake during testing. Let me retest this. > > Double checked, confirmed that it's NOT working. > Apologies for chiming in so late - in my defence, I was on vacation :-) So if I understand the thread correctly, the Surface 3 provides a SMBIOS entry point (not SMBIOS3), and it does not get picked up by the second kernel, right? I would still prefer to get to the bottom of this before papering over it with command line options. If the memory gets corrupted by the first kernel, maybe we are not preserving it correctly in the first kernel.
