From: Andrew Morton <akpm@linux-foundation.org>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Balbir Singh <balbir@linux.vnet.ibm.com>, Andi Kleen <ak@suse.de>,
linux-ia64@vger.kernel.org, "Luck, Tony" <tony.luck@intel.com>
Subject: Re: [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted
Date: Wed, 22 Aug 2007 09:19:59 -0700 [thread overview]
Message-ID: <20070822091959.aa38fd3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <46CC48FD.4000607@linux.vnet.ibm.com>
On Wed, 22 Aug 2007 20:02:29 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> Hi Andrew,
>
> Following Kernel panic was raised, when tried to boot using IA-64
> machine with 2.6.23-rc3-mm1 kernel.
> ===============================================
> [ 15.198125] target0:0:8: Ending Domain Validation
> [ 15.203117] target0:0:8: asynchronous
> [ 15.207377] scsi 0:0:8:0: Attached scsi generic sg1 type 3
> [ 16.971340] GSI 41 (level, low) -> CPU 4 (0x1000) vector 72
> [ 16.977053] ACPI: PCI Interrupt 0000:01:03.1[B] -> GSI 41 (level,
> low) -> IRQ 72
> [ 16.984767] mptbase: Initiating ioc1 bringup
> [ 17.465344] ioc1: LSI53C1030 C0: Capabilities={Initiator}
> [ 15.180382] scsi1 : ioc1: LSI53C1030 C0, FwRev=01032821h, Ports=1,
> MaxQ=222, IRQ=72
> [ 20.376426] GSI 142 (level, low) -> CPU 5 (0x1200) vector 73
> [ 20.382298] ACPI: PCI Interrupt 0000:41:03.0[A] -> GSI 142 (level,
> low) -> IRQ 73
> [ 20.390209] mptbase: Initiating ioc2 bringup
> [ 20.873561] ioc2: LSI53C1030 C0: Capabilities={Initiator}
> [ 20.880366] DMA: Out of SW-IOMMU space for 263200 bytes at device ?
> [ 20.886858] Kernel panic - not syncing: DMA: Memory would be corrupted
Gad, never seen that before. Andi, Tony: help?
next prev parent reply other threads:[~2007-08-22 16:20 UTC|newest]
Thread overview: 27+ 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 ` Andrew Morton [this message]
2007-08-22 17:25 ` Andi Kleen
2007-08-22 18:31 ` Kamalesh Babulal
2007-08-22 21:04 ` Luck, Tony
2007-08-22 22:24 ` Kamalesh Babulal
2007-08-22 22:56 ` 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
2007-08-23 17:22 ` Luck, Tony
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 would be corrupted) Yasunori Goto
2007-08-24 14:52 ` Mel Gorman
2007-08-24 15:49 ` Lee Schermerhorn
2007-08-24 17:00 ` Christoph Lameter
2007-08-24 18:03 ` Lee Schermerhorn
2007-08-24 18:08 ` Christoph Lameter
2007-08-24 17:02 ` Christoph Lameter
2007-08-24 16:46 ` Kamalesh Babulal
2007-08-28 22:41 ` Adam Litke
2007-08-23 9:22 ` [BUG] 2.6.23-rc3-mm1 Kernel panic - not syncing: DMA: Memory would be corrupted 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=20070822091959.aa38fd3e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox