From nobody Mon Jan 17 17:14:32 2022 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 35E251964364 for ; Mon, 17 Jan 2022 17:14:58 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jcz6n0PvNz3tjL for ; Mon, 17 Jan 2022 17:14:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 20HHEWxs051052; Tue, 18 Jan 2022 02:14:33 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 18 Jan 2022 02:14:32 +0900 From: Tomoaki AOKI To: Willem Jan Withagen Cc: Eugene Grosbein , stable@freebsd.org Subject: Re: Trying to boot a supermicro H8DMT board Message-Id: <20220118021432.197aa1241d53b1cba6e8c562@dec.sakura.ne.jp> In-Reply-To: <7c5d9cc0-be85-c855-a294-71a93f2c5440@digiware.nl> References: <8ac447b6-eaaf-0a8f-da69-27db15dd6f55@digiware.nl> <2ec39eef-d2e2-c55e-b032-43de86e71a57@digiware.nl> <3d87a0b3-7bed-453b-df23-4a258ea46fbb@grosbein.net> <802cf542-979d-b8e1-3f71-616b026eb852@grosbein.net> <48f57581-1f39-9f57-0e44-19c2c2bb3aeb@digiware.nl> <78a47e83-a339-0c79-0ee0-9e55be80c78b@grosbein.net> <2f49fd20-cb5a-5ccc-7f9b-0229bc8e14b1@grosbein.net> <86766549-be58-1125-867e-ae4c415e1bb4@digiware.nl> <7903a41f-94ba-2caf-9270-a1bd9582c600@grosbein.net> <229c3042-3297-7903-9778-9b55d5c3f998@digiware.nl> <71d1e25c-f1f6-2371-486e-2382d67a3fc5@grosbein.net> <9d73e9ba-af23-ea90-e5fa-cf3a04a8513b@grosbein.net> <7c5d9cc0-be85-c855-a294-71a93f2c5440@digiware.nl> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Jcz6n0PvNz3tjL X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [2.37 / 15.00]; RCVD_TLS_LAST(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.973]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_SPAM_LONG(1.00)[1.000]; MLMMJ_DEST(0.00)[stable]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received] X-ThisMailContainsUnwantedMimeParts: N On Mon, 17 Jan 2022 15:04:16 +0100 Willem Jan Withagen wrote: > On 17-1-2022 14:46, Eugene Grosbein wrote: > > 17.01.2022 20:24, Willem Jan Withagen wrote: > > > >>> Well, perform independent hardware (memory) testing with something like memtest86+ > >>> and if it is all right, you show ask someone more knowledgeable. Maybe CC: arch@freebsd.org > >> Perhaps should have done that when I started, but supplier assured me that > >> the they just retired the boards with out any issues. > >> Memtest86 found the faulty DIMM in 30 secs... > >> > >> Not sure if we could/want educate vm_mem_init() to actually detect this. > >> It is still in the part where everthing is still running on the first CPU. > >> Making things a bit easier to understand what is going on. > >> > >> Lets see if the box will run on 3 DIMMs for the rime being. > >> Then figure out with DMIdecode what we need expand again. > > Is it ECC memory or non-ECC? > > The kernel already have full memory testing performed at boot time > > unless disabled with another loader knob: > > > > hw.memtest.tests=0 > > > > Try booting it with memory testing disabled and without hw.physmem limitation. > > Maybe it will boot. > > > > With ECC, it could be hardware interrupt while kernel runs that test > > and wrong in-kernel processing of the interrupt. > > Swapped the DIMM with 3 others, but still the same errors. > Then I changed DIMM slot, and the errors went away. > So definitely a hardware issue > > when booted FreeBSD reported already only 12Gb in system ( there are 4 > 4GB dimms) > Using 8Gb. DIMMs are ECC. > But then still it would only boot when mem set to 8G. > > Waiting for memtest to finish at least one pass. > Usually that will take quite some time. > > --WjW > > Not sure this is the case, but some motherboards have severe limitation about DIMM slot usage, if not fully used. For example, assuming slot No. are B0-0, 1, 2, 3 and B1-0, 1, 2, 3, *Must use "interleaved. If 4 in 8 slots are to be used, B0-0, B0-2, B1-0, B1-2 shall be used. (Some forced B0-1, B0-3, B1-1, B1-3, IIRC) *Must NOT use "interleaved. B0-0, B0-1, B1-0, B1-1 shall be used. *Must NOT use B1 unless B0 is full of DIMs. B0-0. B0-1, B0-2, B0-3 shall be used. and so on, depending on motherboard vendor (at worst, per model.) -- Tomoaki AOKI