From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Peter LaDow <petela@gocougs.wsu.edu>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Inbound PCI and Memory Corruption
Date: Thu, 25 Jul 2013 08:08:42 +1000 [thread overview]
Message-ID: <1374703722.6142.5.camel@pasglop> (raw)
In-Reply-To: <CAN8Q1EdAA6ZfYSdTJ6ieZxjuqTF7Cr9Bt6fo2qejbtXoZ=ce6g@mail.gmail.com>
On Wed, 2013-07-24 at 08:39 -0700, Peter LaDow wrote:
> A bit of history that may help. We were using an e100 (an 82559)
> part, but Intel EOL'd that part so we picked up the 82540EP (which
> they have also recently EOL'd). The e100 driver uses a different DMA
> model. It uses pci_map_single/pci_unmap_single along with
> pci_dma_sync_single_for* calls (as well as other PCI calls). The
> e1000 driver, however, does not use the pci_* calls. We have never
> had a problem with the e100 parts. I don't suppose the use of
> pci_map_* vs dma_map_* makes a difference does it?
No, they resolve to the same thing under the hood. Did you do other
changes ? Could it be another unrelated kernel bug causing something
like use-after-free of network buffer or similar oddity unrelated to the
network driver ?
Have you tried with different kernel versions ?
Cheers,
Ben.
next prev parent reply other threads:[~2013-07-24 22:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 16:56 Inbound PCI and Memory Corruption Peter LaDow
2013-06-21 17:14 ` Peter LaDow
2013-06-23 0:00 ` Benjamin Herrenschmidt
2013-06-24 0:56 ` Peter LaDow
2013-06-24 1:16 ` Benjamin Herrenschmidt
2013-06-24 3:47 ` Peter LaDow
2013-06-24 3:49 ` Benjamin Herrenschmidt
2013-06-25 18:44 ` Peter LaDow
2013-07-10 21:06 ` Peter LaDow
2013-07-10 21:40 ` Benjamin Herrenschmidt
2013-07-10 22:16 ` Peter LaDow
2013-07-11 21:00 ` Peter LaDow
2013-07-18 21:30 ` Peter LaDow
2013-07-18 22:02 ` Benjamin Herrenschmidt
2013-07-19 17:44 ` Scott Wood
2013-07-19 13:46 ` Gerhard Sittig
2013-07-24 4:22 ` Peter LaDow
2013-07-24 4:27 ` Benjamin Herrenschmidt
2013-07-24 15:39 ` Peter LaDow
2013-07-24 22:08 ` Benjamin Herrenschmidt [this message]
2013-07-25 6:13 ` Peter LaDow
2013-08-02 15:01 ` Peter LaDow
2013-07-24 8:40 ` David Laight
2013-07-19 20:13 ` Timur Tabi
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=1374703722.6142.5.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=petela@gocougs.wsu.edu \
/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).