Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933896Ab3CHHxN (ORCPT ); Fri, 8 Mar 2013 02:53:13 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:46110 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932694Ab3CHHxL (ORCPT ); Fri, 8 Mar 2013 02:53:11 -0500 X-SecurityPolicyCheck: OK by SHieldMailChecker v1.7.4 Message-ID: <513998A6.3030201@jp.fujitsu.com> Date: Fri, 08 Mar 2013 16:52:06 +0900 From: Takao Indoh User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: chaowang@redhat.com CC: yinghai@kernel.org, caiqian@redhat.com, linux-kernel@vger.kernel.org, kexec@lists.infradead.org, dyoung@redhat.com, vgoyal@redhat.com, hpa@linux.intel.com Subject: Re: 3.9-rc1: crash kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer References: <51397D1D.5030602@redhat.com> <1750036321.11235774.1362722613994.JavaMail.root@redhat.com> <51399154.5030500@redhat.com> <51399442.1080609@redhat.com> In-Reply-To: <51399442.1080609@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2294 Lines: 54 (2013/03/08 16:33), WANG Chao wrote: > On 03/08/2013 03:27 PM, Yinghai Lu wrote: >> On Thu, Mar 7, 2013 at 11:20 PM, WANG Chao wrote: >>>> >>>> looks like your system DO have DMAR table, please enable dmar >>>> remapping in your kernel config. >>> >>> I've already got following config: >>> CONFIG_DMAR_TABLE=y >>> CONFIG_INTEL_IOMMU=y >>> CONFIG_IRQ_REMAP=y >>> >>> but I don't have intel_iommu=on in kernel cmdline. IIRC, iommu will prevent >>> 2nd kernel from booting ... >> >> Did you put intel_iommu=on on first and second cpu both? > > I tried, 2nd kernel didn't boot and keep splitting errors like these: > [ 2.106939] DMAR: No ATSR found > [ 2.110121] IOMMU 0 0xfed90000: using Queued invalidation > [ 2.115522] IOMMU 1 0xfed91000: using Queued invalidation > [ 2.120919] IOMMU: Setting RMRR: > [ 2.124162] IOMMU: Setting identity map for device 0000:00:02.0 [0xab800000 > - 0xaf9fffff] > [ 2.133099] IOMMU: Setting identity map for device 0000:00:1d.0 [0xaac95000 > - 0xaacb2fff] > [ 2.141305] IOMMU: Setting identity map for device 0000:00:1a.0 [0xaac95000 > - 0xaacb2fff] > [ 2.149503] IOMMU: Setting identity map for device 0000:00:14.0 [0xaac95000 > - 0xaacb2fff] > [ 2.157690] IOMMU: Prepare 0-16MiB unity mapping for LPC > [ 2.163011] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff > [Errors, here we go] > [ 2.170932] dmar: DRHD: handling fault status reg 3 > [ 2.170933] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O > [ 2.182486] dmar: DMAR:[DMA Write] Request device [00:02.0] fault addr ffffe000 > [ 2.182486] DMAR:[fault reason 05] PTE Write access is not set > [ 2.195705] dmar: DRHD: handling fault status reg 3 > [ 2.200570] dmar: DMAR:[DMA Read] Request device [00:02.0] fault addr ff873000 > [ 2.200570] DMAR:[fault reason 06] PTE Read access is not set > [ 2.213618] dmar: DRHD: handling fault status reg 3 > [..] This is the problem I'm working on. https://lkml.org/lkml/2012/11/26/814 Thansk, Takao Indoh -- 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/