From owner-freebsd-current@freebsd.org Tue Dec 13 11:14:41 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56930C7543D for ; Tue, 13 Dec 2016 11:14:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 194A81C2E for ; Tue, 13 Dec 2016 11:14:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cGl2b-000IJG-9Z; Tue, 13 Dec 2016 14:14:37 +0300 Date: Tue, 13 Dec 2016 14:14:37 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: "A. Wilcox" , freebsd-current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161213111437.GH90287@zxy.spb.ru> References: <20161212162152.GC90287@zxy.spb.ru> <20161212165457.GI54029@kib.kiev.ua> <20161212171634.GD90287@zxy.spb.ru> <20161212172418.GK54029@kib.kiev.ua> <20161212174311.GE90287@zxy.spb.ru> <20161212183647.GL54029@kib.kiev.ua> <20161212192619.GF90287@zxy.spb.ru> <584F22B1.9000903@Wilcox-Tech.com> <20161212233714.GA90401@zxy.spb.ru> <20161213110535.GS54029@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161213110535.GS54029@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 11:14:41 -0000 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.