All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Alexis Bruemmer <alexisb@us.ibm.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops
Date: Thu, 15 May 2008 18:17:41 +0300	[thread overview]
Message-ID: <20080515151741.GF6778@il.ibm.com> (raw)
In-Reply-To: <1210816813.5596.13.camel@alexis>

On Wed, May 14, 2008 at 07:00:13PM -0700, Alexis Bruemmer wrote:

> I wanted to try and create a test version of this, at least for the
> calgary side, but ran into an error with this patch set:
> 
> Fusion MPT SAS Host driver 3.04.06
> ACPI: PCI Interrupt 0000:34:00.0[A] -> GSI 142 (level, low) -> IRQ 142
> mptbase: ioc0: Initiating bringup
> ioc0: LSISAS1078 C1: Capabilities={Initiator}
> mptbase: ioc0: PCI-MSI enabled
> Calgary: DMA error on CalIOC2 PHB 0x33
> Calgary: 0x02000000@CSR 0x00000000@PLSSR 0xb0008000@CSMR 0x00000000@MCK
> Calgary: 0x00000000@0x810 0xfee0c000@0x820 0x00000000@0x830
> 0x00000000@0x840 0x03804a00@0x850 0x00000000@0x860 0x00000000@0x870
> Calgary: 0x00000000@0xcb0

Calgary caught an errant DMA. If it was working before, we are
probably mis-programming the TCE tables. The first thing to check is
whether all dma_map_xxx calls by mptbase end up calling the Calgary
dma_ops.

Cheers,
Muli

  parent reply	other threads:[~2008-05-15 20:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  6:04 [PATCH 0/2] x86: per-device dma_mapping_ops FUJITA Tomonori
2008-05-13  6:04 ` [PATCH 1/2] add the device argument to dma_mapping_error FUJITA Tomonori
2008-05-13  6:04   ` [PATCH 2/2] x86: per-device dma_mapping_ops support FUJITA Tomonori
2008-05-14  5:55     ` Muli Ben-Yehuda
2008-05-15 20:45     ` Yinghai Lu
2008-05-16  3:44       ` FUJITA Tomonori
2008-05-13 15:39   ` [PATCH 1/2] add the device argument to dma_mapping_error Randy Dunlap
2008-05-15  1:12     ` FUJITA Tomonori
2008-05-14  5:49 ` [PATCH 0/2] x86: per-device dma_mapping_ops Muli Ben-Yehuda
2008-05-15  1:12   ` FUJITA Tomonori
2008-05-15  2:00     ` Alexis Bruemmer
2008-05-15  2:30       ` FUJITA Tomonori
2008-05-15 18:21         ` Alexis Bruemmer
2008-05-15 15:17       ` Muli Ben-Yehuda [this message]
2008-05-15 15:15     ` Muli Ben-Yehuda
2008-05-15  9:01 ` Andi Kleen
2008-05-15  9:16   ` FUJITA Tomonori
2008-05-15  9:30     ` Andi Kleen
2008-05-15  9:41       ` FUJITA Tomonori
2008-05-15 10:48         ` Andi Kleen
2008-05-15 15:32           ` Muli Ben-Yehuda
2008-05-16  3:44           ` FUJITA Tomonori
2008-05-16  5:24             ` Andi Kleen
2008-05-19  6:32               ` FUJITA Tomonori
2008-05-15 15:26         ` Muli Ben-Yehuda
2008-05-15 21:03           ` Andi Kleen
2008-05-15 21:39             ` Muli Ben-Yehuda
2008-05-15 21:45               ` Andi Kleen
2008-05-15 21:53                 ` Muli Ben-Yehuda
2008-05-15 22:05                   ` Muli Ben-Yehuda
2008-05-15 18:25     ` Alexis Bruemmer

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=20080515151741.GF6778@il.ibm.com \
    --to=muli@il.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexisb@us.ibm.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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.