netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: jeffrey.t.kirsher@intel.com, ayyappan.veeraiyan@intel.com,
	john.ronciak@intel.com, jesse.brandeburg@intel.com,
	auke-jan.h.kok@intel.com
Cc: linux-pci@atrey.karlin.mff.cuni.cz, netdev@vger.kernel.org
Subject: Intel ixgb driver bug in linux-2.6.17-rc6-mm2
Date: Tue, 20 Jun 2006 14:35:35 -0500	[thread overview]
Message-ID: <20060620193535.GG9200@austin.ibm.com> (raw)


Hi,

I sat down to do some testing of the ixgb driver a few days ago, and
get failures within seconds.  From what I can tell, I'm getting either a
DMA to a bad address or some other PCI bus error, not sure which. 
The problem appears to happen only for the driver that's in
2.6.17-rc6-mm2. As a sanity check, I'm testing the SuSE SLES10 beta,
which is 2.6.16 based, and it doesn't seem to have any problems.

My test is dirt-simple: telnet to the chargen port.  After an eyeblink,
I get the pci bus error, that's that. "eyeblink" is after about 300MBytes
transfered.  That was with a driver with NAPI enabled. I tried again
with NAPI disabled, and got to about 1.8 GB transfered in two eyeblinks.

To make sure that I'm not dealing with faulty hardware, I tried the same
thing w/ SLES10 2.6.16.18-1.8  and have gotten to RX bytes:20889480686
(19921.7 Mb) so far, with no problems. I don't have easy access to a PCI
bus analyzer, otherwise, I'd tell you more. Ideas? Suggestions? 

I could try taking the diff between these two driver versions, and
seeing what change caused the problem, but thought I should email first,
before doing that.

--linas

             reply	other threads:[~2006-06-20 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 19:35 Linas Vepstas [this message]
2006-06-20 21:13 ` Intel ixgb driver bug in linux-2.6.17-rc6-mm2 Jesse Brandeburg
2006-06-21 20:18   ` Linas Vepstas

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=20060620193535.GG9200@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=ayyappan.veeraiyan@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --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).