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@xxxxxxxxx> 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
