From owner-freebsd-current@freebsd.org Mon Dec 12 23:37:19 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 A8A10C743E1 for ; Mon, 12 Dec 2016 23:37:19 +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 61A811DF3 for ; Mon, 12 Dec 2016 23:37:19 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cGa9j-000LCQ-11; Tue, 13 Dec 2016 02:37:15 +0300 Date: Tue, 13 Dec 2016 02:37:14 +0300 From: Slawa Olhovchenkov To: "A. Wilcox" Cc: freebsd-current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161212233714.GA90401@zxy.spb.ru> References: <20161211204709.GK31311@zxy.spb.ru> <20161212145418.GF54029@kib.kiev.ua> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <584F22B1.9000903@Wilcox-Tech.com> 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: Mon, 12 Dec 2016 23:37:19 -0000 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?