Hello Dan,

On 02/20/2018 08:40 PM, Anderson, Daniel wrote:
> I have been getting the same error and cannot start the tpm2-service:
> 
> $ sudo systemctl start tpm2-abrmd.service
> Job for tpm2-abrmd.service failed because the control process exited with error code. See "systemctl status tpm2-abrmd.service" and "journalctl -xe" for details.
> 
> $ systemctl status tpm2-abrmd.service
> tpm2-abrmd.service: Main process exited, code=exited, status=1/FA
> Failed to start TPM2 Access Broker and Resource Management Daemon
> Unit entered failed state.
> Failed with result 'exit-code'.
> 
> # Start manually:
> $ /usr/local/sbin/tpm2-abrmd&
> ** (tpm2-abrmd:1596): WARNING **: failed to initialize device TCTI context: 0xa000a
> ** (tpm2-abrmd:1596): CRITICAL **: TCTI Initializaiton: 0xa000a
> 
> $ tpm2_rc_decode 0xa000a
> tcti:IO failure
> 

What versions of the tpm2-tss, tools and abrmd are you using? I'll try to
reproduce the issue. But yes, the problem seems to be that it's defaulting
to the device TCTI instead of the socket TCTI. And since you don't have a
/dev/tpm? (or your user doesn't have access to it), the tpm2-abrmd dies.

> So it seems that this is a known bug:
> https://github.com/tpm2-software/tpm2-abrmd/issues/321
> https://github.com/tpm2-software/tpm2-abrmd/pull/330
>
> Is there a workaround?  The discussion is too cryptic for me. For example,  I can't find a tpm2_listpcrs command in  tpm2-tools (or -abrmd or -tss). I am running on Ubuntu Linux with a simulator.
>

PR #300 has been merged already so if you think that's related, it may be
worth to give a try to master. I still didn't have time to catch up on all
the TCTI dynamic loading changes so I can't say if #330 is related to this
issue or not.

> Dan

Best regards,
-- 
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat