Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Aug 2024 18:44:15 +0530
From:      "Kamal R. Prasad" <kamalpr@gmail.com>
To:        herbert@gojira.at
Cc:        freebsd-arm@freebsd.org
Subject:   Re: SD card timeouts on older Raspberry Pi 4 models on 14.1-BETA
Message-ID:  <CAK=yUGJ_4RLYsyzyP%2BaiarVEzHsKeOjfhsD-1AELXFsjPnzyWQ@mail.gmail.com>
In-Reply-To: <8734notn15.wl-herbert@gojira.at>
References:  <FFA1B17F-A105-4610-A87B-28CA4A1260F4@karels.net> <8734notn15.wl-herbert@gojira.at>

next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000008b2968061e9efd18
Content-Type: text/plain; charset="UTF-8"

I had a similar problem on an eMMC card. The problem was that during boot
up, a large contiguous block was being fetched and the kernel could handle
only blocks of a certain block size. Hope this helps.

Thanks
-kamal

On Thu, Aug 1, 2024, 18:31 Herbert J. Skuhra <herbert@gojira.at> wrote:

> On Tue, 07 May 2024 18:50:38 +0200, Mike Karels wrote:
> >
> > I tried to install 14.1-BETA1 on one of the first-generation Raspberry
> Pi 4
> > systems.  The kernel loads and starts, but is unable to mount the root
> file
> > system due to timeout errors like this:
> >
> > sdhci_bcm1-slot0: Controller timeout
> > [register dump]
> > mmcsd0: Error indicated: 1 Timeout
> > [several timeouts later]
> > Mounting from ufs:/dev/ufs/rootfs failed with error 19.
> >
> > Mark Millard also saw the error on a similar-vintage RPi4, but not on a
> newer
> > model (C0T).  The EEPROM had been updated on his older RPi4 recently; my
> > EEPROM was updated a year or so ago.  My RPi3 boots also; it seems to use
> > the same driver for the sdhci.   I have used the same SD card for both
> BETA1
> > and a recent snapshot of -current, with only BETA1 failing.  If I recall
> > correctly, 14.0 worked on the SD card too.
> >
> > I tested several recent snapshots of -current, and they seemed to work
> without
> > problems.  I haven't noticed relevant differences between 14.1 and
> -current,
> > e.g. the sdhci controller driver, but something must be different.
> Anyone have
> > an idea, or suggestion on where to look?  It would be nice to resolve
> this
> > before 14.1-RELEASE.
> >
> >               Mike
> >
> > Excerpts from the boot log:
> >
> > sdhci_bcm1: <Broadcom 2708 SDHCI controller> mem 0x7e340000-0x7e3400ff
> irq 79 on simplebus1
> > mmc1: <MMC/SD bus> on sdhci_bcm1
> > ...
> > mmcsd0: 63GB <SDHC ASTC 0.0 SN 000002D9 MFG 09/2022 by 159 TI> at mmc1
> 50.0MHz/4bit/65535-block
> > ...
> > sdhci_bcm1-slot0: Controller timeout
> > sdhci_bcm1-slot0: ============== REGISTER DUMP ==============
> > sdhci_bcm1-slot0: Sys addr: 0x000000c8 | Version:  0x00001002
> > sdhci_bcm1-slot0: Blk size: 0x00000200 | Blk cnt:  0x00000001
> > sdhci_bcm1-slot0: Argument: 0x0747afff | Trn mode: 0x00000012
> > sdhci_bcm1-slot0: Present:  0x1fff0a06 | Host ctl: 0x00000007
> > sdhci_bcm1-slot0: Power:    0x0000000f | Blk gap:  0x00000080
> > sdhci_bcm1-slot0: Wake-up:  0x00000000 | Clock:    0x00000107
> > sdhci_bcm1-slot0: Timeout:  0x00000003 | Int stat: 0x00000021
> > sdhci_bcm1-slot0: Int enab: 0x01ff003b | Sig enab: 0x01ff0008
> > sdhci_bcm1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000
> > sdhci_bcm1-slot0: Caps:     0x45ee6432 | Caps2:    0x0000a525
> > sdhci_bcm1-slot0: Max curr: 0x00080008 | ADMA err: 0x00000000
> > sdhci_bcm1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000
> > sdhci_bcm1-slot0: ===========================================
> > mmcsd0: Error indicated: 1 Timeout
> > ...
> > mmcsd0: Error indicated: 1 Timeout
> > mountroot: waiting for device /dev/ufs/rootfs...
> > Mounting from ufs:/dev/ufs/rootfs failed with error 19.
>
> Could you resolve this issue?
>
> I am running stable/14-n268234-f5fabf3dcfb on my Raspberry Pi 4 and
> have the same issue after updating U-Boot from 2024.01 to 2024.04. :-(
>
> Do I/we need a newer firmware?
>
>

--0000000000008b2968061e9efd18
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I had a similar problem on an eMMC card. The problem was tha=
t during boot up, a large contiguous block was being fetched and the kernel=
 could handle only blocks of a certain block size. Hope this helps.</p>
<p dir=3D"ltr">Thanks<br>
-kamal<br>
</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu=
, Aug 1, 2024, 18:31 Herbert J. Skuhra &lt;<a href=3D"mailto:herbert@gojira=
.at">herbert@gojira.at</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">On Tue, 07 May 2024 18:50:38 +0200, Mike Karels wrote:<br>
&gt; <br>
&gt; I tried to install 14.1-BETA1 on one of the first-generation Raspberry=
 Pi 4<br>
&gt; systems.=C2=A0 The kernel loads and starts, but is unable to mount the=
 root file<br>
&gt; system due to timeout errors like this:<br>
&gt; <br>
&gt; sdhci_bcm1-slot0: Controller timeout<br>
&gt; [register dump]<br>
&gt; mmcsd0: Error indicated: 1 Timeout<br>
&gt; [several timeouts later]<br>
&gt; Mounting from ufs:/dev/ufs/rootfs failed with error 19.<br>
&gt; <br>
&gt; Mark Millard also saw the error on a similar-vintage RPi4, but not on =
a newer<br>
&gt; model (C0T).=C2=A0 The EEPROM had been updated on his older RPi4 recen=
tly; my<br>
&gt; EEPROM was updated a year or so ago.=C2=A0 My RPi3 boots also; it seem=
s to use<br>
&gt; the same driver for the sdhci.=C2=A0 =C2=A0I have used the same SD car=
d for both BETA1<br>
&gt; and a recent snapshot of -current, with only BETA1 failing.=C2=A0 If I=
 recall<br>
&gt; correctly, 14.0 worked on the SD card too.<br>
&gt; <br>
&gt; I tested several recent snapshots of -current, and they seemed to work=
 without<br>
&gt; problems.=C2=A0 I haven&#39;t noticed relevant differences between 14.=
1 and -current,<br>
&gt; e.g. the sdhci controller driver, but something must be different.=C2=
=A0 Anyone have<br>
&gt; an idea, or suggestion on where to look?=C2=A0 It would be nice to res=
olve this<br>
&gt; before 14.1-RELEASE.<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Mike<br>
&gt; <br>
&gt; Excerpts from the boot log:<br>
&gt; <br>
&gt; sdhci_bcm1: &lt;Broadcom 2708 SDHCI controller&gt; mem 0x7e340000-0x7e=
3400ff irq 79 on simplebus1<br>
&gt; mmc1: &lt;MMC/SD bus&gt; on sdhci_bcm1<br>
&gt; ...<br>
&gt; mmcsd0: 63GB &lt;SDHC ASTC 0.0 SN 000002D9 MFG 09/2022 by 159 TI&gt; a=
t mmc1 50.0MHz/4bit/65535-block<br>
&gt; ...<br>
&gt; sdhci_bcm1-slot0: Controller timeout<br>
&gt; sdhci_bcm1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER =
DUMP =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt; sdhci_bcm1-slot0: Sys addr: 0x000000c8 | Version:=C2=A0 0x00001002<br>
&gt; sdhci_bcm1-slot0: Blk size: 0x00000200 | Blk cnt:=C2=A0 0x00000001<br>
&gt; sdhci_bcm1-slot0: Argument: 0x0747afff | Trn mode: 0x00000012<br>
&gt; sdhci_bcm1-slot0: Present:=C2=A0 0x1fff0a06 | Host ctl: 0x00000007<br>
&gt; sdhci_bcm1-slot0: Power:=C2=A0 =C2=A0 0x0000000f | Blk gap:=C2=A0 0x00=
000080<br>
&gt; sdhci_bcm1-slot0: Wake-up:=C2=A0 0x00000000 | Clock:=C2=A0 =C2=A0 0x00=
000107<br>
&gt; sdhci_bcm1-slot0: Timeout:=C2=A0 0x00000003 | Int stat: 0x00000021<br>
&gt; sdhci_bcm1-slot0: Int enab: 0x01ff003b | Sig enab: 0x01ff0008<br>
&gt; sdhci_bcm1-slot0: AC12 err: 0x00000000 | Host ctl2:0x00000000<br>
&gt; sdhci_bcm1-slot0: Caps:=C2=A0 =C2=A0 =C2=A00x45ee6432 | Caps2:=C2=A0 =
=C2=A0 0x0000a525<br>
&gt; sdhci_bcm1-slot0: Max curr: 0x00080008 | ADMA err: 0x00000000<br>
&gt; sdhci_bcm1-slot0: ADMA addr:0x00000000 | Slot int: 0x00000000<br>
&gt; sdhci_bcm1-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br>
&gt; mmcsd0: Error indicated: 1 Timeout<br>
&gt; ...<br>
&gt; mmcsd0: Error indicated: 1 Timeout<br>
&gt; mountroot: waiting for device /dev/ufs/rootfs...<br>
&gt; Mounting from ufs:/dev/ufs/rootfs failed with error 19.<br>
<br>
Could you resolve this issue?<br>
<br>
I am running stable/14-n268234-f5fabf3dcfb on my Raspberry Pi 4 and<br>
have the same issue after updating U-Boot from 2024.01 to 2024.04. :-(<br>
<br>
Do I/we need a newer firmware?<br>
<br>
</blockquote></div>

--0000000000008b2968061e9efd18--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK=yUGJ_4RLYsyzyP%2BaiarVEzHsKeOjfhsD-1AELXFsjPnzyWQ>