From: Gavin Shan <gwshan@linux•vnet.ibm.com>
To: IanJiang <ianjiang.cn@gmail•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: EEH error in doing DMA with PEX 8619
Date: Tue, 11 Apr 2017 08:24:42 +1000 [thread overview]
Message-ID: <20170410222442.GA11610@gwshan> (raw)
In-Reply-To: <1491826953201-121121.post@n7.nabble.com>
On Mon, Apr 10, 2017 at 05:22:33AM -0700, IanJiang wrote:
>Hi all!
>
>I am porting PLX driver for PEX 8619 to a power8 machine with CentOS-7.3.
>The PEX 8619 is used as an NTB (Non-Transparent Bridge).
>
>First, two DMA buffer are allocated with dma_alloc_coherent() and the
>physical address are:
>src: 0x 00000000_60600000
>dst: 0x 00000000_60800000
>Then, a DMA transfer is started and an EEH is reported in dmesg.
>
>This DMA test is OK at an x86_64 platform.
>
>Here are the details. Any suggestion is appreciated!
.../...
>[72634.742182] brdgCtl: 00000002
>[72634.742183] RootSts: 0002004f 00400000 f0820008 00100147 00002800
>[72634.742184] RootErrSts: 00000000 00008000 00000000
>[72634.742185] PhbSts: 0000001c00000000 0000001c00000000
>[72634.742186] Lem: 0000000004000000 42498e327f502eae
>0000000000000000
>[72634.742189] InAErr: 0000000000004000 0000000000004000
>8000000060600001 8 400000000000001
>[72634.742190] PE[ 1] A/B: 8200302500000000 8000000060600000
Please check if memory physical address (instead of DMA address) is used
in the driver. The EEH error is caused by DMA address 0x60600000 and it's
not having a corresponding TCE entry.
Thanks,
Gavin
next prev parent reply other threads:[~2017-04-10 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 12:22 EEH error in doing DMA with PEX 8619 IanJiang
2017-04-10 22:24 ` Gavin Shan [this message]
2017-04-11 2:04 ` IanJiang
2017-04-11 2:15 ` Benjamin Herrenschmidt
2017-04-11 4:42 ` Gavin Shan
2017-04-11 9:26 ` IanJiang
2017-04-11 9:35 ` Benjamin Herrenschmidt
2017-04-12 1:39 ` IanJiang
2017-04-12 1:50 ` Benjamin Herrenschmidt
2017-04-12 8:42 ` IanJiang
2017-04-12 13:53 ` Benjamin Herrenschmidt
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=20170410222442.GA11610@gwshan \
--to=gwshan@linux$(echo .)vnet.ibm.com \
--cc=ianjiang.cn@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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