From: Joerg Roedel <jroedel@suse.de>
To: Huang Ying <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [lkp] [iommu/vt] 571dbbd4d04: DMAR-IR: Failed to copy IR table for dmar1 from previous kernel
Date: Thu, 2 Jul 2015 08:39:25 +0200 [thread overview]
Message-ID: <20150702063925.GC16233@suse.de> (raw)
In-Reply-To: <1435814058.5489.105.camel@intel.com>
On Thu, Jul 02, 2015 at 01:14:18PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 571dbbd4d044e11c78bc077acb3ccef4c77b096e ("iommu/vt-d: Don't disable IR when it was previously enabled")
>
> The following new message in kernel log may make end user confusing.
>
> [ 0.503764] DMAR-IR: IRQ remapping was enabled on dmar0 but we are not in kdump mode
> [ 0.512418] DMAR-IR: Failed to copy IR table for dmar0 from previous kernel
> [ 0.520501] DMAR-IR: IRQ remapping was enabled on dmar1 but we are not in kdump mode
> [ 0.529154] DMAR-IR: Failed to copy IR table for dmar1 from previous kernel
> [ 0.537077] DMAR-IR: Enabled IRQ remapping in x2apic mode
This is not a problem, the kernel detected that the IOMMU was already
enabled, but it is not booting into a kdump kernel so it is not trying
to copy over translation tables. The messages for this case are indeed a
bit misleading, it looks like the kernel tried to copy the translation
tables, but it didn't. I'll fix this.
What were you doing to trigger this, it is quite uncommon to find the
IOMMU enabled on a normal kernel boot. Did you boot with kexec into a
new kernel?
Joerg
next prev parent reply other threads:[~2015-07-02 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 5:14 [lkp] [iommu/vt] 571dbbd4d04: DMAR-IR: Failed to copy IR table for dmar1 from previous kernel Huang Ying
2015-07-02 6:39 ` Joerg Roedel [this message]
2015-07-02 7:56 ` Huang Ying
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=20150702063925.GC16233@suse.de \
--to=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@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