From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Enrico Jörns" <ejo@pengutronix.de>,
openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>, yocto@pengutronix.de
Subject: Re: [yocto] [PATCH v7 0/7] Add barebox bootloader support (and testing)
Date: Tue, 01 Oct 2024 15:56:10 +0100 [thread overview]
Message-ID: <99df937c036d57a532b29851ffe7d0055d35d83f.camel@linuxfoundation.org> (raw)
In-Reply-To: <92a6efc1-51a0-4153-b894-581fbe868595@pengutronix.de>
On Tue, 2024-10-01 at 16:35 +0200, Ahmad Fatoum wrote:
> Hi,
>
> On 20.09.24 12:37, Enrico Jörns wrote:
> > Am Donnerstag, dem 19.09.2024 um 21:56 +0100 schrieb Richard Purdie:
> > > This looked better in testing, thanks. There was:
> > >
> > > https://valkyrie.yoctoproject.org/#/builders/23/builds/168/steps/14/logs/stdio
> > >
> > > which is from oe-selftest on an ARM server though :/
> >
> > Thank you for the test log!>
> > I'll try to figure out why it works in my test setup but doesn't in the autobuilder..
> > Not sure if I'll have the chance to reproduce it on an ARM host.
>
> I tried reproducing the breakage on a Librecomputer Alta (Cortex-A73/A53) with Debian 12
> for arm64, but without success. Details below.
>
> I applied this series on top of commit
>
> 4fc8427a6c ("systemd: make home directory readable by systemd-coredump")
>
> > Barebox doesn't seem to boot at all (or output is missing) and U-Boot got stuck.
>
> Both barebox' oe-selftest:
>
> a3f@hass:~/poky/build$ oe-selftest -r barebox -v -v -v -K
> [1] 257856
> 2024-09-27 15:06:52,672 - oe-selftest - INFO - Adding layer libraries:
> 2024-09-27 15:06:52,672 - oe-selftest - INFO - /home/a3f/poky/meta/lib
> 2024-09-27 15:06:52,673 - oe-selftest - INFO - /home/a3f/poky/meta-yocto-bsp/lib
> 2024-09-27 15:06:52,674 - oe-selftest - INFO - /home/a3f/poky/meta-selftest/lib
> 2024-09-27 15:06:52,680 - oe-selftest - INFO - Checking base configuration is valid/parsable
> NOTE: Starting bitbake server...
> 2024-09-27 15:06:59,982 - oe-selftest - INFO - Adding: "include selftest.inc" in /home/a3f/poky/build-st/conf/local.conf
> 2024-09-27 15:06:59,983 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
> 2024-09-27 15:06:59,985 - oe-selftest - INFO - test_boot_barebox (barebox.BareboxTest.test_boot_barebox)
> 2024-09-27 15:07:00,024 - oe-selftest - DEBUG - Writing to: /home/a3f/poky/build-st/conf/selftest.inc
>
> QB_DEFAULT_KERNEL = "barebox-dt-2nd.img"
> PREFERRED_PROVIDER_virtual/bootloader = "barebox"
>
>
> 2024-09-27 15:23:54,349 - oe-selftest - INFO - ... ok
> 2024-09-27 15:23:54,357 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2024-09-27 15:23:54,358 - oe-selftest - INFO - Ran 1 test in 1019.863s
> 2024-09-27 15:23:54,359 - oe-selftest - INFO - OK
> 2024-09-27 15:24:08,447 - oe-selftest - INFO - RESULTS:
> 2024-09-27 15:24:08,450 - oe-selftest - INFO - RESULTS - barebox.BareboxTest.test_boot_barebox: PASSED (1014.37s)
> 2024-09-27 15:24:08,513 - oe-selftest - INFO - SUMMARY:
> 2024-09-27 15:24:08,514 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 1019.866s
> 2024-09-27 15:24:08,515 - oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0)
>
> and U-Boot's conclude successfully:
>
> a3f@hass:~/poky/build$ oe-selftest -r uboot -v -v -v -K
> 2024-09-30 10:41:21,225 - oe-selftest - INFO - Adding layer libraries:
> 2024-09-30 10:41:21,225 - oe-selftest - INFO - /home/a3f/poky/meta/lib
> 2024-09-30 10:41:21,225 - oe-selftest - INFO - /home/a3f/poky/meta-yocto-bsp/lib
> 2024-09-30 10:41:21,226 - oe-selftest - INFO - /home/a3f/poky/meta-selftest/lib
> 2024-09-30 10:41:21,229 - oe-selftest - INFO - Checking base configuration is valid/parsable
> NOTE: Starting bitbake server...
> 2024-09-30 10:41:24,120 - oe-selftest - INFO - Adding: "include selftest.inc" in /home/a3f/poky/build-st/conf/local.conf
> 2024-09-30 10:41:24,125 - oe-selftest - INFO - Adding: "include bblayers.inc" in bblayers.conf
> 2024-09-30 10:41:24,131 - oe-selftest - INFO - test_boot_uboot (uboot.UBootTest.test_boot_uboot)
> 2024-09-30 10:41:24,214 - oe-selftest - DEBUG - Writing to: /home/a3f/poky/build-st/conf/selftest.inc
>
> QB_DEFAULT_BIOS = "u-boot.bin"
> PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
>
>
> 2024-09-30 10:52:59,680 - oe-selftest - INFO - ... ok
> 2024-09-30 10:52:59,692 - oe-selftest - INFO - ----------------------------------------------------------------------
> 2024-09-30 10:52:59,693 - oe-selftest - INFO - Ran 1 test in 696.374s
> 2024-09-30 10:52:59,695 - oe-selftest - INFO - OK
> 2024-09-30 10:53:13,581 - oe-selftest - INFO - RESULTS:
> 2024-09-30 10:53:13,584 - oe-selftest - INFO - RESULTS - uboot.UBootTest.test_boot_uboot: PASSED (695.55s)
> 2024-09-30 10:53:13,647 - oe-selftest - INFO - SUMMARY:
> 2024-09-30 10:53:13,648 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 696.378s
> 2024-09-30 10:53:13,649 - oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=1, skipped=0, failures=0, errors=0)
>
>
> > U-Boot log in the failed test says
> >
> > > U-Boot 2024.07 (Jul 01 2024 - 18:07:18 +0000)
> > > DRAM: 256 MiB
> > > Core: 51 devices, 14 uclasses, devicetree: board
> > > Flash: 64 MiB
> > > Loading Environment from Flash... *** Warning - bad CRC, using default environment
> > > In: serial,usbkbd
> > > Out: serial,vidconsole
> > > Err: serial,vidconsole
> > > Bus xhci_pci: Register 8001040 NbrPorts 8
> > > Starting the controller
> >
> > While my successful run goes further:
> >
> > > [...]
> > > Starting the controller
> > > USB XHCI 1.00
> > > scanning bus xhci_pci for devices... 3 USB Device(s) found
> > > Net: eth0: virtio-net#32
> > > ESC[?25h
> > > Hit any key to stop autoboot: 2
> >
> > But not sure if this is an issue with USB emulation or something else...
>
> My successful run looks identical to yours. barebox start up is also
> successful and uneventful.
>
> Note that barebox' XHCI driver doesn't have PCI support unlike U-Boot, so
> if the same issue is affecting both barebox and U-Boot breakage in CI,
> it might not be USB emulation related as barebox doesn't do any
> USB on that platform...
>
> Is `selftest -r uboot -v -v -v -K` close enough to what the CI server runs
> or should I try something else to reproduce this?
That should have worked. "selftest -r barebox" should also fail.
The config used on the autobuilder for that can be seen here:
https://valkyrie.yoctoproject.org/#/builders/23/builds/168/steps/13/logs/stdio
in case the MACHINE value in particular makes a difference.
Cheers,
Richard
next prev parent reply other threads:[~2024-10-01 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 12:06 [PATCH v7 0/7] Add barebox bootloader support (and testing) Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 1/7] barebox: add initial support Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 2/7] barebox-tools: add initial barebox tools support Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 3/7] barebox: set default BAREBOX_CONFIG for qemu machines Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 4/7] oeqa/utils/qemurunner: support ignoring vt100 escape sequences Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 5/7] oeqa: support passing custom boot patterns to runqemu Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 6/7] oeqa/selftest/cases: add basic u-boot test Enrico Jörns
2024-09-19 12:06 ` [PATCH v7 7/7] oeqa/selftest/cases: add basic barebox tests Enrico Jörns
2024-09-19 20:56 ` [PATCH v7 0/7] Add barebox bootloader support (and testing) Richard Purdie
2024-09-20 10:37 ` Enrico Jörns
2024-10-01 14:35 ` [yocto] " Ahmad Fatoum
2024-10-01 14:56 ` Richard Purdie [this message]
2024-10-02 8:17 ` Ahmad Fatoum
2024-10-04 10:14 ` Ahmad Fatoum
2024-10-09 6:45 ` Ahmad Fatoum
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=99df937c036d57a532b29851ffe7d0055d35d83f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=a.fatoum@pengutronix.de \
--cc=alex.kanavin@gmail.com \
--cc=ejo@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@pengutronix.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