U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Stefan Roese <sr@denx.de>, Tom Rini <trini@konsulko.com>,
	Dennis Gilmore <dgilmore@redhat.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH v2] configs: clearfog,helios4: disable sdhci sdma
Date: Thu, 27 Feb 2025 09:43:16 +0000	[thread overview]
Message-ID: <e8bbf95a-f5e8-4b90-b092-8574478c8e9a@solid-run.com> (raw)
In-Reply-To: <51dacd62-bb7c-47cf-83ea-cd3b928b968b@denx.de>

Am 27.02.25 um 10:28 schrieb Stefan Roese:
> On 08.02.25 13:22, Josua Mayer wrote:
>> Testing has shown that loading large initramfs causes data corruption
>> where the kernel image had been loaded to.
>> Debian 12 installation using a 17M initramfs boots fine, but the final
>> system with an initramfs of 27M obscurely fails to boot with bootz
>> reporting "Bad magic!".
>> Inspecting kernel_addr_r after this failed boot attempt does show
>> garbage in place of the expected zimage header.
>>
>> The problem seems to occur on armada 388 only when sdhci sdma is enabled
>> in defconfig. Other armada boards such as turris omnia did not enable
>> the option.
>>
>> Remove sdhci sdma from defconfig for now as a workaround.
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>> ---
>> Changes in v2:
>> - changed *all* a388 clearfog_* defconfig files
>> - Link to v1: 
>> https://lore.kernel.org/r/20250208-a388-kerneladdr-v1-1-1ed91f642c2d@solid-run.com
>
> Josua, do you plan to look into this issue to perhaps fix the
> root cause at some point?
Unfortunately I won't have time to focus on this platform in depth,
with the Armada 388 soon reaching its end of life per Marvell.

Sales and management want to focus on new opportunities.

My only guess so far is the observation that environment
"loadaddr" was equal to the memory buffer address used by
CONFIG_MMC_SDHCI_SDMA

Changing it however didn't seem to resolve the issue.

I am also wondering if SPL may have the same issue,
though it never loads anything as big as kernel or ramdisk.

Anyone interested in working on this by themselves may
reach out to me with questions.

>
> For now:
>
> Reviewed-by: Stefan Roese <sr@denx.de>
Thanks!
>
> Thanks,
> Stefan
>
>> ---
>>   configs/clearfog_defconfig      | 1 -
>>   configs/clearfog_sata_defconfig | 1 -
>>   configs/clearfog_spi_defconfig  | 1 -
>>   configs/helios4_defconfig       | 1 -
>>   4 files changed, 4 deletions(-)
>>
>> diff --git a/configs/clearfog_defconfig b/configs/clearfog_defconfig
>> index 
>> 6f6597c5331f4aadf827b40a8f2864722585fda9..a139d7cb463167f59931fd4a151a309c29ba3a44 
>> 100644
>> --- a/configs/clearfog_defconfig
>> +++ b/configs/clearfog_defconfig
>> @@ -60,7 +60,6 @@ CONFIG_SYS_I2C_MVTWSI=y
>>   CONFIG_I2C_EEPROM=y
>>   CONFIG_SPL_I2C_EEPROM=y
>>   CONFIG_MMC_SDHCI=y
>> -CONFIG_MMC_SDHCI_SDMA=y
>>   CONFIG_MMC_SDHCI_MV=y
>>   CONFIG_SPI_FLASH_WINBOND=y
>>   CONFIG_SPI_FLASH_MTD=y
>> diff --git a/configs/clearfog_sata_defconfig 
>> b/configs/clearfog_sata_defconfig
>> index 
>> 491a27321f9c52af3bd28da546b7065b0aaf38e0..b927532a8c7e99632aa7c45cb809115be9524e04 
>> 100644
>> --- a/configs/clearfog_sata_defconfig
>> +++ b/configs/clearfog_sata_defconfig
>> @@ -61,7 +61,6 @@ CONFIG_I2C_EEPROM=y
>>   CONFIG_SPL_I2C_EEPROM=y
>>   CONFIG_SUPPORT_EMMC_BOOT=y
>>   CONFIG_MMC_SDHCI=y
>> -CONFIG_MMC_SDHCI_SDMA=y
>>   CONFIG_MMC_SDHCI_MV=y
>>   CONFIG_SPI_FLASH_WINBOND=y
>>   CONFIG_SPI_FLASH_MTD=y
>> diff --git a/configs/clearfog_spi_defconfig 
>> b/configs/clearfog_spi_defconfig
>> index 
>> d3de1657c09ac8afb7655094d88b649f711e36b7..85be40db48536ca153d0dae8eda69532745b5526 
>> 100644
>> --- a/configs/clearfog_spi_defconfig
>> +++ b/configs/clearfog_spi_defconfig
>> @@ -61,7 +61,6 @@ CONFIG_I2C_EEPROM=y
>>   CONFIG_SPL_I2C_EEPROM=y
>>   CONFIG_SUPPORT_EMMC_BOOT=y
>>   CONFIG_MMC_SDHCI=y
>> -CONFIG_MMC_SDHCI_SDMA=y
>>   CONFIG_MMC_SDHCI_MV=y
>>   CONFIG_SPI_FLASH_WINBOND=y
>>   CONFIG_SPI_FLASH_MTD=y
>> diff --git a/configs/helios4_defconfig b/configs/helios4_defconfig
>> index 
>> 2778cb7dc8680191155582da14a21b6a521fdef1..baf7c9396362fd9f6a8e527e27e8ad75a1fe643e 
>> 100644
>> --- a/configs/helios4_defconfig
>> +++ b/configs/helios4_defconfig
>> @@ -60,7 +60,6 @@ CONFIG_SYS_I2C_MVTWSI=y
>>   CONFIG_I2C_EEPROM=y
>>   CONFIG_SPL_I2C_EEPROM=y
>>   CONFIG_MMC_SDHCI=y
>> -CONFIG_MMC_SDHCI_SDMA=y
>>   CONFIG_MMC_SDHCI_MV=y
>>   CONFIG_SPI_FLASH_WINBOND=y
>>   CONFIG_SPI_FLASH_MTD=y
>>
>> ---
>> base-commit: ac3dcb0c2710c4917d93d6d2eb34dbfb00516bc2
>> change-id: 20250207-a388-kerneladdr-23438bb34215
>>
>> Best regards,
>
> Viele Grüße,
> Stefan Roese
>


  reply	other threads:[~2025-02-27  9:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 12:22 [PATCH v2] configs: clearfog,helios4: disable sdhci sdma Josua Mayer
2025-02-27  9:28 ` Stefan Roese
2025-02-27  9:43   ` Josua Mayer [this message]
2025-04-16 13:32 ` Stefan Roese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8bbf95a-f5e8-4b90-b092-8574478c8e9a@solid-run.com \
    --to=josua@solid-run.com \
    --cc=dgilmore@redhat.com \
    --cc=sr@denx.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox