Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752614AbbGBH4d (ORCPT ); Thu, 2 Jul 2015 03:56:33 -0400 Received: from mga03.intel.com ([134.134.136.65]:28679 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751293AbbGBH4Z (ORCPT ); Thu, 2 Jul 2015 03:56:25 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,390,1432623600"; d="scan'208";a="754613633" Message-ID: <1435823783.17694.2.camel@intel.com> Subject: Re: [lkp] [iommu/vt] 571dbbd4d04: DMAR-IR: Failed to copy IR table for dmar1 from previous kernel From: Huang Ying To: Joerg Roedel Cc: LKML , LKP ML Date: Thu, 02 Jul 2015 15:56:23 +0800 In-Reply-To: <20150702063925.GC16233@suse.de> References: <1435814058.5489.105.camel@intel.com> <20150702063925.GC16233@suse.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1711 Lines: 45 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/