From nobody Mon Jan 17 18:45:13 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 B334C1958954 for ; Mon, 17 Jan 2022 18:45:43 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 4Jd17V0Ls6z3Hss for ; Mon, 17 Jan 2022 18:45:41 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router10g.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id D508D21309; Mon, 17 Jan 2022 19:45:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1642445139; bh=OQwe0rVFe3JSj687xUzQwj+2NZsLZFevOc70SXlL7DA=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=P6MYGTbn/kdTc7Xbj27PovSwGoaLX//X6X6pY7biErgD37LIZXGqZueul3iDwC7Eo sfU7HObNSlMNEd8FkVNOKr5CePRgYTRKP+7R2ypgTOxof5dev6GdU+cWH/THk9Dwms SzAI9H4iReLFVuf4yh10+dTD5d0ARQ4lr959rEPqxYksTD5jugSDa8y/9mwjUjvzil /K+aIl42gF6JjYMEUm2l4fGPxxVteM/x8qf6Mb+h9ZlyOpXDHNSp+RzVy8f/cycRyi ZWVHw6C1w2qmniWlu2ZPB5T79WiZ9hSRXNuy3ABAjEBAu3WrX3n+I+jUKGaENkxXwQ peRRPe1ZKkGOQ== X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by router10g.digiware.nl (router10g.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udt15QE-s43x; Mon, 17 Jan 2022 19:45:14 +0100 (CET) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id BB0C1212AC; Mon, 17 Jan 2022 19:45:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1642445114; bh=OQwe0rVFe3JSj687xUzQwj+2NZsLZFevOc70SXlL7DA=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=Y2KSQP3RuaMMqAqgY758fJmevPWqmi3NUEzNpzB47JeMM8t19cG+HjOo9UaQusvqx x0LiNNCSoOW7lhBUZv8e/R0YB+NFvZ+Wq7br84323BVMDxSngvtxC5jmnD2ngyuwwX r+Peb8C7jXR24FwbracYMocn+oPv42igJLfsiFU9e4zYIN1x5PHVAzV65MWclSd7lL QL1MpCdhMH8gu1X2Q8vpLM3P8084p2YOGhGQfnYk32UB5e85QHW0nsEEAu154ijzLz gd6lFOmzTQknc2s2Lm2/4StesiQiWD88sn1YS9JhTC+hy7CVZWnWNPqQPud6zHGxc4 DtSoSfQB9xDyA== Message-ID: <8096cd7e-bc11-5fa7-cc96-6bcdf1278ffc@digiware.nl> Date: Mon, 17 Jan 2022 19:45:13 +0100 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.5.0 Subject: Re: Trying to boot a supermicro H8DMT board Content-Language: nl To: Tomoaki AOKI Cc: Eugene Grosbein , stable@freebsd.org 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> <20220118021432.197aa1241d53b1cba6e8c562@dec.sakura.ne.jp> From: Willem Jan Withagen In-Reply-To: <20220118021432.197aa1241d53b1cba6e8c562@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Jd17V0Ls6z3Hss X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=digiware.nl header.s=medusa-2017 header.b=P6MYGTbn; dkim=pass header.d=digiware.nl header.s=medusa-2017 header.b=Y2KSQP3R; dmarc=pass (policy=quarantine) header.from=digiware.nl; spf=pass (mx1.freebsd.org: domain of wjw@digiware.nl designates 176.74.240.9 as permitted sender) smtp.mailfrom=wjw@digiware.nl X-Spamd-Result: default: False [-1.99 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[digiware.nl:s=medusa-2017]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[digiware.nl:+]; DMARC_POLICY_ALLOW(-0.50)[digiware.nl,quarantine]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; MLMMJ_DEST(0.00)[stable]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 17-1-2022 18:14, Tomoaki AOKI wrote: > 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.) Yup, I know... I used the board in the configuration I got it. And its a DUAL processor board with 2 opterons. The config works correct for the first Opteron (Called CPU1) using slots: CPU1/DIMM1A and CPU1/DIMM1B But on the second CPU I have to use the third slot.... so using slots: CPU2/DIMM1B and CPU2/DIMM2B And my memtest86 has complete 1 full pass over 16G without errors. So I'm guessing that the order is not majorly picky. But you are correct in noting this, so I will read up ont this in the manual. Thanx, --WjW