Date: Fri, 16 Dec 2016 13:20:55 -0800 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Adrian Chadd <adrian.chadd@gmail.com>, Slawa Olhovchenkov <slw@zxy.spb.ru>, Konstantin Belousov <kostikbel@gmail.com> Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <1995191.rPAPaoHxgb@ralph.baldwin.cx> In-Reply-To: <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com> References: <20161214102711.GF94325@kib.kiev.ua> <20161215224500.GM98176@zxy.spb.ru> <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, December 15, 2016 03:57:58 PM 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. We have the blacklist: it is the memory test. That is the way to workaround this type of BIOS breakage. This is just the first time in over a decade that test has been relevant. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1995191.rPAPaoHxgb>