From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Jon Mason <jdmason@kudzu.us>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [PATCH 1/2] trusted-firmware-a: continue if TPM device is missing
Date: Wed, 24 Apr 2024 09:37:16 +0300 [thread overview]
Message-ID: <ZiionO_3d-zy5Oh1@nuoska> (raw)
In-Reply-To: <Zif8GPUamF5+3fDR@kudzu.us>
Hi,
On Tue, Apr 23, 2024 at 02:21:12PM -0400, Jon Mason wrote:
> On Mon, Apr 22, 2024 at 10:29:01AM +0300, Mikko Rapeli wrote:
> > Hi,
> >
> > On Sat, Apr 20, 2024 at 06:40:54PM -0400, Jon Mason wrote:
> > > On Wed, Apr 17, 2024 at 02:07:21PM +0300, Mikko Rapeli wrote:
> > > > All other firmware boot components also continue booting
> > > > if TPM is not found. It is up to subsequent SW components
> > > > to e.g. fail if rootfs can't be decrypted. Enables policies
> > > > like fall back to unencrypted rootfs if TPM device is
> > > > not found with qemu and swtpm.
> > > >
> > > > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > >
> > > This series is failing on all instances of qemuarm64-secureboot and
> > > qemuarm-secureboot. You can see it on my gitlab CI at:
> > > https://gitlab.com/jonmason00/meta-arm/-/pipelines/1261200728
> > >
> > > All of them appear to be due to detecting the following error (snipped
> > > from the dmesg of the errorlog):
> > > optee-ftpm optee-ta-bc50d971-d4c9-42c4-82cb-343fb7f37896: ftpm_tee_probe: tee_client_open_session failed, err=ffff3024
> > > optee-ftpm: probe of optee-ta-bc50d971-d4c9-42c4-82cb-343fb7f37896 failed with error -22
> >
> > Bummer, checking what I missed here.
> >
> > Did optee-test/xtest run and possibly pass despite of this? I don't see this from the logs.
>
> optee-test is only being compiled, not being run as part of CI
> (patches very much wanted and welcomed). So, nothing exciting here
> except the kernel trying to load the modules and erroring out.
Ok. I managed to reproduce this issue and also saw that optee-test xtest was
failing on the core-image-base. The image needs
IMAGE_INSTALL:append = " optee-client optee-os-ta optee-test"
and then optee-test/xtest passes. So optee itself is working and fine.
What exact config and commands does the CI job run? I could provide
the patches for optee-test/xtest.
Looking into the ftpm kernel error now...
Cheers,
-Mikko
next prev parent reply other threads:[~2024-04-24 6:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 11:07 [PATCH 1/2] trusted-firmware-a: continue if TPM device is missing Mikko Rapeli
2024-04-17 11:07 ` [PATCH 2/2] optee-ftpm: enumerate also without tee-supplicant Mikko Rapeli
2024-04-22 8:02 ` [meta-arm] " Sumit Garg
2024-04-22 8:13 ` Mikko Rapeli
2024-04-30 12:44 ` Mikko Rapeli
2024-04-20 22:40 ` [PATCH 1/2] trusted-firmware-a: continue if TPM device is missing Jon Mason
2024-04-22 7:29 ` Mikko Rapeli
2024-04-23 18:21 ` Jon Mason
2024-04-24 6:37 ` Mikko Rapeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-30 12:37 [PATCH v2 0/6] TPM and fTPM test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 1/6] trusted-firmware-a: continue if TPM device is missing Mikko Rapeli
2024-04-30 12:37 ` [PATCH 2/6] optee-os: inrease heap size with fTPM Mikko Rapeli
2024-04-30 12:37 ` [PATCH 3/6] oeqa runtime: add optee.py test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 4/6] oeqa runtime: add ftpm.py test Mikko Rapeli
2024-04-30 12:37 ` [PATCH 5/6] ci/qemuarm64-secureboot.yml: install optee and test both optee and ftpm Mikko Rapeli
2024-04-30 12:37 ` [PATCH 6/6] ci/qemuarm-secureboot.yml: " Mikko Rapeli
2024-05-01 2:06 ` [PATCH v2 0/6] TPM and fTPM test Jon Mason
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=ZiionO_3d-zy5Oh1@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=jdmason@kudzu.us \
--cc=meta-arm@lists.yoctoproject.org \
/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.