On Sat, Apr 14, 2018 at 9:17 PM, Kai-Heng Feng
wrote:
> Hi Satish,
>
>> On 2018Mar21, at 00:57, Kai-Heng Feng wrote:
>>
>> Satish Baddipadige wrote:
>>
>>> On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy Kallam
>>> wrote:
On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
wrote:
> O
Hi Satish,
> On 2018Mar21, at 00:57, Kai-Heng Feng wrote:
>
> Satish Baddipadige wrote:
>
>> On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy Kallam
>> wrote:
>>> On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
>>> wrote:
On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng
wrote:
>
Satish Baddipadige wrote:
On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy Kallam
wrote:
On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
wrote:
On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng
wrote:
Hi Broadcom folks,
We are now enabling a new platform with tg3 nic, unfortunately we
obse
On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy Kallam
wrote:
> On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
> wrote:
>> On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng
>> wrote:
>>> Hi Broadcom folks,
>>>
>>> We are now enabling a new platform with tg3 nic, unfortunately we observed
>>> the b
On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
wrote:
> On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng
> wrote:
>> Hi Broadcom folks,
>>
>> We are now enabling a new platform with tg3 nic, unfortunately we observed
>> the bug [1] that dated back to 2015.
>> I tried commit 4419bb1cedcd ("tg3:
On Fri, Feb 9, 2018 at 10:41 AM, Kai Heng Feng
wrote:
> Hi Broadcom folks,
>
> We are now enabling a new platform with tg3 nic, unfortunately we observed
> the bug [1] that dated back to 2015.
> I tried commit 4419bb1cedcd ("tg3: Add workaround to restrict 5762 MRRS to
> 2048”) but it does’t work.
Hi Broadcom folks,
We are now enabling a new platform with tg3 nic, unfortunately we observed
the bug [1] that dated back to 2015.
I tried commit 4419bb1cedcd ("tg3: Add workaround to restrict 5762 MRRS to
2048”) but it does’t work.
Do you have any idea how to solve the issue?
[1] https://
