Thank you so much for the clarification, I get it now.
From: Javier Martinez Canillas [mailto:firstname.lastname@example.org]
Sent: Thursday, September 28, 2017 6:12 PM
To: Slash Wu <slash.wu(a)ztsystems.com>; tpm2(a)lists.01.org
Subject: Re: [tpm2] tpm2-abrmd and tpm2_tools collision
On 09/28/2017 09:12 AM, Slash Wu wrote:
I launched tpm2-abrmd, and then the tpm2-tools (e.g. tpm2_nvlist) failed with the
following msg, but it worked without the tpm2-abrmd been launched, why ?
# /usr/local/bin/tpm2_nvlist -T device
ERROR: Failed to initialize device TCTI context: 0xa000a
It's expected. If the tpm2-abrmd is running, then it has opened the TPM device.
So when the device TCTI library tries to open the device again, the driver will return an
You can easily check this by running your process with strace or enabling the dynamic
debug log messages for the TPM driver:
$ strace -f -eopenat tpm2_pcrlist -T device:/dev/tpm0 2>&1 | grep
openat(AT_FDCWD, "/dev/tpm0", O_RDWR) = -1 EBUSY (Device or resource busy)
$ echo 'file drivers/char/tpm/tpm-dev.c +p' >
$ dmesg | grep tpm
[71684.903356] tpm tpm0: Another process owns this TPM
What's your use case to bypass the tpm2-abrmd? I don't think that's a good
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement Red Hat