From: Oliver <oohall@gmail.com>
To: Alistair Popple <alistair@popple.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Shawn Anastasio <shawn@anastas.io>,
David Gibson <david@gibson.dropbear.id.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Sam Bobroff <sbobroff@linux.ibm.com>
Subject: Re: [PATCH kernel v3 0/3] powerpc/ioda2: Yet another attempt to allow DMA masks between 32 and 59
Date: Thu, 6 Jun 2019 22:07:54 +1000 [thread overview]
Message-ID: <CAOSf1CEKwFHLHLC+CAiEiH=9v+hfRgTSuNUH3hXR4eDyQM1G9g@mail.gmail.com> (raw)
In-Reply-To: <4003261.yxAxO8Uj8t@townsend>
On Thu, Jun 6, 2019 at 5:17 PM Alistair Popple <alistair@popple.id.au> wrote:
>
> I have been hitting EEH address errors testing this with some network
> cards which map/unmap DMA addresses more frequently. For example:
>
> PHB4 PHB#5 Diag-data (Version: 1)
> brdgCtl: 00000002
> RootSts: 00060020 00402000 a0220008 00100107 00000800
> PhbSts: 0000001c00000000 0000001c00000000
> Lem: 0000000100000080 0000000000000000 0000000000000080
> PhbErr: 0000028000000000 0000020000000000 2148000098000240 a008400000000000
> RxeTceErr: 2000000000000000 2000000000000000 c000000000000000 0000000000000000
> PblErr: 0000000000020000 0000000000020000 0000000000000000 0000000000000000
> RegbErr: 0000004000000000 0000004000000000 61000c4800000000 0000000000000000
> PE[000] A/B: 8300b03800000000 8000000000000000
>
> Interestingly the PE[000] A/B data is the same across different cards
> and drivers.
TCE page fault due to permissions so odds are the DMA address was unmapped.
What cards did you get this with? I tried with one of the common
BCM5719 NICs and generated network traffic by using rsync to copy a
linux git tree to the system and it worked fine.
next prev parent reply other threads:[~2019-06-06 12:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:03 [PATCH kernel v3 0/3] powerpc/ioda2: Yet another attempt to allow DMA masks between 32 and 59 Alexey Kardashevskiy
2019-05-30 7:03 ` [PATCH kernel v3 1/3] powerpc/iommu: Allow bypass-only for DMA Alexey Kardashevskiy
2019-06-03 2:03 ` David Gibson
2019-05-30 7:03 ` [PATCH kernel v3 2/3] powerpc/powernv/ioda2: Allocate TCE table levels on demand for default DMA window Alexey Kardashevskiy
2019-07-08 7:01 ` alistair
2019-05-30 7:03 ` [PATCH kernel v3 3/3] powerpc/powernv/ioda2: Create bigger default window with 64k IOMMU pages Alexey Kardashevskiy
2019-07-08 7:01 ` alistair
2019-07-09 0:57 ` Alexey Kardashevskiy
2019-06-06 4:11 ` [PATCH kernel v3 0/3] powerpc/ioda2: Yet another attempt to allow DMA masks between 32 and 59 Shawn Anastasio
2019-06-06 7:17 ` Alistair Popple
2019-06-06 12:07 ` Oliver [this message]
2019-06-07 1:41 ` Alistair Popple
2019-06-10 5:19 ` Alexey Kardashevskiy
2019-06-12 5:05 ` Shawn Anastasio
2019-06-12 6:16 ` Oliver O'Halloran
2019-06-12 19:14 ` Shawn Anastasio
2019-06-12 7:07 ` Alexey Kardashevskiy
2019-06-12 19:15 ` Shawn Anastasio
2019-06-18 4:26 ` Shawn Anastasio
2019-06-18 6:39 ` Alexey Kardashevskiy
2019-06-18 7:00 ` Shawn Anastasio
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='CAOSf1CEKwFHLHLC+CAiEiH=9v+hfRgTSuNUH3hXR4eDyQM1G9g@mail.gmail.com' \
--to=oohall@gmail.com \
--cc=aik@ozlabs.ru \
--cc=alistair@popple.id.au \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sbobroff@linux.ibm.com \
--cc=shawn@anastas.io \
/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;
as well as URLs for NNTP newsgroup(s).