Linux IOMMU Development
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: David Coe <david.coe@live.co.uk>,
	Robert Richter <rrichter@amd.com>,
	Alexander Monakov <amonakov@ispras.ru>,
	iommu@lists.linux-foundation.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Dell.Client.Kernel@dell.com
Subject: Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Date: Wed, 15 Sep 2021 10:30:30 +0200	[thread overview]
Message-ID: <D1BCBF26-0F73-434B-8C95-B2CB4934D0A4@8bytes.org> (raw)
In-Reply-To: <3c61d4d9-f6e0-d847-3b60-bde8b3733f09@molgen.mpg.de>

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

  reply	other threads:[~2021-09-15  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2021-09-15  8:42           ` Paul Menzel
2021-09-15  8:47             ` Jörg Rödel
2021-09-15 14:39         ` Paul Menzel

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=D1BCBF26-0F73-434B-8C95-B2CB4934D0A4@8bytes.org \
    --to=joro@8bytes.org \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=amonakov@ispras.ru \
    --cc=david.coe@live.co.uk \
    --cc=iommu@lists.linux-foundation.org \
    --cc=mario.limonciello@amd.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rrichter@amd.com \
    /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