From: Patrick Schaaf <netdev@bof.de>
To: NETDEV <netdev@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>, ariele@broadcom.com
Subject: kernel 3.14.53 + bnx2x loss of connectivity / parity errors / MCP SCPAD
Date: Wed, 04 Nov 2015 12:31:46 +0100 [thread overview]
Message-ID: <1727409.Ct3NHyBiXb@rofl> (raw)
Dear netdevs,
on a production server (HP DL380 Gen9 with HP 10GE dual port card - bnx2x
driver), I just encountered a full loss of connectivity through the 10 GE
ports. Kernel in use is vanilla 3.14.53.
On the console I could see this (timestamps omitted, have to type by hand,
damn ILO console does not let me copy+paste text...)
MCP SCPAD
MCP SCPAD
bnx2x 0000:04:00.1 eth1: Parity errors detected in blocks:
MCP SCPAD
MCP SCPAD
bnx2x 0000:04:00.0 eth0: Parity errors detected in blocks:
bnx2x: [bnx2x_attn_int_deasserted3:4080(eth0)]LATCHED attention 0x80000000
(masked)
MCP SCPAD
...
systemd-journald[491]: /dev/kmsg buffer overrun, some messages lost.
Some googling around finds:
https://github.com/torvalds/linux/commit/ad6afbe9578d1fa26680faf78c846bd8c00d1d6e
which might be related. If I read that correctly (and I have no real idea what
I'm talking about, sorry...) that patch removes superflous printks which
might, e.g. in our case, hide the real cause. i.e. even with that patch we
would have had a problem / loss of connectivity, but we might know better why.
Maybe that changeset would be suitable for backporting to long term stable
kernels?
Incidentally, how should these parity events be judged generally? Hope it's a
one time cosmic ray incident? Cry "faulty hardware, please repair" to the
supplier? Anything else?
best regards
Patrick
next reply other threads:[~2015-11-04 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:31 Patrick Schaaf [this message]
2015-11-05 6:45 ` kernel 3.14.53 + bnx2x loss of connectivity / parity errors / MCP SCPAD Yuval Mintz
2015-11-05 8:25 ` Patrick Schaaf
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=1727409.Ct3NHyBiXb@rofl \
--to=netdev@bof.de \
--cc=ariele@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--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).