From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jeremy Higdon <jeremy@sgi.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
Date: Thu, 23 Aug 2007 09:34:36 +0000 [thread overview]
Message-ID: <46CD51DC.6030602@linux.vnet.ibm.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A023B2FD5@scsmsx411.amr.corp.intel.com>
Luck, Tony wrote:
>> 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).
>
> -Tony
>
boot log after passing boot parameter swiotlb\x131072
[ 0.000000] 0: 32768 -> 131072
[ 0.000000] 0: 262144 -> 1703936
[ 0.000000] 1: 4194304 -> 4980736
[ 0.000000] Built 2 zonelists in Zone order, mobility grouping on.
Total pages: 1563903
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line:
BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-autobench root=/dev/sda2
console=tty0 console=ttyS0,115200n8 ro autobench_args: root=/dev/sda2
ABAT:1187857488 profile=2 swiotlb\x131072
[ 0.000000] kernel profiling enabled (shift: 2)
<<snip>>
[ 20.408360] mptbase: Initiating ioc2 bringup
[ 20.892659] ioc2: LSI53C1030 C0: Capabilities={Initiator}
[ 20.902432] DMA: Out of SW-IOMMU space for 263200 bytes at device ?
[ 20.908992]
[ 20.908993] Call Trace:
[ 20.913324] [<a0000001000144e0>] show_stack+0x80/0xa0
[ 20.913327] spà0000014322f8f0
bspà00000143229170
[ 20.926764] [<a000000100014530>] dump_stack+0x30/0x60
[ 20.926766] spà0000014322fac0
bspà00000143229158
[ 20.940225] [<a0000001003aaa50>] swiotlb_full+0x50/0x120
[ 20.940227] spà0000014322fac0
bspà00000143229120
[ 20.953915] [<a0000001003aac40>] swiotlb_map_single+0x120/0x1c0
[ 20.953916] spà0000014322fac0
bspà000001432290d8
[ 20.968223] [<a0000001003ab630>] swiotlb_alloc_coherent+0x150/0x240
[ 20.968226] spà0000014322fac0
bspà00000143229090
[ 20.982919] [<a000000100550860>] PrimeIocFifos+0x4c0/0xb20
[ 20.982922] spà0000014322fac0
bspà00000143229010
[ 20.996801] [<a000000100556a80>] mpt_do_ioc_recovery+0xd60/0x28e0
[ 20.996803] spà0000014322faf0
bspà00000143228f30
[ 21.011292] [<a00000010055c8f0>] mpt_attach+0x830/0x20e0
[ 21.011293] spà0000014322fdc0
bspà00000143228eb0
[ 21.025009] [<a0000001005667b0>] mptspi_probe+0x30/0x720
[ 21.025011] spà0000014322fdd0
bspà00000143228e60
[ 21.038722] [<a0000001003bb4b0>] pci_device_probe+0x1f0/0x2c0
[ 21.038724] spà0000014322fdd0
bspà00000143228e18
[ 21.052887] [<a00000010048f9e0>] driver_probe_device+0x180/0x400
[ 21.052888] spà0000014322fdd0
bspà00000143228dc8
[ 21.067276] [<a00000010048ff20>] __driver_attach+0xc0/0x160
[ 21.067277] spà0000014322fdd0
bspà00000143228d90
[ 21.081234] [<a00000010048dd90>] bus_for_each_dev+0xb0/0x120
[ 21.081236] spà0000014322fdd0
bspà00000143228d58
[ 21.095283] [<a00000010048f640>] driver_attach+0x40/0x60
[ 21.095285] spà0000014322fdf0
bspà00000143228d38
[ 21.108983] [<a00000010048e600>] bus_add_driver+0x120/0x400
[ 21.108985] spà0000014322fdf0
bspà00000143228cf8
[ 21.122942] [<a0000001004903c0>] driver_register+0xc0/0x180
[ 21.122943] spà0000014322fdf0
bspà00000143228cd8
[ 21.136906] [<a0000001003bb980>] __pci_register_driver+0xc0/0x140
[ 21.136908] spà0000014322fdf0
bspà00000143228ca0
[ 21.151422] [<a000000100943920>] mptspi_init+0x180/0x1c0
[ 21.151425] spà0000014322fe00
bspà00000143228c70
[ 21.166973] [<a0000001008fc5d0>] kernel_init+0x350/0x840
[ 21.166974] spà0000014322fe00
bspà00000143228c10
[ 21.180677] [<a000000100012150>] kernel_thread_helper+0xd0/0x100
[ 21.180679] spà0000014322fe30
bspà00000143228be0
[ 21.195082] [<a000000100008dc0>] start_kernel_thread+0x20/0x40
[ 21.195084] spà0000014322fe30
bspà00000143228be0
[ 21.209297] Kernel panic - not syncing: DMA: Memory would be corrupted
-
Kamalesh Babulal.
WARNING: multiple messages have this Message-ID (diff)
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Jeremy Higdon <jeremy@sgi.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 14:52:36 +0530 [thread overview]
Message-ID: <46CD51DC.6030602@linux.vnet.ibm.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A023B2FD5@scsmsx411.amr.corp.intel.com>
Luck, Tony wrote:
>> 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).
>
> -Tony
>
boot log after passing boot parameter swiotlb=131072
[ 0.000000] 0: 32768 -> 131072
[ 0.000000] 0: 262144 -> 1703936
[ 0.000000] 1: 4194304 -> 4980736
[ 0.000000] Built 2 zonelists in Zone order, mobility grouping on.
Total pages: 1563903
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line:
BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-autobench root=/dev/sda2
console=tty0 console=ttyS0,115200n8 ro autobench_args: root=/dev/sda2
ABAT:1187857488 profile=2 swiotlb=131072
[ 0.000000] kernel profiling enabled (shift: 2)
<<snip>>
[ 20.408360] mptbase: Initiating ioc2 bringup
[ 20.892659] ioc2: LSI53C1030 C0: Capabilities={Initiator}
[ 20.902432] DMA: Out of SW-IOMMU space for 263200 bytes at device ?
[ 20.908992]
[ 20.908993] Call Trace:
[ 20.913324] [<a0000001000144e0>] show_stack+0x80/0xa0
[ 20.913327] sp=e00000014322f8f0
bsp=e000000143229170
[ 20.926764] [<a000000100014530>] dump_stack+0x30/0x60
[ 20.926766] sp=e00000014322fac0
bsp=e000000143229158
[ 20.940225] [<a0000001003aaa50>] swiotlb_full+0x50/0x120
[ 20.940227] sp=e00000014322fac0
bsp=e000000143229120
[ 20.953915] [<a0000001003aac40>] swiotlb_map_single+0x120/0x1c0
[ 20.953916] sp=e00000014322fac0
bsp=e0000001432290d8
[ 20.968223] [<a0000001003ab630>] swiotlb_alloc_coherent+0x150/0x240
[ 20.968226] sp=e00000014322fac0
bsp=e000000143229090
[ 20.982919] [<a000000100550860>] PrimeIocFifos+0x4c0/0xb20
[ 20.982922] sp=e00000014322fac0
bsp=e000000143229010
[ 20.996801] [<a000000100556a80>] mpt_do_ioc_recovery+0xd60/0x28e0
[ 20.996803] sp=e00000014322faf0
bsp=e000000143228f30
[ 21.011292] [<a00000010055c8f0>] mpt_attach+0x830/0x20e0
[ 21.011293] sp=e00000014322fdc0
bsp=e000000143228eb0
[ 21.025009] [<a0000001005667b0>] mptspi_probe+0x30/0x720
[ 21.025011] sp=e00000014322fdd0
bsp=e000000143228e60
[ 21.038722] [<a0000001003bb4b0>] pci_device_probe+0x1f0/0x2c0
[ 21.038724] sp=e00000014322fdd0
bsp=e000000143228e18
[ 21.052887] [<a00000010048f9e0>] driver_probe_device+0x180/0x400
[ 21.052888] sp=e00000014322fdd0
bsp=e000000143228dc8
[ 21.067276] [<a00000010048ff20>] __driver_attach+0xc0/0x160
[ 21.067277] sp=e00000014322fdd0
bsp=e000000143228d90
[ 21.081234] [<a00000010048dd90>] bus_for_each_dev+0xb0/0x120
[ 21.081236] sp=e00000014322fdd0
bsp=e000000143228d58
[ 21.095283] [<a00000010048f640>] driver_attach+0x40/0x60
[ 21.095285] sp=e00000014322fdf0
bsp=e000000143228d38
[ 21.108983] [<a00000010048e600>] bus_add_driver+0x120/0x400
[ 21.108985] sp=e00000014322fdf0
bsp=e000000143228cf8
[ 21.122942] [<a0000001004903c0>] driver_register+0xc0/0x180
[ 21.122943] sp=e00000014322fdf0
bsp=e000000143228cd8
[ 21.136906] [<a0000001003bb980>] __pci_register_driver+0xc0/0x140
[ 21.136908] sp=e00000014322fdf0
bsp=e000000143228ca0
[ 21.151422] [<a000000100943920>] mptspi_init+0x180/0x1c0
[ 21.151425] sp=e00000014322fe00
bsp=e000000143228c70
[ 21.166973] [<a0000001008fc5d0>] kernel_init+0x350/0x840
[ 21.166974] sp=e00000014322fe00
bsp=e000000143228c10
[ 21.180677] [<a000000100012150>] kernel_thread_helper+0xd0/0x100
[ 21.180679] sp=e00000014322fe30
bsp=e000000143228be0
[ 21.195082] [<a000000100008dc0>] start_kernel_thread+0x20/0x40
[ 21.195084] sp=e00000014322fe30
bsp=e000000143228be0
[ 21.209297] Kernel panic - not syncing: DMA: Memory would be corrupted
-
Kamalesh Babulal.
next prev parent reply other threads:[~2007-08-23 9:34 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 14:32 [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Kamalesh Babulal
2007-08-22 16:19 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory Andrew Morton
2007-08-22 16:19 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Andrew Morton
2007-08-22 16:35 ` Andi Kleen
2007-08-22 17:25 ` Andi Kleen
2007-08-22 18:31 ` Kamalesh Babulal
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 21:04 ` Luck, Tony
2007-08-22 22:24 ` Kamalesh Babulal
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 22:56 ` Luck, Tony
2007-08-22 23:11 ` Jeremy Higdon
2007-08-22 23:11 ` Jeremy Higdon
2007-08-22 23:27 ` Luck, Tony
2007-08-22 23:27 ` Luck, Tony
2007-08-22 23:54 ` Jeremy Higdon
2007-08-22 23:54 ` Jeremy Higdon
2007-08-23 0:05 ` Luck, Tony
2007-08-23 0:05 ` Luck, Tony
2007-08-23 1:09 ` Jeremy Higdon
2007-08-23 1:09 ` Jeremy Higdon
2007-08-23 1:16 ` Jeremy Higdon
2007-08-23 1:16 ` Jeremy Higdon
2007-08-23 9:15 ` Mel Gorman
2007-08-23 9:15 ` Mel Gorman
2007-08-23 13:27 ` Yasunori Goto
2007-08-23 13:27 ` Yasunori Goto
2007-08-23 17:22 ` Luck, Tony
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-23 21:21 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted Andrew Morton
2007-08-23 21:21 ` 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 6:53 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Yasunori Goto
2007-08-24 6:53 ` 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 14:52 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Mel Gorman
2007-08-24 14:52 ` 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 15:49 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Lee Schermerhorn
2007-08-24 15:49 ` 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 17:00 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Christoph Lameter
2007-08-24 17:00 ` 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:03 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Lee Schermerhorn
2007-08-24 18:03 ` 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 18:08 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Christoph Lameter
2007-08-24 18:08 ` Christoph Lameter
2007-08-24 17:02 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel Christoph Lameter
2007-08-24 17:02 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Christoph Lameter
2007-08-24 17:02 ` Christoph Lameter
2007-08-24 16:46 ` Kamalesh Babulal
2007-08-24 16:58 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel Kamalesh Babulal
2007-08-24 16:46 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Kamalesh Babulal
2007-08-28 22:41 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Adam Litke
2007-08-28 22:41 ` [PATCH] Fix find_next_best_node (Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted) Adam Litke
2007-08-28 22:41 ` Adam Litke
2007-08-23 9:22 ` Kamalesh Babulal [this message]
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=46CD51DC.6030602@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=jeremy@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.