From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@lists.yoctoproject.org, Ross Burton <ross.burton@arm.com>
Subject: Re: [poky] [PATCH] parselogs-ignores-genericarm64.txt: add error messages from rockpi4b
Date: Thu, 9 Oct 2025 09:09:52 +0300 [thread overview]
Message-ID: <aOdRsDDPMOKaDQ24@nuoska> (raw)
In-Reply-To: <032b5d106d0cbe940213f9721fb685da0cb550c6.camel@linuxfoundation.org>
Hi,
On Wed, Oct 08, 2025 at 03:18:04PM +0100, Richard Purdie wrote:
> On Wed, 2025-10-08 at 16:28 +0300, Mikko Rapeli via lists.yoctoproject.org wrote:
> > On Thu, Sep 18, 2025 at 03:12:30PM +0300, Mikko Rapeli wrote:
> > > Rockchip rk3399 based rockpi4b with open source firmware from
> > > meta-ts https://gitlab.com/Linaro/trustedsubstrate/meta-ts
> > > triggers some non-fatal errors from various drivers.
> > > Ignore them for now since all other oeqa runtime tests pass.
> > >
> > > https://ledge.validation.linaro.org/scheduler/job/119422
> >
> > Any possibility to get this merged? In these tests
> > I don't control what firmware the devices have and thus
> > there can be errors like this. If I would also build the
> > u-boot firmware with genericarm64 then I could possibly
> > fix these issues, but that's not in the plans.
> >
> > I would like to submit similar workarounds for AMD zcu102,
> > TI am62p5, Broadcom rpi4, NXP imx8mp and Qualcomm rb3gen2.
> >
> > Cheers,
> >
> > -Mikko
> >
> > > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > > ---
> > > �.../oeqa/runtime/cases/parselogs-ignores-genericarm64.txt�� | 6 ++++++
> > > �1 file changed, 6 insertions(+)
> > >
> > > diff --git a/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt b/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
> > > index 3e96a172da..7d360bdbda 100644
> > > --- a/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
> > > +++ b/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
> > > @@ -9,3 +9,9 @@ Error applying setting, reverse things back
> > > �Can't lookup blockdev
> > > �# X11 fails to start without connected display
> > > �modeset(0): failed to set mode: Invalid argument
> > > +memory-controller: probe with driver rk3399-dmc-freq failed with error
> > > +probe with driver rockchip-pcie failed with error
> > > +platform hdmi-sound: deferred probe pending: asoc-simple-card: parse error
> > > +deferred probe pending: rockchip-spi: Failed to request optional TX DMA channel
> > > +platform sound: deferred probe pending: asoc-audio-graph-card: parse error
> > > +platform sound-dit: deferred probe pending: asoc-audio-graph-card: parse error
>
> Perhaps resend adding a comment documenting which boards/firmwares
> these are from and then I'll agree to merge?
Good idea, I'll send a v2 with that info.
Cheers,
-Mikko
prev parent reply other threads:[~2025-10-09 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 12:12 [PATCH] parselogs-ignores-genericarm64.txt: add error messages from rockpi4b Mikko Rapeli
2025-10-08 13:28 ` Mikko Rapeli
2025-10-08 14:18 ` [poky] " Richard Purdie
2025-10-09 6:09 ` Mikko Rapeli [this message]
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=aOdRsDDPMOKaDQ24@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=poky@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.