From owner-freebsd-arm@freebsd.org Mon Apr 19 13:59:44 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 2AB355F2CEF for ; Mon, 19 Apr 2021 13:59:44 +0000 (UTC) (envelope-from stefan.haller@stha.de) Received: from deponia.stha.de (deponia.stha.de [IPv6:2001:8d8:1801:133::1]) (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 (4096 bits) client-digest SHA256) (Client CN "mx1.stha.de", Issuer "mx1.stha.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FP7jV4Y0yz4RWS for ; Mon, 19 Apr 2021 13:59:42 +0000 (UTC) (envelope-from stefan.haller@stha.de) Received: from mail.stha.de (mail.stha.de [IPv6:2a03:4000:24:7d0:100::15]) by deponia.stha.de (Postfix) with ESMTPS id BF7F611236B for ; Mon, 19 Apr 2021 13:59:40 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: stefan) by mail.stha.de (Postfix) with ESMTPSA id 7A4EF189F01 for ; Mon, 19 Apr 2021 13:59:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stha.de; s=20200509; t=1618840780; bh=271LvKRLiAUIUUq7Z+u7tMshaPSACbGyAYLKBlyNvZo=; h=Date:From:To:Subject:References:In-Reply-To:From; b=kIC3B4xANe5RypJ0WE9HYQEHM2sT03ZOdooMK5w0oZT9m5vN8zJTbPT9pofR16k4O 1blV7Terfbz23PxO9Y2nccLZIWuOhrNPEQ0fRvCDKXDVrXqtOa1PZo39MRjT9byZ8W L6MnyvKBXO2ovwC4BACZVlFsEvcisoF9P9zJFxnT3HSKtAgXNSZAalcGneOU3x5WJL m3We9Ch3BmjF2SF/8QZHim0W3wK4zhbM8dhxeCDFrubiQEtzXogtR0KexpQTEzdE7J WYXAgvXSYFAY/s07dcq+lSyvBHYN3QfmJwBPJuDF2zPhSjWi5NpYZYuYFPLImJU4hX d5tKMMSXwBhfQ== Date: Mon, 19 Apr 2021 15:59:39 +0200 From: Stefan Haller To: freebsd-arm@freebsd.org Subject: Re: RPi 4B USB 3 support appears to still be broken in 13.0-RELEASE Message-ID: <10b8cbd7-e426-4096-86ed-7f4629b37db2@stha.de> References: <6D2C75DF-796D-4CC9-9740-A8C15C6A6154@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4FP7jV4Y0yz4RWS X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=stha.de header.s=20200509 header.b=kIC3B4xA; dmarc=pass (policy=none) header.from=stha.de; spf=pass (mx1.freebsd.org: domain of stefan.haller@stha.de designates 2001:8d8:1801:133::1 as permitted sender) smtp.mailfrom=stefan.haller@stha.de X-Spamd-Result: default: False [-2.12 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[stha.de:s=20200509]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RBL_SENDERSCORE_FAIL(0.00)[2001:8d8:1801:133::1:server fail]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2001:8d8:1801:133::1:from:127.0.2.255]; DKIM_TRACE(0.00)[stha.de:+]; DMARC_POLICY_ALLOW(-0.50)[stha.de,none]; NEURAL_SPAM_SHORT(0.88)[0.876]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:8d8:1801:133::1:from]; ASN(0.00)[asn:8560, ipnet:2001:8d8::/32, country:DE]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-Mailman-Approved-At: Mon, 19 Apr 2021 14:17:01 +0000 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: Mon, 19 Apr 2021 13:59:44 -0000 Hi, I just wanted to add one more data point I observed myself. On Sun, Apr 18, 2021 at 07:42:15PM +0200, Robert Clausecker wrote: > This is getting super strange. The > problem seems to occur only in this specific combination: > > * the specific drive I have > * attached to a USB 3 port > * on the Raspberry Pi 4 > * trying to import a zpool from the drive I had a similar error on my RPi 4B as described in the initial post when using ZFS _on GELI_ on an USB3 attached SATA-SSD. After switching to plain ZFS on USB3 on the same device it magically started working. ZFS on GELI was only working on the USB2 ports. Maybe the errors are related? My dmesg dump from the time when it was not working: > ugen0.3: at usbus0 > umass0 on uhub0 > umass0: on usbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number xxxxxxxxxxxx > da0: 400.000MB/s transfers > da0: 457862MB (937703088 512 byte sectors) > da0: quirks=0x2 > GEOM_ELI: Device da0.eli created. > GEOM_ELI: Encryption: AES-CBC 128 > GEOM_ELI: Crypto: software > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 13 2a 29 a6 00 00 07 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 13 2a 29 a6 00 00 07 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da0:umass-sim0:0:0:0): Retrying command, 2 more tries remain > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 08 80 20 36 00 00 07 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error As I said, I switched to plain ZFS on the USB3 attached disk and everything works. (I am using ZFS encryption available since FreeBSD 13 without issues.) Kind regards, Stefan