From owner-freebsd-current@freebsd.org Tue Dec 20 21:49:50 2016 Return-Path: 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 CD6CAC761AE for ; Tue, 20 Dec 2016 21:49:50 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E12F1CA5; Tue, 20 Dec 2016 21:49:50 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [10.0.1.70] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id uBKLnZlY068458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 20 Dec 2016 21:49:46 GMT (envelope-from swills@FreeBSD.org) Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD To: John Baldwin , freebsd-current@freebsd.org References: <20161214102711.GF94325@kib.kiev.ua> <20161215224500.GM98176@zxy.spb.ru> <1995191.rPAPaoHxgb@ralph.baldwin.cx> Cc: Adrian Chadd , Slawa Olhovchenkov , Konstantin Belousov From: Steve Wills Message-ID: Date: Tue, 20 Dec 2016 16:49:29 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <1995191.rPAPaoHxgb@ralph.baldwin.cx> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dpGsxMK1W50q9LenaBLVQQmnvElsjP0U6" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Tue, 20 Dec 2016 21:49:49 +0000 (UTC) X-Spam-Status: No, score=-1.0 required=4.5 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2016 21:49:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dpGsxMK1W50q9LenaBLVQQmnvElsjP0U6 Content-Type: multipart/mixed; boundary="LHgCCvMB4a6VD5VC9TgLvcG2I2rn4jQIs"; protected-headers="v1" From: Steve Wills To: John Baldwin , freebsd-current@freebsd.org Cc: Adrian Chadd , Slawa Olhovchenkov , Konstantin Belousov Message-ID: Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD References: <20161214102711.GF94325@kib.kiev.ua> <20161215224500.GM98176@zxy.spb.ru> <1995191.rPAPaoHxgb@ralph.baldwin.cx> In-Reply-To: <1995191.rPAPaoHxgb@ralph.baldwin.cx> --LHgCCvMB4a6VD5VC9TgLvcG2I2rn4jQIs Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi, On 12/16/2016 16:20, John Baldwin wrote: > 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. >=20 > We have the blacklist: it is the memory test. That is the way to worka= round > this type of BIOS breakage. This is just the first time in over a deca= de that > test has been relevant. I've got a SuperMicro X10SRA board that I bought back in March, I think. It was run CURRENT fine since then, until last month, when it started hanging during boot. I was about to update it to a new version of CURRENT when it started hanging at boot, but hadn't updated yet. The hang is after (verbose boot): ACPI APIC Table: Package ID shift: 4 L3 cache ID shift: 4 L2 cache ID shift: 1 L1 cache ID shift: 1 Core ID shift: 1 Recently I've tried booting 9.3 and 10.3 on it without success. Other operating systems boot fine. Thinking the hang was similar to the one in this thread (or at least the board is), I tried many different BIOS changes and also tried enabling the memory test, but none of that changes anything. This is a single socket board so there are no NUMA or memory interleaving options in the BIOS. The BIOS is up to date (2.0a). It will boot if SMP is disabled. That's obviously sub-optimal, but is useful for building updated kernels, which I've tried. If anyone has any suggestions or ideas, I'd appreciate it. Thanks, Steve --LHgCCvMB4a6VD5VC9TgLvcG2I2rn4jQIs-- --dpGsxMK1W50q9LenaBLVQQmnvElsjP0U6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGQBAEBCgB6BQJYWadrXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5OEZBNDE0QTVDMkEwRUY5Q0ZEMEFEMERG NUNGNjJCMzIwN0IxQkExExxzd2lsbHNAZnJlZWJzZC5vcmcACgkQ9c9isyB7G6EK oAf/SLXCN2loInq0teABXiOsRF+m3auOdElEVr4NS15zaJvcbeMCAbEfRD5uLoOa w7Xyuuayr5IGAv6KQL2nDzWTx3i6rFLFagIGXeKuFTUIk2nL98giJ23apTE05sp0 d3q+tqNdfHJWBZNx9fNxCgt85C66420CCSN63Br12cOH5hr2XQm05e+J8brgxjXe r/fwPQ29fY9hOGuXsHDGYfzBuLmZ7UmUoWGp+Pm2q0VwoKiufY8jHho+26m6scvM yaNhuiJN45zu8A9psq4EfhI1x+db0jUgaQGAEi/OoEM6dOE03O+U/I2UupG8xsTO bm5qTtfrvyuHt3r0x7VzC1BZew== =06Jv -----END PGP SIGNATURE----- --dpGsxMK1W50q9LenaBLVQQmnvElsjP0U6--