Date: Thu, 5 Nov 2020 07:45:29 +0100 From: Michal Meloun <meloun.michal@gmail.com> To: freebsd-arm@freebsd.org Subject: Re: growfs triggering sdhc errors Message-ID: <6780ae20-de0b-62ce-4090-43e1cb3f87d3@freebsd.org> In-Reply-To: <a12657b0-4964-9a78-bf67-6bf1795ace67@FreeBSD.org> References: <2724d1d4-58a1-eef2-c6bb-ce1be0fa3123@FreeBSD.org> <5f443e74-5e55-c8b2-f4c2-ea0034437aa0@FreeBSD.org> <a12657b0-4964-9a78-bf67-6bf1795ace67@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.11.2020 3:01, Steve Wills wrote: > Hi, > > I seem to have narrowed this down to r366106. With commits before that, > growfs works fine. After, it gives these errors. This seems to have been > discovered already tho: > > https://lists.freebsd.org/pipermail/svn-src-head/2020-November/141284.html > > And yet, so for, no response. I will try the proposed patch. > > Steve > This problem should be fixed in another way by r367268. Can you, please, test a fresh current? Michal > On 11/3/20 6:39 PM, Steve Wills wrote: >> 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" >> _______________________________________________ >> 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" > _______________________________________________ > 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?6780ae20-de0b-62ce-4090-43e1cb3f87d3>