Date: Sat, 26 Nov 2016 17:57:47 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: current@freebsd.org Subject: Re: Enabling NUMA in BIOS stop booting FreeBSD Message-ID: <20161126155747.GF54029@kib.kiev.ua> In-Reply-To: <20161126092124.GM57876@zxy.spb.ru> References: <20161126092124.GM57876@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 26, 2016 at 12:21:24PM +0300, Slawa Olhovchenkov wrote: > I am try to enable NUMA in bios and can't boot FreeBSD. > Boot stoped after next messages: > > === > Booting... > KDB: debugger backends: ddb > KDB: current backend: ddb So at least the hammer_time() has a chance to initialize the console. Do you have serial console ? Set the loader tunable debug.late_console to 1 and see if any NMI reaction appear. > === > > This is verbose boot. > No reaction to ~^B, NMI. > > Same for head and 10.3-RELEASE. > > Hardware is Supermicro X10DRi, Dual E5-2650v4, 256GB RAM. Is there a BIOS option for 'on-chip cluster' or 'HPC computing' ? What if you try to frob it ? > > On slight different hardware > (Supermicro X10DRi w/ old BIOS, Dual E5-2640v3, 128GB RAM) > 10.3 boot ok w/ BIOS NUMA enabled. I think the only way to debug this is to add printf() lines to hammer_time() to see where does it break. Note that amd64_kdb_init() call succeeded, so you can start bisect the code from there.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161126155747.GF54029>