From: Prashant Sreedharan <prashant@broadcom.com>
To: Toan Pham <tpham3783@gmail.com>
Cc: Michael Chan <mchan@broadcom.com>, <sanjeevb@broadcom.com>,
<netdev@vger.kernel.org>
Subject: Re: [Problem] broadcom tg3 network driver disconnects under high load
Date: Tue, 28 Apr 2015 13:43:01 -0700 [thread overview]
Message-ID: <1430253781.26841.21.camel@prashant> (raw)
In-Reply-To: <CAGNmLEOJxarDZxmoXQfruPQ3RP89=h_zOTfBw-Fzq+Vizg315g@mail.gmail.com>
On Tue, 2015-04-28 at 16:06 -0400, Toan Pham wrote:
> > We were able to reproduce this issue internally only with iommu enabled.
>
> My last test to collect lspci-info took about 5 hours over a gigabit
> network for the bug to show up. My setup was running 3 tx scp
> sessions, each transferring a 1GB file outbound, and 1 rx scp session
> copying another 1GB file inbound. In a production environment with
> the BCM5762 NIC running as a server, I observed that the failure rate
> is about 1.65/week. Please perform a similar test with iommu
> disabled, and leave it running for days if need be.
Sure will try
>
>
> > Meanwhile can you try the attached patch and see if you are able to reproduce the problem ?
>
> No problem. I will apply the patch to kernel 4.0 and report back the
> result. Let me know if you need me to turn on any debug options like
> pcie trace, dev debug etc.... Thanks
If you can collect pcie trace that would be great. Thanks
next prev parent reply other threads:[~2015-04-28 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:33 [Problem] broadcom tg3 network driver disconnects under high load Toan Pham
2015-04-24 20:56 ` Michael Chan
2015-04-27 22:10 ` Toan Pham
2015-04-28 18:11 ` Michael Chan
2015-04-28 18:53 ` Toan Pham
2015-04-28 19:01 ` Prashant Sreedharan
2015-04-28 20:06 ` Toan Pham
2015-04-28 20:43 ` Prashant Sreedharan [this message]
2015-04-29 17:34 ` Toan Pham
2015-04-29 18:55 ` Prashant Sreedharan
[not found] ` <FB3F1E16BFB90C48B98EE49AA520E9667BC552@SJEXCHMB09.corp.ad.broadcom.com>
2015-08-10 12:20 ` Satish Baddipadige
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=1430253781.26841.21.camel@prashant \
--to=prashant@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sanjeevb@broadcom.com \
--cc=tpham3783@gmail.com \
/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).