Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760220AbXHWJQP (ORCPT ); Thu, 23 Aug 2007 05:16:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755125AbXHWJQA (ORCPT ); Thu, 23 Aug 2007 05:16:00 -0400 Received: from gir.skynet.ie ([193.1.99.77]:42272 "EHLO gir.skynet.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751544AbXHWJP7 (ORCPT ); Thu, 23 Aug 2007 05:15:59 -0400 Date: Thu, 23 Aug 2007 10:15:56 +0100 To: "Luck, Tony" Cc: Jeremy Higdon , Kamalesh Babulal , Andi Kleen , Andrew Morton , linux-kernel@vger.kernel.org, Balbir Singh , linux-ia64@vger.kernel.org Subject: Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Message-ID: <20070823091556.GA18456@skynet.ie> References: <46CC48FD.4000607@linux.vnet.ibm.com> <20070822091959.aa38fd3e.akpm@linux-foundation.org> <20070822172541.GA8058@bingen.suse.de> <46CC811C.9010600@linux.vnet.ibm.com> <617E1C2C70743745A92448908E030B2A023B2D39@scsmsx411.amr.corp.intel.com> <46CCB79E.7070109@linux.vnet.ibm.com> <617E1C2C70743745A92448908E030B2A023B2F6A@scsmsx411.amr.corp.intel.com> <20070822231111.GD89849@sgi.com> <617E1C2C70743745A92448908E030B2A023B2FD5@scsmsx411.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <617E1C2C70743745A92448908E030B2A023B2FD5@scsmsx411.amr.corp.intel.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: mel@skynet.ie (Mel Gorman) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1580 Lines: 34 On (22/08/07 16:27), Luck, Tony didst pronounce: > > The more ioc's you have, the more space you will use. > > Default SW IOTLB allocation is 64MB ... how much should we see > used per ioc? > > Kamelesh: You could try increasing the amount of sw iotlb space > available by booting with a swiotlb=131072 argument (argument > value is the number of 2K slabs to allocate ... 131072 would > give you four times as much space as the default allocation). > I tried that value and just in case swiotlb=262144. An IA-64 machines I have here fails with the same message anyway. i.e. [ 19.834906] mptbase: Initiating ioc1 bringup [ 20.317152] ioc1: LSI53C1030 C0: Capabilities={Initiator} [ 15.474303] scsi1 : ioc1: LSI53C1030 C0, FwRev=01032821h, Ports=1, MaxQ=222, IRQ=72 [ 20.669730] GSI 142 (level, low) -> CPU 5 (0x1200) vector 73 [ 20.675602] ACPI: PCI Interrupt 0000:41:03.0[A] -> GSI 142 (level, low) -> IRQ 73 [ 20.683508] mptbase: Initiating ioc2 bringup [ 21.166796] ioc2: LSI53C1030 C0: Capabilities={Initiator} [ 21.180539] DMA: Out of SW-IOMMU space for 263200 bytes at device ? [ 21.187018] Kernel panic - not syncing: DMA: Memory would be corrupted -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab - 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/