From owner-freebsd-current@freebsd.org Fri Dec 23 21:07:10 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 3FB46C8EDF0 for ; Fri, 23 Dec 2016 21:07:10 +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 F3A10821 for ; Fri, 23 Dec 2016 21:07:09 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cKX3S-00041B-M8; Sat, 24 Dec 2016 00:07:06 +0300 Date: Sat, 24 Dec 2016 00:07:06 +0300 From: Slawa Olhovchenkov To: Willem Jan Withagen Cc: Adrian Chadd , Konstantin Belousov , freebsd-current Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161223210706.GD37118@zxy.spb.ru> References: <20161215123330.GQ94325@kib.kiev.ua> <20161215131624.GL98176@zxy.spb.ru> <20161215135656.GS94325@kib.kiev.ua> <20161215224500.GM98176@zxy.spb.ru> <3792b7ea-0818-b358-4091-d78c3214a09c@digiware.nl> <20161223132627.GA37153@zxy.spb.ru> <20161223193001.GC37118@zxy.spb.ru> <035cd161-28b6-b165-77b6-3dea21b3a9b3@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <035cd161-28b6-b165-77b6-3dea21b3a9b3@digiware.nl> 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: Fri, 23 Dec 2016 21:07:10 -0000 On Fri, Dec 23, 2016 at 09:37:40PM +0100, Willem Jan Withagen wrote: > On 23-12-2016 20:30, Slawa Olhovchenkov wrote: > > On Fri, Dec 23, 2016 at 08:16:39PM +0100, Willem Jan Withagen wrote: > > > >> On 23-12-2016 14:26, Slawa Olhovchenkov wrote: > >>> On Thu, Dec 22, 2016 at 09:26:02PM +0100, Willem Jan Withagen wrote: > >>> > >>>> On 16-12-2016 00:57, Adrian Chadd wrote: > >>>>> heh, an updated BIOS that solves the problem will solve the problem. :) > >>>>> > >>>>> I think you have enough information to provide to supermicro. Ie, > >>>>> "SMAP says X, when physical memory pages at addresses X are accessed, > >>>>> they don't behave like memory, maybe something is wrong". > >>>>> > >>>>> All I can think of is some hack to add a blacklist for that region so > >>>>> you can boot the unit. But it makes me wonder what else is going on. > >>>> > >>>> I have an X10DRL-iT with 256Gb and 2* 2630V4 available for testing until > >>>> begin January. Started it on 11-RELEASE and upgraded to 12-CURRENT of > >>>> 20-12-2016. > >>>> Boots just fine, and seems to run OKE. > >>>> > >>>> If anything useful to test, just let me know. > >>> > >>> For touch issuse you must enable in BIOS both NUMA and Memory > >>> Interleave below 4G. > >> > >> Numa was already on, but I cannot find the Memory Interleave option. > > > > for X10DRi: > > > > Advanced/Chipset Config/North Bridge/Memory Config/Socket Interleave below 4G > > The only thing that could be this is: > a7 mode, > but that is already enabled. > This speaks about a bit higher memory bandwidth. In may case A7 immediately below 'Socket Interleave below 4G' > On the PCIe page ther is something like: > above 4G encoding > but that will probably not be it. > > --WjW >