From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: bruce.w.allan@intel.com, netdev@vger.kernel.org,
gospo@redhat.com, sassmann@redhat.com, stable@vger.kernel.org
Subject: Re: [net] e1000e: enable ECC on I217/I218 to catch packet buffer memory errors
Date: Tue, 29 Jan 2013 16:01:49 -0500 (EST) [thread overview]
Message-ID: <20130129.160149.1063934767478304765.davem@davemloft.net> (raw)
In-Reply-To: <1359369828-13663-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 28 Jan 2013 02:43:48 -0800
> From: Bruce Allan <bruce.w.allan@intel.com>
>
> In rare instances, memory errors have been detected in the internal packet
> buffer memory on I217/I218 when stressed under certain environmental
> conditions. Enable Error Correcting Code (ECC) in hardware to catch both
> correctable and uncorrectable errors. Correctable errors will be handled
> by the hardware. Uncorrectable errors in the packet buffer will cause the
> packet to be received with an error indication in the buffer descriptor
> causing the packet to be discarded. If the uncorrectable error is in the
> descriptor itself, the hardware will stop and interrupt the driver
> indicating the error. The driver will then reset the hardware in order to
> clear the error and restart.
>
> Both types of errors will be accounted for in statistics counters.
>
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Cc: <stable@vger.kernel.org> # 3.5.x & 3.6.x
> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
Applied.
prev parent reply other threads:[~2013-01-29 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 10:43 [net] e1000e: enable ECC on I217/I218 to catch packet buffer memory errors Jeff Kirsher
2013-01-28 12:38 ` Josh Boyer
2013-01-28 12:45 ` Jeff Kirsher
2013-01-28 17:46 ` Allan, Bruce W
2013-01-29 21:01 ` David Miller [this message]
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=20130129.160149.1063934767478304765.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bruce.w.allan@intel.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.com \
--cc=stable@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).