From: Daniel Kim <dkim@playmechanix.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Siva Reddy Kallam <siva.kallam@broadcom.com>,
Prashant Sreedharan <prashant@broadcom.com>,
Michael Chan <mchan@broadcom.com>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [Problem] Broadcom BCM5762 Ethernet tg3 times out with stack trace
Date: Thu, 1 Jun 2017 17:01:27 -0500 [thread overview]
Message-ID: <CANeD+K-O_umVCz-5O68TH9R9ADa22UJungTuYoHjSZRvvNrhmw@mail.gmail.com> (raw)
In-Reply-To: <CANeD+K_hYMuC_AqB97fjBt+NXCMi5r8KzCNpcvFBk5obKL_k=w@mail.gmail.com>
On Fri, May 12, 2017 at 6:12 PM, Daniel Kim <dkim@playmechanix.com> wrote:
> I believe I do have IOMMU enabled. At least the dmesg output seems to
> imply that I do:
> [ 1.141948] iommu: Adding device 0000:00:02.0 to group 0
> [ 1.142033] iommu: Adding device 0000:00:10.0 to group 1
> [ 1.142074] iommu: Adding device 0000:00:10.1 to group 1
> [ 1.142119] iommu: Adding device 0000:00:11.0 to group 2
> [ 1.142172] iommu: Adding device 0000:00:12.0 to group 3
> [ 1.142184] iommu: Adding device 0000:00:12.2 to group 3
> [ 1.142234] iommu: Adding device 0000:00:13.0 to group 4
> [ 1.142247] iommu: Adding device 0000:00:13.2 to group 4
> [ 1.142303] iommu: Adding device 0000:00:14.0 to group 5
> [ 1.142315] iommu: Adding device 0000:00:14.2 to group 5
> [ 1.142328] iommu: Adding device 0000:00:14.3 to group 5
> [ 1.142373] iommu: Adding device 0000:00:14.4 to group 6
> [ 1.142417] iommu: Adding device 0000:00:14.5 to group 7
> [ 1.142529] iommu: Adding device 0000:00:15.0 to group 8
> [ 1.142570] iommu: Adding device 0000:00:15.2 to group 8
> [ 1.142639] iommu: Adding device 0000:00:18.0 to group 9
> [ 1.142653] iommu: Adding device 0000:00:18.1 to group 9
> [ 1.142668] iommu: Adding device 0000:00:18.2 to group 9
> [ 1.142682] iommu: Adding device 0000:00:18.3 to group 9
> [ 1.142695] iommu: Adding device 0000:00:18.4 to group 9
> [ 1.142712] iommu: Adding device 0000:00:18.5 to group 9
> [ 1.142725] iommu: Adding device 0000:01:00.0 to group 0
> [ 1.142733] iommu: Adding device 0000:01:00.1 to group 0
> [ 1.142840] iommu: Adding device 0000:04:00.0 to group 8
> [ 1.143305] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
>
> The last kernel I used where the NIC mostly worked was 4.4.0 (x86-64).
> Even when it worked, it had this issue we've experienced since v3.13
> where the NIC would suddenly become unresponsive. It won't be
> considered disconnected from the network, but RX/TX packets, errors,
> dropped, etc. values displayed with ifconfig would show a number that
> looked suspiciously close to 32-bit INT_MAX.
>
> Since v4.8, I can trigger it much faster and it now prints out a call
> stack and other messages into dmesg.
I'd like to follow up on this since I haven't heard of any updates for
awhile. Is there anything I can do on my end to help?
next prev parent reply other threads:[~2017-06-01 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 8:53 [Problem] Broadcom BCM5762 Ethernet tg3 times out with stack trace Siva Reddy Kallam
2017-05-12 19:10 ` Daniel Kim
2017-05-12 21:45 ` Michael Chan
2017-05-12 23:12 ` Daniel Kim
2017-06-01 22:01 ` Daniel Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-06 12:17 Siva Reddy Kallam
2017-05-12 4:09 Siva Reddy Kallam
2017-05-11 15:25 Daniel Kim
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=CANeD+K-O_umVCz-5O68TH9R9ADa22UJungTuYoHjSZRvvNrhmw@mail.gmail.com \
--to=dkim@playmechanix.com \
--cc=mchan@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@broadcom.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).