netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Larson <clarson@mvista.com>
To: netdev@vger.kernel.org
Subject: MV643xx Ethernet Driver Issue on a Motorola PrPMC-275 board.
Date: Tue, 29 Jul 2008 10:49:09 -0700	[thread overview]
Message-ID: <488F5815.9020402@mvista.com> (raw)

Greetings,

I was wondering if anyone had any advice on an issue a customer of ours 
is running into.  When they run a series of bandwidth tests, slowly 
increasing the bandwidth & # of tcp connections to roughly 30Mbit at 
4000 connections, their machine panics.  An address passed to 
dma_unmap_single is beyond lowmem, as though it was corrupted in some 
fashion.  The address is the data pointer in the ethernet dma 
descriptors, it pulls a descriptor out of the ring in the packet receipt 
functions and at that point the address is wrong.  Nowhere in the driver 
is a descriptor set up with that address, yet the datasheet on the 
mv643xx doesn't seem to indicate that the dma engine ever writes to the 
descriptors themselves, only to the data they point to (as you'd 
expect).  Does anyone have any ideas on this?  I'm afraid that I'm a bit 
out of my depth on this issue.  The architecture is ppc.

Thanks.
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Software Engineer
MontaVista Software, Inc.

             reply	other threads:[~2008-07-29 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 17:49 Chris Larson [this message]
2008-07-30 23:56 ` MV643xx Ethernet Driver Issue on a Motorola PrPMC-275 board Lennert Buytenhek
2008-07-31 16:44   ` Chris Larson
2008-07-31 17:48     ` Lennert Buytenhek

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=488F5815.9020402@mvista.com \
    --to=clarson@mvista.com \
    --cc=netdev@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 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).