On 04/04/19 at 01:23am, Junichi Nomura wrote: > Hi Dave and Chao, > > On 4/3/19 6:02 PM, Chao Fan wrote: > > On Wed, Apr 03, 2019 at 04:23:06PM +0800, Chao Fan wrote: > >> On Wed, Apr 03, 2019 at 04:09:16PM +0800, Dave Young wrote: > >>> Fix 3. need more debugging, have you or Junichi run tests on more real > >>> hardware, maybe it is easier to reproduce on real hardware, I'm glad to > >>> help to try test patch or provide any help. > >> > >> I am still testing in real hardware. > > > > Hi Dave, > > > > I find a Fujitsu Desktop PC to test it. > > Without this PATCH, it failed to kexec and kdump. > > With this PATCH, it succeed to kexec. > > But failed to kdump. From the log, I think it didn't jump to the second > > kernel, just reboot after panic. I have not figured out what's the > > problem, but it seems not caused by this PATCH. > > So I still think this PATCH works for the Fujitsu Desktop PC. > > > > As for your issue, I think there may be some problems related to specified > > hardware. Are you using a Lenovo laptop? > > > > And I am not sure how Nomura tested it. > > I've tested 3 different models of EFI-booted baremetal servers with both > normal kexec and panic kexec. So far as I've tried Linus's v5.1-rc3, > the problem always reproduced without the patch and disappears with the patch. Hmm, both of my two laptops (Thinkpad T480s and T420) failed to boot with kexec. I will see if I can find something, but it may need more time because early console does not work especially after kexec. Thanks Dave _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
