Date: Fri, 13 Mar 2015 18:27:39 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-hackers@freebsd.org Subject: Re: Server with 3TB Crashing at boot Message-ID: <55032C1B.5030004@multiplay.co.uk> In-Reply-To: <5503234A.4060103@fuckner.net> References: <550046F7.1050205@fuckner.net> <CAJ-VmokruCyo3M5up9n%2BAfvkr7VFBtUftpdgc=52ES%2BNt6=JZA@mail.gmail.com> <CAPQ4ffsd-SpsLTbGL8BdBsNHLx9HhVQ4Wh%2B95M98fCmT5idPAg@mail.gmail.com> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <CAJ-Vmom%2BZy_6ZCcTA_h4LFL-wDdaCmbqAgN5shpOsBBgWJw1mg@mail.gmail.com> <5503234A.4060103@fuckner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/03/2015 17:50, Michael Fuckner wrote: > On 03/12/2015 08:30 PM, Adrian Chadd wrote: >> Right. Try booting it with SMP disabled but with all the RAM. >> >> I think it's 'kern.smp.disabled=1' at the bootloader, then 'boot -v' > > my problem seems to be my /boot/loader.conf > > which is the correct option for verboose booting? > when loading nvme/nvd/zfs it crashes. > why is mpr1 detected after loading nvme? (I boot from mpr0) > > > hw.memtest.tests=0 > #kern.smp.disabled=1 > console=comconsole > boot_verbose="YES" > verbose_loading="YES" > zfs_load="NO" > nvme_load="NO" > nvd_load="NO" > > http://dedi3.fuckner.net/~molli123/temp/kldload-nvme_nvd_zfs.txt > http://dedi3.fuckner.net/~molli123/temp/freebsd-10.1_smp-disabled_verbose.txt > > http://dedi3.fuckner.net/~molli123/temp/freebsd-10.1_smp-enabled_verbose.txt > > > > Any idea? Looks like that's panicing when allocating the zfs dbuf hash table, which by my calculation should be requesting 8GB for a 4TB physmem? Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55032C1B.5030004>