This is similar to bug 1394912, but for AMD. Description of problem: On boot, I get the following messages: [ 0.606538] tpm_crb MSFT0101:00: can't request region for resource [mem 0xda762000-0xda765fff] [ 0.606542] tpm_crb: probe of MSFT0101:00 failed with error -16 [ 0.723956] ima: No TPM chip found, activating TPM-bypass! Version-Release number of selected component (if applicable): kernel-5.3.11-300.fc31.x86_64 How reproducible: Always Additional info: Mainboard is ASUS PRIME B450-PLUS with an AMD Ryzen 5 2600. BIOS is version 1823 from 10/15/2019.
Created attachment 1636770 [details] asus-b450-plus-iomem
Created attachment 1636771 [details] asus-b450-plus-dmidecode
Same problem with Asus X370 and B350 motherboards. I suspect all Asus AM4 motherboards have the same problem when fTPM is enabled.
Created attachment 1643385 [details] dump from /proc/iomem
Same on MSI PC-Mate woth B350 chipset and Ryzen 1600X $ dmesg | egrep -i 'Linux version|DMI:|tpm|Ryzen' [ 0.000000] Linux version 5.4.2-300.fc31.x86_64 (mockbuild.fedoraproject.org) (gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC)) #1 SMP Fri Dec 6 13:07:05 UTC 2019 [ 0.000000] efi: TPMFinalLog=0xdd9f4000 ACPI 2.0=0xdd98a000 ACPI=0xdd98a000 SMBIOS=0xde478000 MEMATTR=0xda678698 ESRT=0xdafe1998 TPMEventLog=0xd7987018 [ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7A34/B350 PC MATE (MS-7A34), BIOS A.J0 01/23/2019 [ 0.000000] ACPI: TPM2 0x00000000DD9AFAE8 000034 (v04 ALASKA A M I 00000001 AMI 00000000) [ 0.106107] smpboot: CPU0: AMD Ryzen 5 1600X Six-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) [ 0.651244] tpm_tis MSFT0101:00: IRQ index 0 not found [ 0.651325] tpm_crb MSFT0101:00: can't request region for resource [mem 0xdda28000-0xdda28fff] [ 0.651327] tpm_crb: probe of MSFT0101:00 failed with error -16 [ 0.765543] ima: No TPM chip found, activating TPM-bypass!
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Looks much better with the latest kernel: $ dmesg | egrep -i 'Linux version|DMI:|tpm|Ryzen' [ 0.000000] Linux version 5.5.8-200.fc31.x86_64 (mockbuild.fedoraproject.org) (gcc version 9.2.1 20190827 (Red Hat 9.2.1-1) (GCC)) #1 SMP Thu Mar 5 21:28:03 UTC 2020 [ 0.000000] efi: TPMFinalLog=0xdac17000 ACPI 2.0=0xd17a2000 ACPI=0xd17a2000 SMBIOS=0xdb63d000 SMBIOS 3.0=0xdb63c000 ESRT=0xd821b518 MEMATTR=0xd6c74018 RNG=0xdb63bd98 TPMEventLog=0xd1234018 [ 0.000000] DMI: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 2008 12/06/2019 [ 0.006217] ACPI: TPM2 0x00000000D17BA3C0 000034 (v03 ALASKA A M I 00000001 AMI 00000000) [ 0.405574] smpboot: CPU0: AMD Ryzen 5 2600 Six-Core Processor (family: 0x17, model: 0x8, stepping: 0x2) [ 0.910700] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xda76f000-0xda76ffff flags 0x200] vs da76f000 4000 [ 0.910705] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xda773000-0xda773fff flags 0x200] vs da773000 4000 Not sure whether the last two lines still indicate some issue. A simple tpm2_pcrread does at list output something.
Still the same under F32. I have not tried the Beta-BIOS yet. $ dmesg | egrep -i 'Linux version|DMI:|tpm|Ryzen' [ 0.000000] Linux version 5.6.0-0.rc7.git0.2.fc32.x86_64 (mockbuild.fedoraproject.org) (gcc version 10.0.1 20200311 (Red Hat 10.0.1-0.9) (GCC)) #1 SMP Mon Mar 23 18:38:45 UTC 2020 [ 0.000000] efi: TPMFinalLog=0xdd9f4000 ACPI 2.0=0xdd98a000 ACPI=0xdd98a000 SMBIOS=0xde478000 MEMATTR=0xda6f8318 ESRT=0xdae78c18 RNG=0xde493298 TPMEventLog=0xd7919018 [ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7A34/B350 PC MATE (MS-7A34), BIOS A.J0 01/23/2019 [ 0.000000] ACPI: TPM2 0x00000000DD9AFAE8 000034 (v04 ALASKA A M I 00000001 AMI 00000000) [ 0.106659] smpboot: CPU0: AMD Ryzen 5 1600X Six-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) [ 0.676668] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdda24000-0xdda24fff flags 0x200] vs dda24000 4000 [ 0.676670] tpm_crb MSFT0101:00: can't request region for resource [mem 0xdda24000-0xdda24fff] [ 0.676673] tpm_crb: probe of MSFT0101:00 failed with error -16 [ 0.791881] ima: No TPM chip found, activating TPM-bypass!
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.