Date: Fri, 23 Dec 2016 16:26:27 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Willem Jan Withagen <wjw@digiware.nl> Cc: Adrian Chadd <adrian.chadd@gmail.com>, Konstantin Belousov <kostikbel@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161223132627.GA37153@zxy.spb.ru> In-Reply-To: <3792b7ea-0818-b358-4091-d78c3214a09c@digiware.nl> References: <20161214121336.GD98176@zxy.spb.ru> <20161214152627.GF98176@zxy.spb.ru> <20161214190349.GJ94325@kib.kiev.ua> <20161215105118.GK98176@zxy.spb.ru> <20161215123330.GQ94325@kib.kiev.ua> <20161215131624.GL98176@zxy.spb.ru> <20161215135656.GS94325@kib.kiev.ua> <20161215224500.GM98176@zxy.spb.ru> <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com> <3792b7ea-0818-b358-4091-d78c3214a09c@digiware.nl>
index | next in thread | previous in thread | raw e-mail
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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161223132627.GA37153>