From owner-freebsd-current@freebsd.org  Fri Dec 16 21:31:03 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 7FE82C832BA
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 16 Dec 2016 21:31:03 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5E37614D0
 for <freebsd-current@freebsd.org>; Fri, 16 Dec 2016 21:31:02 +0000 (UTC)
 (envelope-from jhb@freebsd.org)
Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net
 [73.231.226.104])
 by mail.baldwin.cx (Postfix) with ESMTPSA id 8637310AA5E;
 Fri, 16 Dec 2016 16:31:01 -0500 (EST)
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
Date: Fri, 16 Dec 2016 13:20:55 -0800
Message-ID: <1995191.rPAPaoHxgb@ralph.baldwin.cx>
User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; )
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>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mail.baldwin.cx); Fri, 16 Dec 2016 16:31:01 -0500 (EST)
X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx
X-Virus-Status: Clean
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, 16 Dec 2016 21:31:03 -0000

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