mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Barret Rhoden <brho@google.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
	lkp@lists.01.org
Subject: Re: [iommu/vt] c9ac3b69cf: WARNING:at_drivers/iommu/intel-iommu.c:#dmar_parse_one_rmrr
Date: Mon, 3 Feb 2020 11:02:12 -0500	[thread overview]
Message-ID: <abfc90f3-1b2a-9784-e688-209913c1d9a4@google.com> (raw)
In-Reply-To: <20200203091023.GH12867@shao2-debian>

Hi -

On 2/3/20 4:10 AM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: c9ac3b69cfdbc46a0504fa353b5126827e4b0bdb ("iommu/vt-d: skip RMRR entries that fail the sanity check")
> https://github.com/0day-ci/linux/commits/Barret-Rhoden/iommu-vt-d-bad-RMRR-workarounds/20200109-051817

This looks like your system's firmware might be buggy, which is what the 
warning is all about.

 From the kmesg:

> kern  :info  : [    2.912758] DMAR: RMRR base: 0x0000009f271000 end: 0x0000009f290fff
> kern  :info  : [    2.919226] DMAR: RMRR base: 0x000000a1800000 end: 0x000000a3ffffff
> kern  :err   : [    2.925692] DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000a1800000-0x00000000a3ffffff], contact BIOS vendor for fixes
> kern  :warn  : [    2.939636] ------------[ cut here ]------------
> kern  :warn  : [    2.944436] Your BIOS is broken; bad RMRR [0x00000000a1800000-0x00000000a3ffffff]
>                               BIOS vendor: Dell Inc.; Ver: 1.2.8; Product Version: 


The e820 map has this:

> kern  :info  : [    0.000000] BIOS-e820: [mem 0x00000000a0000000-0x00000000a00fffff] reserved
> kern  :info  : [    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
> kern  :info  : [    0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved

The region 0xa1800000-0xa3ffffff isn't explicitly reserved (it's not 
listed at all), which the IOMMU-folk say is the fault of the firmware.

My commit made it so that it merely spits out a warning, instead of 
failing to use the IOMMU at all.

Thanks,

Barret


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  9:10 kernel test robot
2020-02-03 16:02 ` Barret Rhoden [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=abfc90f3-1b2a-9784-e688-209913c1d9a4@google.com \
    --to=brho@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=rong.a.chen@intel.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

all inboxes | Powered by JetHome®