Date: Sun, 16 Oct 2022 00:00:01 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: FYI: Rock64 USB3 port no longer works for main [so: 14] Message-ID: <8A639ABB-D8CC-47D6-A106-A5E2463E7AEE@yahoo.com> References: <8A639ABB-D8CC-47D6-A106-A5E2463E7AEE.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Unfortunately, last I recorded the Rock64 console output
goes back to 2022-Apr --for an even older system build:
main-n252475-e76c0108990b-dirty
(a 2022-Jan-16 commit). The build with the observed USB3
problem is (the USB3 NVMe SSD booted on a RPi3B instead):
# uname -apKU
FreeBSD Rock64_RPi_4_3_2v1p2 14.0-CURRENT FreeBSD 14.0-CURRENT #46 =
main-n258610-ba7319e9091b-dirty: Fri Oct 14 16:35:36 PDT 2022 =
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA53-nodbg-clang/usr/main-src/arm6=
4.aarch64/sys/GENERIC-NODBG-CA53 arm64 aarch64 1400072 1400072
Note that some differences in boot-text reported below may
well be expected text. I do not have the context to evaluate
most text for good vs. bad. The differences avoid reporting
identical text and irrelevant minor variations.
Newer, failing context:
snps_dwc3_fdt0: <Synopsys Designware DWC3> mem 0xff600000-0xff6fffff irq =
58 on rk_dwc30
snps_dwc3_fdt0: 64 bytes context size, 32-bit DMA
usbus4: trying to attach
usbus4 on snps_dwc3_fdt0
Older, working context:
xhci0: <Synopsys Designware DWC3> mem 0xff600000-0xff6fffff irq 58 on =
rk_dwc30
xhci0: 64 bytes context size, 32-bit DMA
usbus4: trying to attach
usbus4 on xhci0
Later, a block that is the same for both:
ugen4.1: <Synopsys XHCI root HUB> at usbus4
uhub3 on usbus4
uhub3: <Synopsys XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on =
usbus4
Later, a block only in the older working context:
Root mount waiting for: usbus4 CAM
ugen4.2: <Samsung PSSD T7 Touch> at usbus4
umass0 on uhub3
umass0: <Samsung PSSD T7 Touch, class 0/0, rev 3.20/1.00, addr 1> on =
usbus4
umass0: SCSI over Bulk-Only; quirks =3D 0x0000
umass0:0:0: Attached to scbus0
Then both got:
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
Root mount waiting for: CAM
But the failure then got:
Root mount waiting for: CAM
Root mount waiting for: CAM
Mounting from ufs:/dev/gpt/Rock64root failed with error 22; retrying for =
3 more seconds
Mounting from ufs:/dev/gpt/Rock64root failed with error 22: Invalid =
fstype.
Loader variables:
vfs.root.mountfrom=3Dufs:/dev/gpt/Rock64root
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot>=20
Booting from USB2 instead and later plugging a USB3 device
into the USB3 port gives no indication of activity (via the
activity light on the USB3 device).
With this, I have stopped maintaining an environment for the
Rock64. I will not be pursuing the above issue.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A639ABB-D8CC-47D6-A106-A5E2463E7AEE>