* AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
@ 2021-04-12 18:07 Paul Menzel
2021-09-14 9:10 ` Paul Menzel
0 siblings, 1 reply; 9+ messages in thread
From: Paul Menzel @ 2021-04-12 18:07 UTC (permalink / raw)
To: Jörg Rödel; +Cc: iommu, Alexander Monakov, Robert Richter
Dear Linux folks,
On the Dell OptiPlex 5055, Linux warns about an EFR mismatch in the
firmware.
```
[…]
[ 0.000000] 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 0000:00:00.2: AMD-Vi: IOMMU performance counters
supported
[ 2.525221] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 2.531240] pci 0000:00:00.2: PCI INT A: not connected
[ 2.536415] pci 0000:00:01.0: Adding to iommu group 0
[ 2.541485] pci 0000: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.
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-04-12 18:07 AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada) Paul Menzel
@ 2021-09-14 9:10 ` Paul Menzel
2021-09-14 12:09 ` Jörg Rödel
0 siblings, 1 reply; 9+ messages in thread
From: Paul Menzel @ 2021-09-14 9:10 UTC (permalink / raw)
To: Jörg Rödel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu, Dell.Client.Kernel
[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.000000] 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 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
> [ 2.525221] pci 0000:00:00.2: can't derive routing for PCI INT A
> [ 2.531240] pci 0000:00:00.2: PCI INT A: not connected
> [ 2.536415] pci 0000:00:01.0: Adding to iommu group 0
> [ 2.541485] pci 0000: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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-14 9:10 ` Paul Menzel
@ 2021-09-14 12:09 ` Jörg Rödel
2021-09-14 22:15 ` Paul Menzel
0 siblings, 1 reply; 9+ messages in thread
From: Jörg Rödel @ 2021-09-14 12:09 UTC (permalink / raw)
To: Paul Menzel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu, Dell.Client.Kernel
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-14 12:09 ` Jörg Rödel
@ 2021-09-14 22:15 ` Paul Menzel
2021-09-14 22:17 ` Paul Menzel
0 siblings, 1 reply; 9+ messages in thread
From: Paul Menzel @ 2021-09-14 22:15 UTC (permalink / raw)
To: Jörg Rödel
Cc: David Coe, Robert Richter, Mario Limonciello, Alexander Monakov,
iommu, Dell.Client.Kernel
[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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-14 22:15 ` Paul Menzel
@ 2021-09-14 22:17 ` Paul Menzel
2021-09-15 8:30 ` Jörg Rödel
2021-09-15 14:39 ` Paul Menzel
0 siblings, 2 replies; 9+ messages in thread
From: Paul Menzel @ 2021-09-14 22:17 UTC (permalink / raw)
To: Jörg Rödel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu,
Mario Limonciello, Dell.Client.Kernel
[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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-14 22:17 ` Paul Menzel
@ 2021-09-15 8:30 ` Jörg Rödel
2021-09-15 8:42 ` Paul Menzel
2021-09-15 14:39 ` Paul Menzel
1 sibling, 1 reply; 9+ messages in thread
From: Jörg Rödel @ 2021-09-15 8:30 UTC (permalink / raw)
To: Paul Menzel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu,
Mario Limonciello, Dell.Client.Kernel
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 <pmenzel@molgen.mpg.de>:
>
> [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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-15 8:30 ` Jörg Rödel
@ 2021-09-15 8:42 ` Paul Menzel
2021-09-15 8:47 ` Jörg Rödel
0 siblings, 1 reply; 9+ messages in thread
From: Paul Menzel @ 2021-09-15 8:42 UTC (permalink / raw)
To: Jörg Rödel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu,
Mario Limonciello, Dell.Client.Kernel
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-15 8:42 ` Paul Menzel
@ 2021-09-15 8:47 ` Jörg Rödel
0 siblings, 0 replies; 9+ messages in thread
From: Jörg Rödel @ 2021-09-15 8:47 UTC (permalink / raw)
To: Paul Menzel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu,
Mario Limonciello, Dell.Client.Kernel
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 <pmenzel@molgen.mpg.de>:
>
> 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
2021-09-14 22:17 ` Paul Menzel
2021-09-15 8:30 ` Jörg Rödel
@ 2021-09-15 14:39 ` Paul Menzel
1 sibling, 0 replies; 9+ messages in thread
From: Paul Menzel @ 2021-09-15 14:39 UTC (permalink / raw)
To: Jörg Rödel
Cc: David Coe, Robert Richter, Alexander Monakov, iommu,
Mario Limonciello, Dell.Client.Kernel
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
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
[-- Attachment #2: IVRS.dsl --]
[-- Type: text/x-dsl, Size: 6833 bytes --]
/*
* 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 0000 4] Signature : "IVRS" [I/O Virtualization Reporting Structure]
[004h 0004 4] Table Length : 000000D0
[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 : 00000001
[01Ch 0028 4] Asl Compiler ID : "ACPI"
[020h 0032 4] Asl Compiler Revision : 00040000
[024h 0036 4] Virtualization Info : 00203041
[028h 0040 8] Reserved : 0000000000000000
[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 : 00000000FC000000
[040h 0064 2] PCI Segment Group : 0000
[042h 0066 2] Virtualization Info : 0000
[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 : FFFF
[05Bh 0091 1] Data Setting : 00
[05Ch 0092 1] Entry Type : 00
[05Dh 0093 2] Device ID : 0000
[05Fh 0095 1] Data Setting : 00
[060h 0096 1] Entry Type : 48
[061h 0097 2] Device ID : 0000
[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 : 0000
[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 : 0000
[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 : 00000000FC000000
[088h 0136 2] PCI Segment Group : 0000
[08Ah 0138 2] Virtualization Info : 0000
[08Ch 0140 4] Attributes : 00040200
[090h 0144 8] EFR Image : 400F77EF22294ADA
[098h 0152 8] Reserved : 0000000000000000
[0A0h 0160 1] Entry Type : 03
[0A1h 0161 2] Device ID : 0008
[0A3h 0163 1] Data Setting : 00
[0A4h 0164 1] Entry Type : 04
[0A5h 0165 2] Device ID : FFFE
[0A7h 0167 1] Data Setting : 00
[0A8h 0168 1] Entry Type : 43
[0A9h 0169 2] Device ID : FF00
[0ABh 0171 1] Data Setting : 00
[0ACh 0172 1] Reserved : 00
[0ADh 0173 2] Source Used Device ID : 00A4
[0AFh 0175 1] Reserved : 00
[0B0h 0176 1] Entry Type : 04
[0B1h 0177 2] Device ID : FFFF
[0B3h 0179 1] Data Setting : 00
[0B4h 0180 1] Entry Type : 00
[0B5h 0181 2] Device ID : 0000
[0B7h 0183 1] Data Setting : 00
[0B8h 0184 1] Entry Type : 48
[0B9h 0185 2] Device ID : 0000
[0BBh 0187 1] Data Setting : 00
[0BCh 0188 1] Handle : 00
[0BDh 0189 2] Source Used Device ID : 00A0
[0BFh 0191 1] Variety : 02
[0C0h 0192 1] Entry Type : 48
[0C1h 0193 2] Device ID : 0000
[0C3h 0195 1] Data Setting : D7
[0C4h 0196 1] Handle : 20
[0C5h 0197 2] Source Used Device ID : 00A0
[0C7h 0199 1] Variety : 01
[0C8h 0200 1] Entry Type : 48
[0C9h 0201 2] Device ID : 0000
[0CBh 0203 1] Data Setting : 00
[0CCh 0204 1] Handle : 21
[0CDh 0205 2] Source Used Device ID : 0001
[0CFh 0207 1] Variety : 01
Raw Table Data: Length 208 (0xD0)
0000: 49 56 52 53 D0 00 00 00 02 EE 41 4D 44 00 00 00 // IVRS......AMD...
0010: 4D 59 52 54 4C 45 00 00 01 00 00 00 41 43 50 49 // MYRTLE......ACPI
0020: 00 00 04 00 41 30 20 00 00 00 00 00 00 00 00 00 // ....A0 .........
0030: 10 B0 48 00 02 00 40 00 00 00 00 FC 00 00 00 00 // ..H...@.........
0040: 00 00 00 00 6E 8F 04 80 03 08 00 00 04 FE FF 00 // ....n...........
0050: 43 00 FF 00 00 A4 00 00 04 FF FF 00 00 00 00 00 // C...............
0060: 48 00 00 00 00 A0 00 02 48 00 00 D7 20 A0 00 01 // H.......H... ...
0070: 48 00 00 00 21 01 00 01 11 B0 58 00 02 00 40 00 // H...!.....X...@.
0080: 00 00 00 FC 00 00 00 00 00 00 00 00 00 02 04 00 // ................
0090: DA 4A 29 22 EF 77 0F 40 00 00 00 00 00 00 00 00 // .J)".w.@........
00A0: 03 08 00 00 04 FE FF 00 43 00 FF 00 00 A4 00 00 // ........C.......
00B0: 04 FF FF 00 00 00 00 00 48 00 00 00 00 A0 00 02 // ........H.......
00C0: 48 00 00 D7 20 A0 00 01 48 00 00 00 21 01 00 01 // H... ...H...!...
[-- Attachment #3: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2021-09-15 14:39 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-12 18:07 AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada) Paul Menzel
2021-09-14 9:10 ` Paul Menzel
2021-09-14 12:09 ` Jörg Rödel
2021-09-14 22:15 ` Paul Menzel
2021-09-14 22:17 ` Paul Menzel
2021-09-15 8:30 ` Jörg Rödel
2021-09-15 8:42 ` Paul Menzel
2021-09-15 8:47 ` Jörg Rödel
2021-09-15 14:39 ` Paul Menzel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.