From owner-freebsd-current@freebsd.org Tue Dec 13 14:34:04 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 9A9DBC75A6E for ; Tue, 13 Dec 2016 14:34:04 +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 5C6B8B5F for ; Tue, 13 Dec 2016 14:34:04 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1cGo9Z-000O4T-VI; Tue, 13 Dec 2016 17:34:01 +0300 Date: Tue, 13 Dec 2016 17:34:01 +0300 From: Slawa Olhovchenkov To: Konstantin Belousov Cc: "A. Wilcox" , freebsd-current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161213143401.GK90287@zxy.spb.ru> References: <20161212183647.GL54029@kib.kiev.ua> <20161212192619.GF90287@zxy.spb.ru> <584F22B1.9000903@Wilcox-Tech.com> <20161212233714.GA90401@zxy.spb.ru> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161213141114.GJ90287@zxy.spb.ru> 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 14:34:04 -0000 On Tue, Dec 13, 2016 at 05:11:14PM +0300, Slawa Olhovchenkov wrote: > On Tue, Dec 13, 2016 at 03:57:59PM +0200, Konstantin Belousov wrote: > > > On Tue, Dec 13, 2016 at 03:49:32PM +0300, Slawa Olhovchenkov wrote: > > > > Boot with NUMA enabled and interleave off. > > > > > > Already with patched kernel > > > > > > > Patch kernel with the 'if (1 || ...)' patch. > > > > Reboot, enter BIOS setup and enable interleave there. > > > > Try to boot - does it boot ? > > > > > > No. > > > > > > > If it did not booted, power machine off for 10 minutes. > > > > > > OK > > > > > > > Power it on, try to boot (with the same patched kernel). > > > > Does the machine boot now ? > > > > > > Don't boot. > > > > I am really puzzled. In other words, touching all memory causes the > > msgbuf to not hang. > > yes > > > Can you try one more experiment ? > > Take the patch below, apply it. > > >From the config where interleave is disabled, install new kernel. > > Reboot, enter BIOS setup and enable interleave. > > Set late_console to zero in loader. > > Do not enable memory test. > > Boot the patched kernel. > > Kernel must hang, according to your previous reports. > > I want to see the console log. > > Hmm. I am [already] show output from ddb, and guess kernel will be > hang at first wirte to *mbp, i.e. you don't see any in console log. > > OK, anyway I am try this pacth. 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 XXX1 YYY1 ZZZ1