From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@microsoft.com, linux-doc@vger.kernel.org,
corbet@lwn.net, linux-kernel@vger.kernel.org,
thiruan@microsoft.com, tee-dev@lists.linaro.org, jgg@ziepe.ca,
ilias.apalodimas@linaro.org, rdunlap@infradead.org,
linux-integrity@vger.kernel.org, peterhuewe@gmx.de,
bryankel@microsoft.com
Subject: Re: [Tee-dev] [PATCH v8 0/2] fTPM: firmware TPM running in TEE
Date: Wed, 07 Aug 2019 15:21:33 +0200 [thread overview]
Message-ID: <5707aee16681065a975ed42a06069674c3127edb.camel@pengutronix.de> (raw)
In-Reply-To: <20190711200858.xydm3wujikufxjcw@linux.intel.com>
Hi,
I spent some time with the fTPM module and TA on a Nitrogen6X with the
latest OP-TEE master. After stumbling through the "tee_supplicant no
persistent storage" problem, my module now issues the following error
message on module load:
[ 34.633252] tpm tpm0: ftpm_tee_tpm_op_send: SUBMIT_COMMAND invoke error: 0xffff0006
[ 34.641035] tpm tpm0: tpm_try_transmit: send(): error -65530
[ 34.647008] tpm tpm0: ftpm_tee_tpm_op_send: SUBMIT_COMMAND invoke error: 0xffff0006
[ 34.654788] tpm tpm0: tpm_try_transmit: send(): error -65530
[ 34.660480] ftpm-tee ftpm: ftpm_tee_probe: tpm_chip_register failed with rc=-65530
[ 34.678087] ftpm-tee: probe of ftpm failed with error -65530
To me the TEE_ERROR_BAD_PARAMETERS indicates some ABI issue between the
TA and the kernel module. Note that I built the TA from
https://github.com/microsoft/MSRSec.git with commit
6bb57db632c424f87cbaf7ec6f9c89be7682b3c0. Maybe this is not the correct
version, I had some problems building the module from the repository
mentioned in the Patches
Regards,
Rouven Czerwinski
--
Pengutronix e.K. | |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2019-08-07 13:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 20:47 [PATCH v8 0/2] fTPM: firmware TPM running in TEE Sasha Levin
2019-07-05 20:47 ` [PATCH v8 1/2] " Sasha Levin
2019-07-11 20:04 ` Jarkko Sakkinen
2019-07-05 20:47 ` [PATCH v8 2/2] fTPM: add documentation for ftpm driver Sasha Levin
2019-07-11 20:05 ` Jarkko Sakkinen
2019-07-11 20:08 ` [PATCH v8 0/2] fTPM: firmware TPM running in TEE Jarkko Sakkinen
2019-07-11 20:10 ` Ilias Apalodimas
2019-07-11 20:35 ` Sasha Levin
2019-07-12 3:37 ` Jarkko Sakkinen
2019-07-15 9:05 ` Ilias Apalodimas
2019-08-01 16:35 ` Jarkko Sakkinen
2019-08-04 21:44 ` Jarkko Sakkinen
2019-08-05 18:05 ` Sasha Levin
2019-08-05 22:51 ` Jarkko Sakkinen
2019-08-08 1:08 ` Sasha Levin
2019-08-07 13:21 ` Rouven Czerwinski [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=5707aee16681065a975ed42a06069674c3127edb.camel@pengutronix.de \
--to=r.czerwinski@pengutronix.de \
--cc=bryankel@microsoft.com \
--cc=corbet@lwn.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=tee-dev@lists.linaro.org \
--cc=thiruan@microsoft.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;
as well as URLs for NNTP newsgroup(s).