On Tue, Dec 13, 2016 at 01:05:35PM +0200, Konstantin Belousov wrote: > On Tue, Dec 13, 2016 at 02:37:14AM +0300, Slawa Olhovchenkov wrote: > > On Mon, Dec 12, 2016 at 04:20:33PM -0600, A. Wilcox wrote: > > > > > >>>> Try the debugging patch below, which unconditionally disables import of > > > >>>> previous buffer. To test, you would need to boot, then frob options in > > > >>>> BIOS, reboot, again frob etc. > > > >>> > > > >>> still need test patch? if yes, with BIOS options? > > > >> Yes, please test the patch. I explained the procedure above. > > > > > > > > sorry, i don't know 'frob'. > > > > what exactly options combination I need test and what about memory test? > > > > > > > > > > > > > The idea is that when rebooting, stale memory contents remain, but are > > > corrupted due to interleave. > > > > > > "Frob" basically means "mess with". So apply patch, test kernel, > > > reboot, change NUMA option, reboot again, see if it works, and so on. > > > Basically repeat your test with the NUMA=on interleave=on, NUMA=off > > > interleave=on, etc etc. > > > > NUMA=on interleave=off booted > > NUMA=on interleave=on hang > > > > I think different combination whatever? > > Do you mean, that both patched kernel, and unpatched kernel with the > memory test enabled, hang when NUMA and interleave options enabled ? Unpatched kernel boot with the memory test enabled when NUMA and interleave options enabled -- I am already reported this. patched kernel with the memory test enabled boot too. i.e. memory test enabled allow boot in any situation. > Could you enable the options, power down the machine for 10-20 minutes, > and try to boot ? For with kernel and bios options and boot options? I am have two day befor server put in production for any expirements, but please, be more clear in what combination need to test.Received on Tue Dec 13 2016 - 10:14:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC