All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Chan <michael.chan@broadcom.com>
To: Roman Steinhart <roman@aternos.org>
Cc: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Netdev <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: bnxt_en NIC driver crashes IO_PAGE_FAULT
Date: Tue, 8 Jun 2021 11:15:08 -0700	[thread overview]
Message-ID: <CACKFLinsTh1OimRj80qcP0Uai5uWsV5+vEPvXF+-kuKprgzC-A@mail.gmail.com> (raw)
In-Reply-To: <CAKrGhHJDas5WdrHWYrscAYijnybHtTNEPW6v_UMiOgnWFVVLxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 713 bytes --]

On Tue, Jun 8, 2021 at 10:53 AM Roman Steinhart <roman@aternos.org> wrote:
> We received a bunch of new servers with a Supermicro H12SSL-NT
> mainboard that has an embedded Broadcom BCM57416 NIC.
>
> On all those servers we observe crashes of the NIC driver (bnxt_en) from
> time to time. We're not able to manually reproduce this issue, it just occurs at
> some point. Also our monitoring does not show any irregularities(high traffic
> flow or sth. like this).
>

These IOMMU faults are seen on AMD systems, right?  We have also seen
similar issues on some AMD systems and have worked with AMD to debug
the issues.  I'll likely have someone who's more familiar with these
AMD IOMMU issues contact you.  Thanks.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]

       reply	other threads:[~2021-06-08 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKrGhHJDas5WdrHWYrscAYijnybHtTNEPW6v_UMiOgnWFVVLxg@mail.gmail.com>
2021-06-08 18:15 ` Michael Chan [this message]
2021-06-08 17:56 bnxt_en NIC driver crashes IO_PAGE_FAULT Roman Steinhart

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=CACKFLinsTh1OimRj80qcP0Uai5uWsV5+vEPvXF+-kuKprgzC-A@mail.gmail.com \
    --to=michael.chan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=roman@aternos.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.