From: Joe Jin <joe.jin@oracle.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Fujinaka, Todd" <todd.fujinaka@intel.com>,
Mary Mcgrath <mary.mcgrath@oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel@lists.sf.net" <e1000-devel@lists.sf.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [E1000-devel] 82571EB: Detected Hardware Unit Hang
Date: Wed, 28 Nov 2012 16:31:14 +0800 [thread overview]
Message-ID: <50B5CBD2.5020804@oracle.com> (raw)
In-Reply-To: <1354039840.2701.14.camel@bwh-desktop.uk.solarflarecom.com>
On 11/28/12 02:10, Ben Hutchings wrote:
> On Tue, 2012-11-27 at 17:32 +0000, Fujinaka, Todd wrote:
>> Forgive me if I'm being too repetitious as I think some of this has
>> been mentioned in the past.
>>
>> We (and by we I mean the Ethernet part and driver) can only change the
>> advertised availability of a larger MaxPayloadSize. The size is
>> negotiated by both sides of the link when the link is established. The
>> driver should not change the size of the link as it would be poking at
>> registers outside of its scope and is controlled by the upstream
>> bridge (not us).
> [...]
>
> MaxPayloadSize (MPS) is not negotiated between devices but is programmed
> by the system firmware (at least for devices present at boot - the
> kernel may be responsible in case of hotplug). You can use the kernel
> parameter 'pci=pcie_bus_perf' (or one of several others) to set a policy
> that overrides this, but no policy will allow setting MPS above the
> device's MaxPayloadSizeSupported (MPSS).
>
Ben,
Unfortunately I'm using 3.0.x kernel and this is not included in the kernel.
So I'm trying to use ethtool modify it from eeprom to see if help or no.
Todd, I'll review all MaxPayload for all devices, but need to say if it mismatch,
customer could not modify it from BIOS for there was not entry at there, to
test it, we have to find how to verify if this is the root cause, so still
need to find the offset in eeprom.
Thanks in advance,
Joe
next prev parent reply other threads:[~2012-11-28 8:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 6:24 82571EB: Detected Hardware Unit Hang Joe Jin
2012-11-08 20:35 ` Dave, Tushar N
2012-11-09 1:22 ` Joe Jin
2012-11-14 2:47 ` Joe Jin
2012-11-14 3:45 ` Dave, Tushar N
2012-11-15 0:32 ` Joe Jin
2012-11-15 20:26 ` Dave, Tushar N
2012-11-19 5:38 ` Joe Jin
2012-11-20 8:59 ` Dave, Tushar N
2012-11-20 13:24 ` Joe Jin
2012-11-26 16:23 ` [E1000-devel] " Fujinaka, Todd
2012-11-27 0:59 ` Joe Jin
2012-11-27 2:06 ` Mary Mcgrath
2012-11-27 17:32 ` [E1000-devel] " Fujinaka, Todd
2012-11-27 18:10 ` Ben Hutchings
2012-11-27 18:24 ` Fujinaka, Todd
2012-11-28 8:31 ` Joe Jin [this message]
2012-11-28 15:53 ` Fujinaka, Todd
2012-11-29 3:10 ` Ethan Zhao
2012-11-29 15:52 ` Fujinaka, Todd
2012-12-19 3:04 ` Joe Jin
2012-12-19 5:52 ` Yijing Wang
2012-12-19 6:13 ` Joe Jin
2012-11-20 13:24 ` Joe Jin
2012-11-14 3:37 ` Li Yu
2012-11-14 3:43 ` Dave, Tushar N
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=50B5CBD2.5020804@oracle.com \
--to=joe.jin@oracle.com \
--cc=bhutchings@solarflare.com \
--cc=e1000-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mary.mcgrath@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=todd.fujinaka@intel.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).