From owner-freebsd-current@freebsd.org  Thu Dec 15 10:51:22 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 DBCC5C80609
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 15 Dec 2016 10:51:22 +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 9B2EDAD3
 for <freebsd-current@freebsd.org>; Thu, 15 Dec 2016 10:51:22 +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 1cHTd8-0003lp-Td; Thu, 15 Dec 2016 13:51:18 +0300
Date: Thu, 15 Dec 2016 13:51:18 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: freebsd-current@freebsd.org
Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD
Message-ID: <20161215105118.GK98176@zxy.spb.ru>
References: <20161213152838.GL90287@zxy.spb.ru>
 <20161213172529.GC54029@kib.kiev.ua>
 <20161213174345.GB98176@zxy.spb.ru>
 <20161214095350.GE94325@kib.kiev.ua>
 <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161214190349.GJ94325@kib.kiev.ua>
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: Thu, 15 Dec 2016 10:51:23 -0000

On Wed, Dec 14, 2016 at 09:03:49PM +0200, Konstantin Belousov wrote:

> So my opinion did not changed, this sounds like firmware problem.
> I do not see how can I drill into it more.

I am don't know how it related. msgbufp mapped different with and w/o
memory test:

w/o memory test, hang:
msgbufp=0xfffff8207ff00000 pa_indx=7 phys_avail[pa_indx]=207ff00000

w/ memory test, boot:
msgbufp=0xfffff8203ff00000 pa_indx=7 phys_avail[pa_indx]=203ff00000