From: Stefan Agner Sent: Tuesday, May 09, 2017 2:23 AM
>To: Andy Duan ; Andrew Lunn
>Cc: feste...@gmail.com; netdev@vger.kernel.org; netdev-
>ow...@vger.kernel.org
>Subject: Re: FEC on i.MX 7 transmit queue timeout
>
>On 2017-05-07 19:13, Andy Duan wrote:
>> From: Andrew
On 2017-05-07 19:13, Andy Duan wrote:
> From: Andrew Lunn Sent: Friday, May 05, 2017 8:24 PM
>>To: Andy Duan
>>Cc: Stefan Agner ; feste...@gmail.com;
>>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>Subject: Re: FEC on i.MX 7 transmit queue timeout
>>
&
From: Andrew Lunn Sent: Friday, May 05, 2017 8:24 PM
>To: Andy Duan
>Cc: Stefan Agner ; feste...@gmail.com;
>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>Subject: Re: FEC on i.MX 7 transmit queue timeout
>
>> No, it is not workaround. As i said, quque1 and queue2
> No, it is not workaround. As i said, quque1 and queue2 are for AVB paths
> have higher priority in transmition.
Does this higher priority result in the low priority queue being
starved? Is that why the timer goes off? What happens when somebody
does use AVB. Are we back to the same problem? Thi
n
>>>>> Cc: fugang.d...@freescale.com; feste...@gmail.com;
>>>>> netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>>>> Subject: Re: FEC on i.MX 7 transmit queue timeout
>>>>>
>>>>> Hi Andy,
>>>>>
>>
om;
>>>> netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>>> Subject: Re: FEC on i.MX 7 transmit queue timeout
>>>>
>>>> Hi Andy,
>>>>
>>>> On 2017-04-20 19:48, Andy Duan wrote:
>>>>> On 2017年04月20日 07:15
r.kernel.org
>>> Subject: Re: FEC on i.MX 7 transmit queue timeout
>>>
>>> Hi Andy,
>>>
>>> On 2017-04-20 19:48, Andy Duan wrote:
>>>> On 2017年04月20日 07:15, Stefan Agner wrote:
>>>>> I tested again with imx6sx-fec compatible stri
On 2017-05-03 20:08, Andy Duan wrote:
> From: Stefan Agner Sent: Thursday, May 04, 2017 9:22 AM
>>To: Andy Duan
>>Cc: fugang.d...@freescale.com; feste...@gmail.com;
>>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>Subject: Re: FEC on i.MX 7 transmit queue ti
From: Stefan Agner Sent: Thursday, May 04, 2017 9:22 AM
>To: Andy Duan
>Cc: fugang.d...@freescale.com; feste...@gmail.com;
>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>Subject: Re: FEC on i.MX 7 transmit queue timeout
>
>Hi Andy,
>
>On 2017-04-20 19:48, Andy Du
Hi Andy,
On 2017-04-20 19:48, Andy Duan wrote:
> On 2017年04月20日 07:15, Stefan Agner wrote:
>> I tested again with imx6sx-fec compatible string. I could reproduce it
>> on a Colibri with i.MX 7Dual. But not always: It really depends whether
>> queue 2 is counting up or not. Just after boot, I check
On 2017年04月20日 07:15, Stefan Agner wrote:
> I tested again with imx6sx-fec compatible string. I could reproduce it
> on a Colibri with i.MX 7Dual. But not always: It really depends whether
> queue 2 is counting up or not. Just after boot, I check /proc/interrupts
> twice, if queue 2 is counting it
l.com;
>>>> netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>>> Subject: Re: FEC on i.MX 7 transmit queue timeout
>>>>
>>>> Hi Andy,
>>>>
>>>> On 2017-04-18 19:24, Andy Duan wrote:
>>>>> On 2017年04月19日 03
vger.kernel.org
>>> Subject: Re: FEC on i.MX 7 transmit queue timeout
>>>
>>> Hi Andy,
>>>
>>> On 2017-04-18 19:24, Andy Duan wrote:
>>>> On 2017年04月19日 03:46, Stefan Agner wrote:
>>>>> Hi,
>>>>>
>>>>&
On 2017-04-18 22:28, Andy Duan wrote:
> From: Stefan Agner Sent: Wednesday, April 19, 2017 1:02 PM
>>To: Andy Duan
>>Cc: fugang.d...@freescale.com; feste...@gmail.com;
>>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>>Subject: Re: FEC on i.MX 7 transmit queue ti
From: Stefan Agner Sent: Wednesday, April 19, 2017 1:02 PM
>To: Andy Duan
>Cc: fugang.d...@freescale.com; feste...@gmail.com;
>netdev@vger.kernel.org; netdev-ow...@vger.kernel.org
>Subject: Re: FEC on i.MX 7 transmit queue timeout
>
>Hi Andy,
>
>On 2017-04-18 19:24, Andy
Hi Andy,
On 2017-04-18 19:24, Andy Duan wrote:
> On 2017年04月19日 03:46, Stefan Agner wrote:
>> Hi,
>>
>> I noticed last week on upstream (v4.11-rc6) on a Colibri iMX7 board that
>> after a while (~10 minutes) the detdev wachdog prints a stacktrace and
>> the driver then continuously dumps the TX ri
On 2017年04月19日 03:46, Stefan Agner wrote:
> Hi,
>
> I noticed last week on upstream (v4.11-rc6) on a Colibri iMX7 board that
> after a while (~10 minutes) the detdev wachdog prints a stacktrace and
> the driver then continuously dumps the TX ring. I then did a quick test
> with 4.10, and realized
Hi,
I noticed last week on upstream (v4.11-rc6) on a Colibri iMX7 board that
after a while (~10 minutes) the detdev wachdog prints a stacktrace and
the driver then continuously dumps the TX ring. I then did a quick test
with 4.10, and realized it actually suffers the same issue, so it seems
not to
18 matches
Mail list logo
