Date: Tue, 3 Nov 2020 18:39:33 -0500 From: Steve Wills <swills@FreeBSD.org> To: freebsd-arm@freebsd.org Subject: Re: growfs triggering sdhc errors Message-ID: <5f443e74-5e55-c8b2-f4c2-ea0034437aa0@FreeBSD.org> In-Reply-To: <2724d1d4-58a1-eef2-c6bb-ce1be0fa3123@FreeBSD.org> References: <2724d1d4-58a1-eef2-c6bb-ce1be0fa3123@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Just to add a little more detail here, the exact output of growfs is: https://reviews.freebsd.org/file/data/xxwzfra5fjqqwxd7ws36/PHID-FILE-h7epoca7bcj5vurlzajf/raw-paste-data.txt I see this using the official snapshots too: FreeBSD 13.0-CURRENT FreeBSD 13.0-CURRENT #0 b9403d7aae8-c254071(main): Thu Oct 29 10:38:29 UTC 2020 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 FreeBSD-13.0-CURRENT-arm64-aarch64-RPI3-20201029-b9403d7aae8.img Note growfs is triggered on firstboot via the /etc/rc.d/growfs script and having growfs_enable="YES" in /etc/rc.conf and the /firstboot file existing. The partitions (MBR and BSD) seem to grow fine (gpart) but the growfs triggers the issue. Steve On 11/3/20 6:09 PM, Steve Wills wrote: > Hi, > > It seems that sometime between r362013 and r366608 of CURRENT, something > broke such that growfs on my RPI3 breaks with: > > sdhci_bcm0-slot0: Got data interrupt 0x00600000, but there is no active > command. > > followed by a register dump. Any ideas where to look? > > Thanks, > Steve > _______________________________________________ > 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?5f443e74-5e55-c8b2-f4c2-ea0034437aa0>