Date: Thu, 15 Dec 2016 15:57:58 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com> In-Reply-To: <20161215224500.GM98176@zxy.spb.ru> References: <20161214102711.GF94325@kib.kiev.ua> <20161214105211.GC98176@zxy.spb.ru> <20161214113927.GG94325@kib.kiev.ua> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA>