Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Alex Guzman <alex@guzman.io>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Jerry Snitselaar <jsnitsel@redhat.com>,
	linux-integrity@vger.kernel.org
Subject: Re: Debugging errors with Dell XPS 9560 TPM
Date: Wed, 19 Feb 2020 15:32:50 -0500
Message-ID: <CAJ7-PMbujee92N1f9xVF8vtXgS49qpe7qHkeWh1Z0R-Rk-Jkaw@mail.gmail.com> (raw)
In-Reply-To: <233ecdf9-0495-90d1-9d9d-7e7d7e60d011@intel.com>

My gentoo ebuild has these config flags set:

        --with-crypto="$(usex gcrypt gcrypt ossl)" \
        --with-udevrulesdir="$(get_udevdir)/rules.d" \
        --with-udevrulesprefix=60- --disable-defaultflags \
        --disable-tcti-device-async

So I'm already testing with async off as far as I can tell.

I just updated to the latest commits of tpm2-tss and tpm2-tools
(21c6bf9e75391a7033b74c517c88e336d2da4a9d and
711250043ee075a4ebef7c8ad2a22d23e542ca00 respectively) as well as
updating to 5.6_rc2. Still the same result.


On Tue, Feb 18, 2020 at 12:52 PM Tadeusz Struk <tadeusz.struk@intel.com> wrote:
>
> 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

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02  0:19 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 [this message]
2020-02-18 17:52           ` Tadeusz Struk

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=CAJ7-PMbujee92N1f9xVF8vtXgS49qpe7qHkeWh1Z0R-Rk-Jkaw@mail.gmail.com \
    --to=alex@guzman.io \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=tadeusz.struk@intel.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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org
	public-inbox-index linux-integrity

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git