Date: Thu, 5 Nov 2020 13:19:02 -0500 From: Steve Wills <swills@FreeBSD.org> To: mmel@freebsd.org, freebsd-arm@freebsd.org Subject: Re: growfs triggering sdhc errors Message-ID: <aa2022ff-1d8a-0056-67a7-75af4de3e6c6@FreeBSD.org> In-Reply-To: <6780ae20-de0b-62ce-4090-43e1cb3f87d3@freebsd.org> References: <2724d1d4-58a1-eef2-c6bb-ce1be0fa3123@FreeBSD.org> <5f443e74-5e55-c8b2-f4c2-ea0034437aa0@FreeBSD.org> <a12657b0-4964-9a78-bf67-6bf1795ace67@FreeBSD.org> <6780ae20-de0b-62ce-4090-43e1cb3f87d3@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 11/5/20 1:45 AM, Michal Meloun wrote: > > > 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? Thanks for the reply, I've tested with r367383 but I'm still seeing the same issue, as soon as growfs runs, I get errors then continual sdhc register dumps: OK to grow filesystem on /dev/mmcsd0s2a, mounted on /, from 5.4GB to 30GB? [yes/no] yes mmcsd0: Error indicated: 6 NO MEMORY gmmcsd0: Error indicated: 1 Timeout vm_fault: pager read error, pid 34 (growfs) pid 34 (growfs), jid 0, uid 0: exited on signal 10 mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout mmcsd0: Error indicated: 1 Timeout rdfs: read error: 10258176: vm_fault: pager read error, pid 25 (sh) pid 25 (sh), jid 0, uid 0: exited on signal 10 vm_fault: pager read error, pid 1 (init) vm_fault: pager read error, pid 1 (init) sdhci_bcm0-slot0: Got data interrupt 0x00600000, but there is no active command. vm_fault: pager read error, pid 1 (init) sdhci_bcm0-slot0: ============== REGISTER DUMP ============== sdhci_bcm0-slot0: Sys addr: 0x00000000 | Version: 0x00009902 sdhci_bcm0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000040 sdhci_bcm0-slot0: Argument: 0x00657d40 | Trn mode: 0x00000036 sdhci_bcm0-slot0: Present: 0x010f0000 | Host ctl: 0x00000002 sdhci_bcm0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_bcm0-slot0: Wake-up: 0x00000000 | Clock: 0x00000207 sdhci_bcm0-slot0: Timeout: 0x0000000e | Int stat: 0x00000000 sdhci_bcm0-slot0: Int enab: 0x01ff00bb | Sig enab: 0x01ff00bb sdhci_bcm0-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000 sdhci_bcm0-slot0: Caps: 0x00000000 | Caps2: 0x00000000 sdhci_bcm0-slot0: Max curr: 0x00000001 | ADMA err: 0x00000000 sdhci_bcm0-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000 sdhci_bcm0-slot0: =========================================== Perhaps it's something local? FWIW, I'm testing on RPI3 Model B v1.2. Thanks, Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aa2022ff-1d8a-0056-67a7-75af4de3e6c6>