mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Stafford Horne <shorne@gmail.com>,
	Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/3] ci: container: downgrade OpenRISC toolchain from 14.2.0 to 13.1.0
Date: Wed, 14 Aug 2024 18:14:35 +0200	[thread overview]
Message-ID: <20240814161435.566270-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240814161435.566270-1-a.fatoum@pengutronix.de>

The newest toolchain bump breaks OpenRISC start-up under QEMU: The console is
now completely silent. Steps to reproduce the hang:

  CONTAINER_GCC13=bdfdd5effcc169ebf8a9df2f1a5956ef34549682f78b450a97aceea2afd76f7a
  CONTAINER_GCC14=fa35adeae1ab49b4dc09fc3bf4d68f92541a0d1f41e0df91a4879fd331e4b592
  CONTAINER_BASE=ghcr.io/barebox/barebox/barebox-ci@sha256:fa35adeae1a

  export CONTAINER=${CONTAINER_BASE}@sha256:${CONTAINER_GCC14}
  export LG_BUILDDIR=build-openrisc
  ./scripts/container.sh ./MAKEALL -a openrisc -O $LG_BUILDDIR
  ./scripts/container.sh pytest --lg-env test/openrisc/generic_defconfig.yaml \
	--interactive

Running the same steps, but with the older toolchain boots successfully:

  export CONTAINER=${CONTAINER_BASE}@sha256:${CONTAINER_GCC13}
  export LG_BUILDDIR=build-openrisc
  git checkout v2024.08.0
  ./scripts/container.sh ./MAKEALL -a openrisc -O $LG_BUILDDIR
  ./scripts/container.sh pytest --lg-env test/openrisc/generic_defconfig.yaml \
	--interactive

The hang happens somewhere before the jump to _start in arch/openrisc/cpu/start.S.
Until that's fixed, let's pin the OpenRISC GCC version to the old v13.1.0.

Cc: Stafford Horne <shorne@gmail.com>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
@Stafford, do you have an idea what could cause this?
---
 test/Containerfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/Containerfile b/test/Containerfile
index fe3e3a6186b0..aca2c5fcde81 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -56,7 +56,7 @@ RUN korg_crosstool_dl() { wget -nv -O - https://mirrors.edge.kernel.org/pub/tool
     korg_crosstool_dl x86_64 ${GCC_VERSION} arm-linux-gnueabi && \
     korg_crosstool_dl x86_64 ${GCC_VERSION} aarch64-linux     && \
     korg_crosstool_dl x86_64 ${GCC_VERSION} mips-linux        && \
-    korg_crosstool_dl x86_64 ${GCC_VERSION} or1k-linux        && \
+    korg_crosstool_dl x86_64 13.1.0         or1k-linux        && \
     korg_crosstool_dl x86_64 ${GCC_VERSION} powerpc-linux     && \
     korg_crosstool_dl x86_64 ${GCC_VERSION} riscv64-linux
 
-- 
2.39.2




  parent reply	other threads:[~2024-08-14 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 16:14 [PATCH 1/3] debug_ll: ns16550: fix prototype in documentation comment Ahmad Fatoum
2024-08-14 16:14 ` [PATCH 2/3] openrisc: implement C debug_ll for NS16550 Ahmad Fatoum
2024-08-14 16:14 ` Ahmad Fatoum [this message]
2024-08-15  8:49   ` (subset) [PATCH 3/3] ci: container: downgrade OpenRISC toolchain from 14.2.0 to 13.1.0 Sascha Hauer
2024-08-18  7:14   ` Stafford Horne
2024-08-18 17:09     ` Ahmad Fatoum
2024-08-22 16:43       ` Ahmad Fatoum
2024-08-23  6:21         ` Stafford Horne
2024-08-15  8:50 ` (subset) [PATCH 1/3] debug_ll: ns16550: fix prototype in documentation comment Sascha Hauer

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=20240814161435.566270-3-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=shorne@gmail.com \
    /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