From: Huang Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [iommu/vt] 571dbbd4d04: DMAR-IR: Failed to copy IR table for dmar1 from previous kernel
Date: Thu, 02 Jul 2015 15:56:23 +0800 [thread overview]
Message-ID: <1435823783.17694.2.camel@intel.com> (raw)
In-Reply-To: <20150702063925.GC16233@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
On Thu, 2015-07-02 at 08:39 +0200, Joerg Roedel wrote:
> 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?
Yes. We use kexec to boot the new kernel.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: Huang Ying <ying.huang@intel.com>
To: Joerg Roedel <jroedel@suse.de>
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, 02 Jul 2015 15:56:23 +0800 [thread overview]
Message-ID: <1435823783.17694.2.camel@intel.com> (raw)
In-Reply-To: <20150702063925.GC16233@suse.de>
On Thu, 2015-07-02 at 08:39 +0200, Joerg Roedel wrote:
> 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?
Yes. We use kexec to boot the new kernel.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-07-02 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 5:14 [iommu/vt] 571dbbd4d04: DMAR-IR: Failed to copy IR table for dmar1 from previous kernel Huang Ying
2015-07-02 5:14 ` [lkp] " Huang Ying
2015-07-02 6:39 ` Joerg Roedel
2015-07-02 6:39 ` [lkp] " Joerg Roedel
2015-07-02 7:56 ` Huang Ying [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=1435823783.17694.2.camel@intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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 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.