Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Dear Linux folks, Am 15.09.21 um 00:17 schrieb Paul Menzel: [Use Mario’s current address] Am 15.09.21 um 00:15 schrieb Paul Menzel: [Cc: +Mario from AMD] Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). The reason is most likely that the latest firmware still reports a different EFR feature set in the IVRS table than the IOMMU reports in its EFR MMIO register. What do you mean exactly? Only 0x400 is prepended. The rest of the string is identical. What feature set would the 0x400 in the beginning be? ACPICA 20200326 is able to deassemble IVRS subtable type 0x11. The incorrect(?) value can be seen there. $ sudo iasl -d -p IVRS.dsl /sys/firmware/acpi/tables/IVRS […] $ grep EFR IVRS.dsl [090h 0144 8]EFR Image : 400F77EF22294ADA Anyway, it’d be great if AMD and Dell could take a look. Dell client kernel team, please confirm, that you received the report. Kind regards, Paul [1]: https://acpica.org/node/178 /* * Intel ACPI Component Architecture * AML/ASL+ Disassembler version 20200925 (64-bit version) * Copyright (c) 2000 - 2020 Intel Corporation * * Disassembly of IVRS, Wed Sep 15 11:48:42 2021 * * ACPI Data Table [IVRS] * * Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue */ [000h 4]Signature : "IVRS"[I/O Virtualization Reporting Structure] [004h 0004 4] Table Length : 00D0 [008h 0008 1] Revision : 02 [009h 0009 1] Checksum : EE [00Ah 0010 6] Oem ID : "AMD" [010h 0016 8] Oem Table ID : "MYRTLE" [018h 0024 4] Oem Revision : 0001 [01Ch 0028 4] Asl Compiler ID : "ACPI" [020h 0032 4]Asl Compiler Revision : 0004 [024h 0036 4] Virtualization Info : 00203041 [028h 0040 8] Reserved : [030h 0048 1]Subtable Type : 10 [Hardware Definition Block] [031h 0049 1]Flags : B0 [032h 0050 2] Length : 0048 [034h 0052 2] DeviceId : 0002 [036h 0054 2]Capability Offset : 0040 [038h 0056 8] Base Address : FC00 [040h 0064 2]PCI Segment Group : [042h 0066 2] Virtualization Info : [044h 0068 4]Feature Reporting : 80048F6E [048h 0072 1] Entry Type : 03 [049h 0073 2]Device ID : 0008 [04Bh 0075 1] Data Setting : 00 [04Ch 0076 1] Entry Type : 04 [04Dh 0077 2]Device ID : FFFE [04Fh 0079 1] Data Setting : 00 [050h 0080 1] Entry Type : 43 [051h 0081 2]Device ID : FF00 [053h 0083 1] Data Setting : 00 [054h 0084 1] Reserved : 00 [055h 0085 2]Source Used Device ID : 00A4 [057h 0087 1] Reserved : 00 [058h 0088 1] Entry Type : 04 [059h 0089 2]Device ID : [05Bh 0091 1] Data Setting : 00 [05Ch 0092 1] Entry Type : 00 [05Dh 0093 2]Device ID : [05Fh 0095 1] Data Setting : 00 [060h 0096 1] Entry Type : 48 [061h 0097 2]Device ID : [063h 0099 1] Data Setting : 00 [064h 0100 1] Handle : 00 [065h 0101 2]Source Used Device ID : 00A0 [067h 0103 1] Variety : 02 [068h 0104 1] Entry Type : 48 [069h 0105 2]Device ID : [06Bh 0107 1] Data Setting : D7 [06Ch 0108 1] Handle : 20 [06Dh 0109 2]Source Used Device ID : 00A0 [06Fh 0111 1] Variety : 01 [070h 0112 1] Entry Type : 48 [071h 0113 2]Device ID : [073h 0115 1] Data Setting : 00 [074h 0116 1] Handle : 21 [075h 0117 2]Source Used Device ID : 0001 [077h 0119 1] Variety : 01 [078h 0120 1]Subtable Type : 11 [Hardware Definition Block] [079h 0121 1]Flags : B0 [07Ah 0122 2] Length : 0058 [07Ch 0124 2] DeviceId : 0002 [07Eh 0126 2]Capability Offset : 0040 [080h 0128 8] Base Address : FC00 [088h 0136 2]PCI Segment Group : [08Ah 0138 2] Virtualization Info : [08Ch 0140 4] Attributes : 00040200 [090h 0144 8]EFR Image : 400F77EF22294ADA [098h
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Possible, but still DELL is the first point of contact here. If they find out that the problem is actually in Agesa, then DELL can escalate this to AMD. > Am 15.09.2021 um 10:42 schrieb Paul Menzel : > > Dear Jörg, > > > Am 15.09.21 um 10:30 schrieb Jörg Rödel: >> Mainly DELL should look at this, because it is their BIOS which is >> responsible for this inconsistency. > > I am not so sure about that, as today’s (x86) firmware often consists of > platform initialization (PI) code (or firmware support package (FSP), > provided by the chipset/SoC vendors, like AGESA for AMD, which the ODM just > integrate. > > If only Dell systems are affected, that would of course point to a bug in the > Dell firmware. > > > Kind regards, > > Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Dear Jörg, Am 15.09.21 um 10:30 schrieb Jörg Rödel: Mainly DELL should look at this, because it is their BIOS which is responsible for this inconsistency. I am not so sure about that, as today’s (x86) firmware often consists of platform initialization (PI) code (or firmware support package (FSP), provided by the chipset/SoC vendors, like AGESA for AMD, which the ODM just integrate. If only Dell systems are affected, that would of course point to a bug in the Dell firmware. Kind regards, Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Mainly DELL should look at this, because it is their BIOS which is responsible for this inconsistency. > Am 15.09.2021 um 00:17 schrieb Paul Menzel : > > [Use Mario’s current address] > > Am 15.09.21 um 00:15 schrieb Paul Menzel: >> [Cc: +Mario from AMD] >> Dear Jörg, >> Am 14.09.21 um 14:09 schrieb Jörg Rödel: >>> On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). >>> >>> The reason is most likely that the latest firmware still reports a >>> different EFR feature set in the IVRS table than the IOMMU reports in >>> its EFR MMIO register. >> What do you mean exactly? Only 0x400 is prepended. The rest of the string is >> identical. What feature set would the 0x400 in the beginning be? >> Anyway, it’d be great if AMD and Dell could take a look. >> Kind regards, >> Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
[Use Mario’s current address] Am 15.09.21 um 00:15 schrieb Paul Menzel: [Cc: +Mario from AMD] Dear Jörg, Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). The reason is most likely that the latest firmware still reports a different EFR feature set in the IVRS table than the IOMMU reports in its EFR MMIO register. What do you mean exactly? Only 0x400 is prepended. The rest of the string is identical. What feature set would the 0x400 in the beginning be? Anyway, it’d be great if AMD and Dell could take a look. Kind regards, Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
[Cc: +Mario from AMD] Dear Jörg, Am 14.09.21 um 14:09 schrieb Jörg Rödel: On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). The reason is most likely that the latest firmware still reports a different EFR feature set in the IVRS table than the IOMMU reports in its EFR MMIO register. What do you mean exactly? Only 0x400 is prepended. The rest of the string is identical. What feature set would the 0x400 in the beginning be? Anyway, it’d be great if AMD and Dell could take a look. Kind regards, Paul ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote: > Linux 5.15-rc1 still warns about that (also with latest system firmware > 1.1.50). The reason is most likely that the latest firmware still reports a different EFR feature set in the IVRS table than the IOMMU reports in its EFR MMIO register. Regards, Joerg ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
[Cc: +Dell Linux kernel client team] Dear Linux folks, Am 12.04.21 um 20:07 schrieb Paul Menzel: On the Dell OptiPlex 5055, Linux warns about an EFR mismatch in the firmware. ``` […] [ 0.00] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS 1.1.20 05/31/2019 […] [ 1.479774] smpboot: CPU0: AMD Ryzen 5 PRO 1500 Quad-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) […] [ 2.507370] AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada). [ 2.507381] pci :00:00.2: AMD-Vi: IOMMU performance counters supported [ 2.525221] pci :00:00.2: can't derive routing for PCI INT A [ 2.531240] pci :00:00.2: PCI INT A: not connected [ 2.536415] pci :00:01.0: Adding to iommu group 0 [ 2.541485] pci :00:01.3: Adding to iommu group 1 […] ``` The difference in the MMIO value is a prepended 0x400. Can that be explained somehow? If not, it’d be great, if you could give more details about the firmware issue, so I can contact the Dell support to fix the firmware. Linux 5.15-rc1 still warns about that (also with latest system firmware 1.1.50). Kind regards, Paul [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a44092e326d403c7878018ba532369f84d31dbfa ___ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
