From owner-freebsd-current@freebsd.org  Thu Dec 22 20:26:14 2016
Return-Path: <owner-freebsd-current@freebsd.org>
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 6CC9DC8CCD4
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 22 Dec 2016 20:26:14 +0000 (UTC) (envelope-from wjw@digiware.nl)
Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9])
 (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 32C761BFD
 for <freebsd-current@freebsd.org>; Thu, 22 Dec 2016 20:26:13 +0000 (UTC)
 (envelope-from wjw@digiware.nl)
Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1])
 by smtp.digiware.nl (Postfix) with ESMTP id 3A66233FF1;
 Thu, 22 Dec 2016 21:26:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at digiware.com
Received: from smtp.digiware.nl ([127.0.0.1])
 by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id ND_1CwuBmCBd; Thu, 22 Dec 2016 21:26:05 +0100 (CET)
Received: from [192.168.10.10] (asus [192.168.10.10])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by smtp.digiware.nl (Postfix) with ESMTPSA id 9623433FEF;
 Thu, 22 Dec 2016 21:26:05 +0100 (CET)
Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD
To: Adrian Chadd <adrian.chadd@gmail.com>, Slawa Olhovchenkov <slw@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>
 <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com>
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 freebsd-current <freebsd-current@freebsd.org>
From: Willem Jan Withagen <wjw@digiware.nl>
Message-ID: <3792b7ea-0818-b358-4091-d78c3214a09c@digiware.nl>
Date: Thu, 22 Dec 2016 21:26:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <CAJ-Vmon8NX9c0C6rK896UoSDdT=L0MVLuNkciuwzrgv9dEYjuA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2016 20:26:14 -0000

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.

--WjW