From nobody Wed Aug 17 23:03:37 2022 X-Original-To: freebsd-arm@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 4M7Ns51nGyz4ZWvD for ; Wed, 17 Aug 2022 23:05:13 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (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 "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M7Ns36LdXz3WST for ; Wed, 17 Aug 2022 23:05:11 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.16.1/8.16.1) with ESMTPS id 27HN3b22015833 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 17 Aug 2022 16:03:37 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.16.1/8.16.1/Submit) id 27HN3b8q015832; Wed, 17 Aug 2022 16:03:37 -0700 (PDT) (envelope-from warlock) Date: Wed, 17 Aug 2022 16:03:37 -0700 From: John Kennedy To: Marek Soudny Cc: freebsd-arm Subject: Re: kernel: Fatal data abort - issue on rpi4 Message-ID: References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> X-Rspamd-Queue-Id: 4M7Ns36LdXz3WST X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net X-Spamd-Result: default: False [-1.80 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[phouka.net]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net] X-ThisMailContainsUnwantedMimeParts: N On Wed, Aug 17, 2022 at 11:10:30AM +0200, Marek Soudny wrote: > Hello, > > I am quite new to arm/aarch64. I recently purchased rpi4, burned an > sdcard image and have been trying to run it. Time to time (but actually > quite often) the box becomes unresponsive. I can not ping it, neither > ssh into it. I am running fbsd 13.1-release. When I was doing a lot of SDcard work pre-RPI4, I was almostly exclusively using SanDisk (Ultra) cards. I was looking for robust cards with high transfer speed. Once USB became an option, I pretty only much booted off them when I was forced to. I'm not knocking SD cards to much here, but they're tiny and I put mine through a LOT of disk I/O. Even with wear leveling, without a lot of space to level over I can't be doing that thing a lot of favors. Depending on how your cooling thermals are, you could be torturing that poor thing. Hanging a space-big USB disk off that thing seemed like a big win in a lot of ways. Again, depends on your use. > Does it sound familiar? Am I doing something wrong? As it's currently > not stable, I can perform any tests with it, if required. I actually > found a similar issue > https://forums.freebsd.org/threads/fatal-kernel-mode-data-abort-every-2-3-boots-on-raspberry-pi-b.49066/ > - do you think it's an sdcard issue? If so, is there a recommended list > for purchase new ones? Well, I think your link looks much more like a disk (deiver) issue, where yours looked more like some kind of register dump to me without a stack trace and some of the trappings from that image. If it's easy, I'd try USB. Probably bigger, faster, cheaper, and for a test you may just have something laying around idle (plus it may help rule out some physical issue with the SD card slot). If it works, then that points to a problematic card. If not, something else.