iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Thomas G <thomas.grudzien@gmail.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>, iommu@lists.linux-foundation.org
Subject: Re: (new error in kernel 5.5) DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
Date: Mon, 3 Feb 2020 10:27:56 +0100	[thread overview]
Message-ID: <CAJ9qOnVFBzSHPJ=fmhk-nv-0h=SYgx=kj+vKnHS06F96opHXoQ@mail.gmail.com> (raw)
In-Reply-To: <7a147a10-c472-2fcd-b45f-215dd6c96b7c@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2739 bytes --]

Thanks Baolu, I'll wait for 5.6 then.
In the meanwhile I'll also try to contact Asrock, without much hope they
actually patch their bios.

Best regards

On Mon, Feb 3, 2020 at 2:34 AM Lu Baolu <baolu.lu@linux.intel.com> wrote:

> Hi Thomas,
>
> Below commit is supposed to fix this issue. It's currently in
> x86/vt-d branch of the iommu tree, and will be part of v5.6-rc1.
>
> commit f5a68bb0752e0cf77c06f53f72258e7beb41381b
> Author: Barret Rhoden <brho@google.com>
> Date:   Wed Jan 15 11:03:56 2020 +0800
>
>      iommu/vt-d: Mark firmware tainted if RMRR fails sanity check
>
>      RMRR entries describe memory regions that are DMA targets for devices
>      outside the kernel's control.
>
>      RMRR entries that fail the sanity check are pointing to regions of
>      memory that the firmware did not tell the kernel are reserved or
>      otherwise should not be used.
>
>      Instead of aborting DMAR processing, this commit marks the firmware
>      as tainted. These RMRRs will still be identity mapped, otherwise,
>      some devices, e.x. graphic devices, will not work during boot.
>
>      Signed-off-by: Barret Rhoden <brho@google.com>
>      Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>      Fixes: f036c7fa0ab60 ("iommu/vt-d: Check VT-d RMRR region in BIOS
> is reported as reserved")
>      Signed-off-by: Joerg Roedel <jroedel@suse.de>
>
> Best regards,
> baolu
>
> On 2020/2/3 5:06, Thomas G wrote:
> > Dear all,
> >
> > Vt-d seems to be broken since I upgraded to kernel 5.5, there is a new
> > dmesg that was not there in 5.4:
> > "DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
> > [0x0000000041d92000-0x0000000041d94fff], contact BIOS vendor for fixes"
> >
> > System motherboard is Asrock X299 Taichi XE, bios 1.70, CPU is Core i9
> 7920
> > Vt-d and gpu passthrough was working ok since kernel 4.20 when I
> > purchased it
> >
> > I attached the dmesg I get with kernel 5.5.1, and the dmesg from 5.4.17.
> >
> > Also, I use the following script that displays the IOMMU groups, I found
> > the script there
> > https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF
> >
> > #!/bin/bash
> > shopt -s nullglob
> > for d in /sys/kernel/iommu_groups/*/devices/*; do
> >      n=${d#*/iommu_groups/*}; n=${n%%/*}
> >      printf 'IOMMU Group %s ' "$n"
> >      lspci -nns "${d##*/}"
> > done;
> >
> > The output of this script with kernel 5.4.17 is attached to this email.
> > The same script with kernel 5.5.1 produces an empty output
> >
> > Hope it helps narrowing down the problem, please ask additional info if
> > needed. Sorry if this is not submitted as it should be (then please
> > advise), first time I report -what apprears to be- a bug.
> >
> > Best,
> > Thomas
>

[-- Attachment #1.2: Type: text/html, Size: 3861 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

      reply	other threads:[~2020-02-03  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 21:06 (new error in kernel 5.5) DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR Thomas G
2020-02-03  1:34 ` Lu Baolu
2020-02-03  9:27   ` Thomas G [this message]

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='CAJ9qOnVFBzSHPJ=fmhk-nv-0h=SYgx=kj+vKnHS06F96opHXoQ@mail.gmail.com' \
    --to=thomas.grudzien@gmail.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).