Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: "Genevieve" <genevieve@sunlashed.garden>
To: <linux-integrity@vger.kernel.org>
Subject: Firmware bug on ASRock X370/Ryzen 2600 prevents use of TPM device
Date: Mon, 12 Dec 2022 19:49:40 -0600	[thread overview]
Message-ID: <CP0B9GMWHUP5.3VZOZJBZJ3ODC@arch> (raw)

Hi there,

Apologies if this is the wrong mailing list for this query - feel free
to redirect me if so.

Looking into issues I'm having with systemd being unable to access the
TPM, it seems they occur because its firmware reports incorrect info
and the kernel or driver then can't expose a device for it.
(The device combination here is an ASRock X370 Killer SLI/AC motherboard
and a Ryzen 2600 CPU).

> tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the
> entire command/response buffer.
> [mem 0xec6c2000-0xec6c2fff flags 0x200] vs ec6c2000 4000
> fbcon: Taking over console
> tpm_crb MSFT0101:00: can't request region for resource
> [mem 0xec6c2000-0xec6c2fff]
> tpm_crb: probe of MSFT0101:00 failed with error -16

This leads to some errors later in boot when a TPM device is expected
but cannot be found:

> systemd-pcrphase[601]: ERROR:tcti:src/tss2-tcti/tcti-device.c:452:
> Tss2_Tcti_Device_Init() Failed to open specified TCTI device file
> /dev/tpmrm0: No such file or directory
> systemd-pcrphase[601]: Failed to initialize TCTI context:
> tcti:IO failure

(The initial bug report filed with systemd can be found here:
https://github.com/systemd/systemd/issues/25700)

It was suggested to me that it is possible to tweak the driver
to allow it to expose this device despite the issues with its
firmware, which is why I'm reaching out here.

Let me know if there's any other additional information I can provide,
and thanks for your time.

Best,

Genevieve

                 reply	other threads:[~2022-12-13  1:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CP0B9GMWHUP5.3VZOZJBZJ3ODC@arch \
    --to=genevieve@sunlashed.garden \
    --cc=linux-integrity@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox