On Tue, Dec 3, 2019 at 2:46 AM Zbigniew Jędrzejewski-Szmek
On Mon, Dec 02, 2019 at 11:27:44PM -0700, Chris Murphy wrote:
> Gist is tpm2-abrmd expects to find a TPM2, since it doesn't, it fails
> ungracefully and restarts every 5s, thus spamming the journal.
Yeah, I had the same issue and ended up disabling it.
Note: it is against the policy for a service to be enabled by default
if it cannot handle the default case gracefully:
Tricky question, is it really enabled by default? Or is it being poked
by fwupd? Of course from my simple user perspective, that doesn't
matter, but per the policy...I'm not certain.
$ sudo systemctl status tpm2-abrmd
● tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon
Loaded: loaded (/usr/lib/systemd/system/tpm2-abrmd.service;
disabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue
2019-12-03 11:53:19 MST; 4s ago
Process: 7993 ExecStart=/usr/sbin/tpm2-abrmd (code=exited, status=1/FAILURE)
Main PID: 7993 (code=exited, status=1/FAILURE)