From owner-freebsd-arm@freebsd.org Tue Feb 11 02:41:28 2020 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 2342024BC33 for ; Tue, 11 Feb 2020 02:41:28 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Gn8k4gMFz4N6N for ; Tue, 11 Feb 2020 02:41:26 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 01B2feHI020627 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Feb 2020 18:41:41 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 01B2fe6w020626; Mon, 10 Feb 2020 18:41:40 -0800 (PST) (envelope-from fbsd) Date: Mon, 10 Feb 2020 18:41:39 -0800 From: bob prohaska To: Klaus K??chemann Cc: bob prohaska , freebsd-arm@freebsd.org Subject: Re: RPI4 Install r357606 test 09.02.2020 failed Message-ID: <20200211024139.GE19140@www.zefox.net> References: <202002092026.019KQXLF021366@mail.karels.net> <4551CAE8-08DA-463F-876C-DD1BBAA5D7C5@bitblocks.com> <20200210192602.GA19140@www.zefox.net> <20200210200910.GB19140@www.zefox.net> <20200211011450.GD19140@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 48Gn8k4gMFz4N6N 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.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.975,0]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.06)[ip: (0.25), ipnet: 50.1.16.0/20(0.12), asn: 7065(-0.03), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.21)[0.215,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[googlemail.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]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 02:41:28 -0000 Hi Klaus, I do appreciate your humor and share much of it, but also have some sympathy for the poor sods chasing through the archives trying to figure out what they're doing wrong. BTDT Back around mid-summer the Pi3 was working extremely well. It really looked like Tier 1 material. Then, I think in roughly September, problems started cropping up. All appeared to be software initially. I think most of them _were_ software. At the time. Then I noticed a Pi2 acting up. Eventually it failed completely, with a bad power supply. New supply, it's fixed. Took a long time to sort that out. The Pi3 making mischief now is slightly younger than the Pi2. Both have been powered on 24/7, mostly running buildworld/kernel. Now the Pi3 is behaving suspiciously like the Pi2. And, the supply voltage is at the lower limit of acceptable. Didn't check when I got it, so there's no basis for comparison. It may be that a sound objection to the Pi is poor quality in little things like power supplies, cables and connectors. Apologies if I'm belaboring the obvious.... bob prohaska