Date: Fri, 16 Apr 2021 18:58:12 -0700 From: Vincent Milum Jr <freebsd-arm@darkain.com> To: Robert Clausecker <fuz@fuz.su> Cc: freebsd-arm@freebsd.org Subject: Re: RPi 4B USB 3 support appears to still be broken in 13.0-RELEASE Message-ID: <CAOWUMWGvYBZmMo1OVfsHQ6OohBOpQy5_n%2B0T5BeKWvqowBQQiA@mail.gmail.com> In-Reply-To: <YHoXAS%2B0/ptwL0IS@fuz.su> References: <YHoXAS%2B0/ptwL0IS@fuz.su>
next in thread | previous in thread | raw e-mail | index | archive | help
What's the power source for the hard drive? From your bug tracker link, it looks like this is a SSD of some kind, not a USB thumb drive. It is possible that the drive is pulling too much power for the Pi's USB port to handle. Remember that the Pi's power source is ALSO a USB port, so that power is then shared between both the Pi as well as any devices plugged into it. Power brownouts from pulling too much power on the Pi can present themselves in a number of ways, including CAM errors for disks. On Fri, Apr 16, 2021 at 4:00 PM Robert Clausecker <fuz@fuz.su> wrote: > Greetings! > > Last time I experimented with ZFS on the RPi 4B, I noticed that > there is a strange problem when attaching the zpool via USB 3 as > opposed to USB 2. When doing that, mounting root fails with > IO errors like these: > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 03 c1 b9 65 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 03 c1 b9 65 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 > > Attaching the boot disk through USB 2 instead works. Likewise, > using USB 3 with a UFS root file system works (and in fact ran fine > in a development system for months). I do not understand this. > > I had previously reported this issue as PR 249520: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249520 > > There's some stuff about UEFI booting in there which you can ignore. > The same problem also appears when booting via U-Boot. > > Now what surprises me is that this issue still occurs with > FreeBSD 13.0-RELEASE. So whatever fixes had been performed > did not seem to address the underlying problem at all. > > Is there any workaround or solution (except for ditching root > on ZFS which would be rather painful for my use case?) > > Yours, > Robert Clausecker > > -- > () ascii ribbon campaign - for an 8-bit clean world > /\ - against html email - against proprietary attachments > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOWUMWGvYBZmMo1OVfsHQ6OohBOpQy5_n%2B0T5BeKWvqowBQQiA>