Date: Mon, 12 Dec 2016 02:09:51 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Konstantin Belousov <kostikbel@gmail.com> Cc: current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161211230951.GB90287@zxy.spb.ru> In-Reply-To: <20161211224621.GA90287@zxy.spb.ru> References: <20161126092124.GM57876@zxy.spb.ru> <20161126155747.GF54029@kib.kiev.ua> <20161211182111.GH31311@zxy.spb.ru> <20161211191626.GI31311@zxy.spb.ru> <20161211192656.GZ54029@kib.kiev.ua> <20161211194559.GJ31311@zxy.spb.ru> <20161211200654.GA54029@kib.kiev.ua> <20161211204709.GK31311@zxy.spb.ru> <20161211211552.GL31311@zxy.spb.ru> <20161211224621.GA90287@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 12, 2016 at 01:46:21AM +0300, Slawa Olhovchenkov wrote: > > > > > > Can you show the verbose dmesg up to the failure point ? > > > > > > In particular, the SMAP lines should be relevant. > > > > > > > > > > KDB: debugger backends: ddb > > > > > KDB: current backend: ddb > > > > > exit from kdb_init > > > > > KDB: enter: Boot flags requested debugger > > > > > [ thread pid 0 tid 0 ] > > > > > Stopped at 0xffffffff805361eb = kdb_enter+0x3b: movq > > > > > $0,0xffffffff80dcef20 = kdb_why Hang at boot is result of combination next two BIOS setting: NUMA enabled Socket Interleave below 4G enabled (memory options) Disabling any allow boot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161211230951.GB90287>