From owner-freebsd-current@freebsd.org  Fri Dec 23 19:30:06 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 350B2C8D157
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 23 Dec 2016 19:30:06 +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 E9265D79
 for <freebsd-current@freebsd.org>; Fri, 23 Dec 2016 19:30:05 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1cKVXW-0001Vg-1x; Fri, 23 Dec 2016 22:30:02 +0300
Date: Fri, 23 Dec 2016 22:30:02 +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: <20161223193001.GC37118@zxy.spb.ru>
References: <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>
 <20161223132627.GA37153@zxy.spb.ru>
 <c3c3ae7a-f24f-9157-fc3c-623d2ce27143@digiware.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c3c3ae7a-f24f-9157-fc3c-623d2ce27143@digiware.nl>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
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
 <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: Fri, 23 Dec 2016 19:30:06 -0000

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