From mboxrd@z Thu Jan 1 00:00:00 1970 From: troy.kisky@boundarydevices.com (Troy Kisky) Date: Fri, 08 Aug 2014 17:33:18 -0700 Subject: [BUG]: imx6q (wandboard): Very unstable ethernet since kernel 3.16 In-Reply-To: References: <1407503758.19455.1.camel@sharkbay.at> <20140808132754.GC30282@n2100.arm.linux.org.uk> <1407507023.19455.3.camel@sharkbay.at> <20140808143008.GD30282@n2100.arm.linux.org.uk> <1407509932.19455.7.camel@sharkbay.at> <53E548DB.90905@boundarydevices.com> Message-ID: <53E56C4E.9090708@boundarydevices.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 8/8/2014 3:51 PM, George Joseph wrote: > On Fri, Aug 8, 2014 at 4:02 PM, Troy Kisky > wrote: > > On 8/8/2014 7:58 AM, Thomas Scheiblauer wrote: > > > > > > Indeed, commenting out these 2 lines in > > arch/arm/boot/dts/imx6qdl-wandboard.dtsi fixes my problem without having > > to increase TX_RING_SIZE. > > Thank you very much! > > > Could you also please checkout commit > > commit 9fc77821b17155c6e0ab50b1e1dd80c2b0e63e98 > Author: Sascha Silbe > > Date: Thu Feb 6 23:24:13 2014 +0100 > > ARM: dts: imx6qdl-wandboard: use GPIO_6 for FEC interrupt > > > and see if it also shows ethernet instabilities? > > > I'm confused by the references to GPIO_6 and GPIO1_IO06 as it relates to the wandboard. According > to the schematic for both the rev B1 and C1, the GPIO_6 PAD is physically connected to pin 30 on the > camera interface and according to the dtb tree, GPIO1_IO06 isn't mapped to any PAD. > > This kinda fits with my own observation which is that Ethernet is working fine (40MB/s sustained) > regardless of whether fec is using "gpio1 6" and "intc 0 119" for extended interrupts or the default > "intc 0 118" and "intc 0 119". Otherwise stock 3.16.0 on WB Quad C1. > Are you using a wandboard also? With or without camera plugged in? Same question for Thomas. Do you have a camera? Troy