public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Mel Gorman <mel@skynet.ie>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	Jeremy Higdon <jeremy@sgi.com>,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	linux-ia64@vger.kernel.org
Subject: Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted
Date: Thu, 23 Aug 2007 13:27:45 +0000	[thread overview]
Message-ID: <20070823221005.0D76.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <20070823091556.GA18456@skynet.ie>

> 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\x131072 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&2144. 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\x01032821h, Ports=1, MaxQ"2, IRQr
> [   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

I saw same trouble on my box, and I chased what was wrong.
Here is today's progress of mine.

__get_free_pages() of swiotlb_alloc_coherent() fails in rc3-mm1.
(See following patch)
But, it doesn't fail on rc2-mm2, and kernel can boot up.

Hmmm....


(2.6.23-rc3-mm1)
---
swiotlb_alloc_coherent flags! order=3 ret\000000000000000
DMA: Out of SW-IOMMU space for 266368 bytes at device ?
Kernel panic - not syncing: DMA: Memory would be corrupted
---




(2.6.23-rc2-mm2)
---
swiotlb_alloc_coherent flags! order=3 retà00000020080000
           :
       (boot up continue...)

---
 lib/swiotlb.c |    2 ++
 1 file changed, 2 insertions(+)

Index: current/lib/swiotlb.c
=================================--- current.orig/lib/swiotlb.c	2007-08-23 22:27:01.000000000 +0900
+++ current/lib/swiotlb.c	2007-08-23 22:29:49.000000000 +0900
@@ -455,6 +455,8 @@ swiotlb_alloc_coherent(struct device *hw
 	flags |= GFP_DMA;
 
 	ret = (void *)__get_free_pages(flags, order);
+
+	printk("%s flags=%0x order=%d ret=%p\n",__func__, flags, order, ret);
 	if (ret && address_needs_mapping(hwdev, virt_to_bus(ret))) {
 		/*
 		 * The allocated memory isn't reachable by the device.


-- 
Yasunori Goto 



  reply	other threads:[~2007-08-23 13:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46CC48FD.4000607@linux.vnet.ibm.com>
2007-08-22 16:19 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Andrew Morton
2007-08-22 16:35   ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Andi Kleen
2007-08-22 18:43     ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Kamalesh Babulal
2007-08-22 21:04       ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Luck, Tony
2007-08-22 22:36         ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Kamalesh Babulal
2007-08-22 22:56           ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Luck, Tony
2007-08-22 23:11             ` Jeremy Higdon
2007-08-22 23:27               ` Luck, Tony
2007-08-22 23:54                 ` Jeremy Higdon
2007-08-23  0:05                   ` Luck, Tony
2007-08-23  1:09                     ` Jeremy Higdon
2007-08-23  1:16                       ` Jeremy Higdon
2007-08-23  9:15                 ` Mel Gorman
2007-08-23 13:27                   ` Yasunori Goto [this message]
2007-08-23 17:22                     ` Luck, Tony
2007-08-23 21:21                       ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Andrew Morton
2007-08-24  6:53                         ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory wo Yasunori Goto
2007-08-24 14:52                           ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memor Mel Gorman
2007-08-24 15:49                             ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Lee Schermerhorn
2007-08-24 17:00                               ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel Christoph Lameter
2007-08-24 18:03                                 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Lee Schermerhorn
2007-08-24 18:08                                   ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel Christoph Lameter
2007-08-24 17:02                             ` Christoph Lameter
2007-08-24 16:58                           ` Kamalesh Babulal
2007-08-28 22:41                           ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Adam Litke
2007-08-23  9:34                 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Kamalesh Babulal

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=20070823221005.0D76.Y-GOTO@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=jeremy@sgi.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@skynet.ie \
    --cc=tony.luck@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