Thread (21 messages) 21 messages, 6 authors, 2013-05-27

Re: BQL support in gianfar causes network hickup

From: Paul Gortmaker <hidden>
Date: 2013-02-06 01:56:11

On Tue, Feb 5, 2013 at 8:00 AM, Keitel, Tino (ALC NetworX GmbH)
[off-list ref] wrote:
On Di, 2012-11-27 at 05:32 -0800, Eric Dumazet wrote:
quoted
On Tue, 2012-11-27 at 13:42 +0100, Keitel, Tino (ALC NetworX GmbH)
wrote:
quoted
On Di, 2012-11-27 at 04:36 -0800, Eric Dumazet wrote:
quoted
Can you reproduce the problem using a single cpu ?
Yes, it is a single-CPU system.
Can you reproduce the problem without PTP running, or disabled in the
driver ?

(comment the "priv->hwts_tx_en = 1;" line)
I can't reproduce it with that line commented. However, so far I was
only able to reproduce it when starting the ptp2 client, so maybe this
is connected.
How critical is ptp2 for this?  And/or the platform details?  I can
try and reproduce it on an mpc8349 system and/or an mpc8548
system (and even an mpc8641D system) but I'd rather know that
was a meaningful chase and not a snipe hunt before going there.

So, in that respect, a "If you run this, you will get this" type of
error message would be good.   I understand that may be too
idealistic, though.

Thanks,
Paul.
--
quoted
By the way are any errata flagged in gfar_detect_errata() ?
This is from dmesg:

fsl-gianfar e0024000.ethernet: enabled errata workarounds, flags: 0x7

0x7 would be GFAR_ERRATA_74, GFAR_ERRATA_76 and GFAR_ERRATA_A002
according to drivers/net/ethernet/freescale/gianfar.h.

Regards,
Tino
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help