From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 13 07:52:21 2015 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4586C79D; Fri, 13 Mar 2015 07:52:21 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A6B70BA5; Fri, 13 Mar 2015 07:52:20 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t2D7qE09049531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Mar 2015 09:52:14 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t2D7qE09049531 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t2D7qCQe049530; Fri, 13 Mar 2015 09:52:12 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 13 Mar 2015 09:52:12 +0200 From: Konstantin Belousov To: Peter Jeremy Subject: Re: Server with 3TB Crashing at boot Message-ID: <20150313075212.GU2379@kib.kiev.ua> References: <550046F7.1050205@fuckner.net> <550093DD.5040603@freebsd.org> <55015D3B.6030605@fuckner.net> <5501DD57.7030305@freebsd.org> <20150313054116.GB92183@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150313054116.GB92183@server.rulingia.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: "freebsd-hackers@freebsd.org" , Adrian Chadd , freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2015 07:52:21 -0000 On Fri, Mar 13, 2015 at 04:41:16PM +1100, Peter Jeremy wrote: > On 2015-Mar-12 12:30:39 -0700, Adrian Chadd wrote: > >Right. Try booting it with SMP disabled but with all the RAM. > > Is this possible? Can one CPU see the RAM on another CPU if that CPU > isn't enabled in the kernel? Yes, of course. The disabled state means that the core is not started to execute the stream of the architectural instructions opcodes. The memory controller, address decoder and inter-socket links, and pcie links are configured by the motherboard firmware during the POST. They are left alone by our kernel.