From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Alex Guzman <alex@guzman.io>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jerry Snitselaar <jsnitsel@redhat.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: Debugging errors with Dell XPS 9560 TPM
Date: Tue, 18 Feb 2020 09:52:46 -0800 [thread overview]
Message-ID: <f5406106-d6dd-6d53-8ddf-a795da5e4657@intel.com> (raw)
In-Reply-To: <76b24921c76dbc8fe6ea04b44e695d8a5c89a356.camel@guzman.io>
On 2/14/20 5:47 PM, Alex Guzman wrote:
> I just tested with 5.6_rc1. The behavior is still present:
>
>
> ERROR:tcti:src/tss2-tcti/tcti-device.c:290:tcti_device_receive() Failed
> to read response from fd 3, got errno 1: Operation not permitted
> ERROR:esys:src/tss2-
> esys/api/Esys_GetCapability.c:307:Esys_GetCapability_Finish() Received
> a non-TPM Error
> ERROR:esys:src/tss2-
> esys/api/Esys_GetCapability.c:107:Esys_GetCapability() Esys Finish
> ErrorCode (0x000a000a)
> ERROR: Esys_GetCapability(0xA000A) - tcti:IO failure
> ERROR: Unable to run tpm2_getcap
I tried to reproduce this, but I couldn't. Do you know what version
of TSS are you using, and what is the configuration used to build it.
Could you try to rebuild it with --enable-tcti-device-async=no
and try that.
Thanks,
--
Tadeusz
prev parent reply other threads:[~2020-02-18 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 0:19 Debugging errors with Dell XPS 9560 TPM Alex Guzman
2020-02-14 18:32 ` Alex Guzman
2020-02-14 20:29 ` James Bottomley
2020-02-14 21:02 ` Jerry Snitselaar
2020-02-14 21:04 ` James Bottomley
2020-02-15 1:47 ` Alex Guzman
2020-02-18 17:52 ` Tadeusz Struk
2020-02-19 20:32 ` Alex Guzman
2020-02-18 17:52 ` Tadeusz Struk [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=f5406106-d6dd-6d53-8ddf-a795da5e4657@intel.com \
--to=tadeusz.struk@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alex@guzman.io \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.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 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).