From owner-freebsd-arm@freebsd.org Sun Mar 7 15:55:12 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D2C0F56AC89 for ; Sun, 7 Mar 2021 15:55:12 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DtmJb6ml4z3CH0 for ; Sun, 7 Mar 2021 15:55:11 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 127FtFkF004730 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 7 Mar 2021 07:55:16 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 127FtFuQ004729; Sun, 7 Mar 2021 07:55:15 -0800 (PST) (envelope-from fbsd) Date: Sun, 7 Mar 2021 07:55:15 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm , bob prohaska Subject: Re: RPi4 Status and sysutils/rpi-firmware (and rng) Message-ID: <20210307155515.GA4591@www.zefox.net> References: <20210307021628.GA99890@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DtmJb6ml4z3CH0 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2021 15:55:12 -0000 On Sat, Mar 06, 2021 at 09:30:33PM -0800, Mark Millard wrote: > > I've not done the huge-file copy-corruption testing > recently, and never with stable/13 or releng/13.0 or > a 13.0-BETA*/RC* . I probably should try, booting > a 13.0-RC* image as the context (other than the > rpi-firmware replacements). I use a file that is > notably bigger than the RAM. > This is -current, chosen to be the latest offered. > Historically, if the corruption problems show up > the technique to get a reliable environment was to > restrict it to using 3 GiBytes, possibly via some > text in config.txt . This also applied to the > RPi4B 4 GiByte models. > Might it be useful to attempt the huge-file corruption test? This is a microSD-only setup, but it's a 32 GB card so there's enough space for a file bigger than the 8 GB RAM. The most obvious sticking point is need to manufacture a test file since there's no ethernet. The second issue would be reporting; all I can do is look at the screen and make manual notes. Enough for a go/no-go test, not so good for details. Thanks for reading, and all your help! bob prohaska