From owner-freebsd-current@freebsd.org Tue Dec 13 17:45:25 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 59FE4C76DE2 for ; Tue, 13 Dec 2016 17:45:25 +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 1BF0B1CC0 for ; Tue, 13 Dec 2016 17:45:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cGr7B-0003FY-QE; Tue, 13 Dec 2016 20:43:45 +0300 Date: Tue, 13 Dec 2016 20:43:45 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: freebsd-current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161213174345.GB98176@zxy.spb.ru> References: <20161213110535.GS54029@kib.kiev.ua> <20161213111437.GH90287@zxy.spb.ru> <20161213112340.GT54029@kib.kiev.ua> <20161213124931.GI90287@zxy.spb.ru> <20161213135759.GY54029@kib.kiev.ua> <20161213141114.GJ90287@zxy.spb.ru> <20161213143401.GK90287@zxy.spb.ru> <20161213150139.GZ54029@kib.kiev.ua> <20161213152838.GL90287@zxy.spb.ru> <20161213172529.GC54029@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161213172529.GC54029@kib.kiev.ua> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 17:45:25 -0000 On Tue, Dec 13, 2016 at 07:25:29PM +0200, Konstantin Belousov wrote: > This is not what I expected. > Also, I realized that I mis-read the memory test code. It does not > obliterate memory, old content is preserved. > > Please do exactly the same testing with another patch, at the end of the > message. There could be more output, up to 256 lines. No problem. Booting... KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=0000000000099c00 SMAP type=02 base=0000000000099c00 len=0000000000006400 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=000000007906b000 SMAP type=02 base=000000007916b000 len=0000000000936000 SMAP type=04 base=0000000079aa1000 len=0000000000509000 SMAP type=02 base=0000000079faa000 len=0000000002056000 SMAP type=01 base=0000000100000000 len=0000001f80000000 SMAP type=02 base=000000007c000000 len=0000000014000000 SMAP type=02 base=00000000fed1c000 len=0000000000029000 SMAP type=02 base=00000000ff000000 len=0000000001000000 TTT1 0xfffff8207ff00000 0xfffff8207fffffb8 100000 . 0 . 1000 . 2000 . 3000 . 4000 . 5000 . 6000 . 7000 . 8000 . 9000 . a000 . b000 . c000 . d000 . e000 . f000 . 10000 . 11000 . 12000 . 13000 . 14000 . 15000 . 16000 . 17000 . 18000 . 19000 . 1a000 . 1b000 . 1c000 . 1d000 . 1e000 . 1f000 . 20000 . 21000 . 22000 . 23000 . 24000 . 25000 . 26000 . 27000 . 28000 . 29000 . 2a000 . 2b000 > > > > > If the patched kernel boots succesfully, or if the patched kernel > > > boots further, I will provide one more, last patch, to test. > > > > please, next time point what verion of source need to patch: vanila or > > already patched. > I usually send full patches, i.e. the patch must be applied to the clean > checkout. Patch the vanilla sources. np.