[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50A43828.6000702@oracle.com>
Date: Thu, 15 Nov 2012 08:32:40 +0800
From: Joe Jin <joe.jin@...cle.com>
To: "Dave, Tushar N" <tushar.n.dave@...el.com>
CC: "e1000-devel@...ts.sf.net" <e1000-devel@...ts.sf.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mary Mcgrath <mary.mcgrath@...cle.com>
Subject: Re: 82571EB: Detected Hardware Unit Hang
On 11/14/12 11:45, Dave, Tushar N wrote:
>> -----Original Message-----
>> From: Joe Jin [mailto:joe.jin@...cle.com]
>> Sent: Tuesday, November 13, 2012 6:48 PM
>> To: Dave, Tushar N
>> Cc: e1000-devel@...ts.sf.net; netdev@...r.kernel.org; linux-
>> kernel@...r.kernel.org; Mary Mcgrath
>> Subject: Re: 82571EB: Detected Hardware Unit Hang
>>
>> On 11/09/12 04:35, Dave, Tushar N wrote:
>>> All devices in path from root complex to 82571, should have *same* max
>> payload size otherwise it can cause hang.
>>> Can you double check this?
>>
>> Hi Tushar,
>>
>> Checked with hardware vendor and they said no way to modify the max
>> payload size from BIOS, can I modify it from driver side?
>
> If you want to change value for 82571 device you can do it from eeprom but for other upstream devices I am not sure. I will check with my team.
Hi Tushar,
Would you please help to fine the offset of max payload size in eeprom?
I'd like to have a try to modify it by ethtool.
Thanks in advance,
Joe
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists