lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACdvmAi3JbdLstkudF=Fb_O_P1GGADuubKVS6s22hvC93qz3tg@mail.gmail.com>
Date: Tue, 6 May 2025 09:42:13 -0400
From: Da Xue <da@...sconfused.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: Christian Hewitt <christianshewitt@...il.com>, Neil Armstrong <neil.armstrong@...aro.org>, 
	Kevin Hilman <khilman@...libre.com>, Jerome Brunet <jbrunet@...libre.com>, 
	Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, 
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: sm1-bananapi: lower SD card speed
 for stability

On Tue, May 6, 2025 at 2:26 AM Martin Blumenstingl
<martin.blumenstingl@...glemail.com> wrote:
>
> On Mon, May 5, 2025 at 4:37 PM Christian Hewitt
> <christianshewitt@...il.com> wrote:
> >
> > Users report being able to boot (u-boot) from SD card but kernel
> > init then fails to mount partitions on the card containing boot
> > media resulting in first-boot failure. System logs show only the
> > probe of the mmc devices: the SD card is seen, but no partitions
> > are found so init fails to mount them and boot stalls.
> >
> > Reducing the speed of the SD card from 50MHz to 35MHz results in
> > complete probing of the card and successful boot.
> >
> > Signed-off-by: Christian Hewitt <christianshewitt@...il.com>
> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
>
> > ---
> > The same workaround of dropping to 35MHz is also done with the
> > ac2xx dtsi; which has a comment about CRC errors being seen at
> > 50MHz. It's probable this is the same although I forget now how
> > that diagnosis was done (or who did it, Martin perhaps?).
> Maybe Jerome helped investigate/debug? I can't recall and at the same
> time: if it fixes the end user experience it's a win.

We had an issue too and ended up disabling MMC_MODE_HS_52MHz | MMC_MODE_HS;

>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ