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 will happen! > > But if only queue 0 is mostly in use, then it seems to work just fine. If your case is only running best effort like tcp/udp, you can re-set the "fsl,num-tx-queues" and "fsl,num-rx-queues" to 1 in board dts file. Other two queues are for AVB audio/video queues, they have high priority than queue 0. If running iperf tcp test on the three queues, then the tcp segment may be out-of-order that cause net watchdog timeout. > > I also tried i.MX 7Dual SabreSD here, and the same thing. I had to > reboot 3 times, then queue 2 was counting: > 57: 8 GIC-0 150 Level 30be0000.ethernet > 58: 20137 GIC-0 151 Level 30be0000.ethernet > 59: 9269 GIC-0 152 Level 30be0000.ethernet > > It took me about 40 minutes on Sabre until it happened, and I had to > force it using iperf, but then I got the ring dumps: My board had ran more than 47 hours with nfs rootfs in 4.11.0-rc6, but not running iperf. I am testing with iperf.
Andy
