From nobody Mon Jan 17 13:24:01 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 488E61963BCD for ; Mon, 17 Jan 2022 13:24:31 +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 4Jct0s5zvPz4h0N for ; Mon, 17 Jan 2022 13:24:29 +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 E8E471F655; Mon, 17 Jan 2022 14:24:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1642425867; bh=l2rVf8e01I4xZLB4+1O4meHhI0n69S86i7UJua6kLTA=; h=Date:Subject:To:References:From:In-Reply-To; b=XrR7iwnOjzwHT9xaxpnAvyQQNcyE6jKmLz5JCg9xrloR9smEhIWC+re8vas8CwiML E0ppl3WVlJ0fIgzhcTGx3Gz5hlRE4L+8/h0y568HEF+5YPC1hykrOGmICm1TlyeZx1 XMaL3Y4vSQxM/7Jvslfg1VbXMhVc186e1j096wpz20ayXtSYonRzXRImg0e+1ALjyH IQprmHATe6AvdBT/YXXPRxaHAGB8qaB01eKpeCMy0Jt1f6XM9cs18j0pDN9L2nRfV1 oaOsK89eQd0MYruQsGrEPcRGtuj4QWeb/pv2KZWs4oKYY4RfVIrK6YK+uGp67uJ6cA 6XSD+QJptGDRQ== 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 3yUShUsvAF6e; Mon, 17 Jan 2022 14:24:02 +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 B607F1F479; Mon, 17 Jan 2022 14:24:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=digiware.nl; s=medusa-2017; t=1642425842; bh=l2rVf8e01I4xZLB4+1O4meHhI0n69S86i7UJua6kLTA=; h=Date:Subject:To:References:From:In-Reply-To; b=srgz38yH8uKfB21nuY3k2NumPB3N7fFxkU6LTItccP9u9mqzLRa+0MKIW9ChIqa8k YfXXkpxbI0vEufNJOMbaAYebwiP+ff6R36zfIpnvwX4gK62NC2xmQIezGP3A0x50ck YwAixnbde1ZO7aaSLRonKHTZE3wKzL5oUnAwcK5LG8OFsUflUbamjkwXxjEaCZDmYm jrNZnKgKZ8muyShN92TfJ+qA1yyU9k2QJBsuTtlYRhyDhxwozDRFTYBEEfS9ixk4TL i8wKjUdJTa8ltU4W3cIR1xlTi/Kjf2mYSJjSEeAON/Fdztl/YkjC/dDqoRN9yQ9/Ee d+L/MsmbMJr2g== Message-ID: Date: Mon, 17 Jan 2022 14:24:01 +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: 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> From: Willem Jan Withagen In-Reply-To: <71d1e25c-f1f6-2371-486e-2382d67a3fc5@grosbein.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Jct0s5zvPz4h0N X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=digiware.nl header.s=medusa-2017 header.b=XrR7iwnO; dkim=pass header.d=digiware.nl header.s=medusa-2017 header.b=srgz38yH; 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 [-4.00 / 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)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[digiware.nl:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[digiware.nl,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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 14:09, Eugene Grosbein wrote: > 17.01.2022 18:43, Willem Jan Withagen wrote: > >>> How much RAM does the system have? >>> You can try reducing memory addressed by the kernel with another loader knob: >>> >>> hw.physmem=4G >> But this was an even better hint... I set it too 1G to even avond the 4Gb limit. >> Board should have 16Gb of mem.... >> >> It now get all the way to mounting the USB stick... >> >> This what could be the problem now? >> >> subsystem ffffff >> parse_acpi_tables(0)... SRAT: Ignoring memory at addr 0x100000000 >> SRAT: Ignoring memory at addr 0x220000000 >> SRAT: No memory found for CPU 4 >> done. >> subsystem 1000000 >> vm_mem_init(0)... vm_mem_init:131 >> done. >> >> I have both tried 1Gb and 4Gb. >> Could be that one of the DIMMs is defect, not seated correctly, or in the wrong slot?? >> >> This would suggest that 4Gb is missing: >> real memory = 12884901888 (12288 MB) >> Physical memory chunk(s): >> 0x0000000000010000 - 0x0000000000099fff, 565248 bytes (138 pages) >> 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) >> 0x0000000001200000 - 0x00000000da659fff, 3645218816 bytes (889946 pages) >> avail memory = 3618148352 (3450 MB) >> done. > 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. --WjW