From mboxrd@z Thu Jan 1 00:00:00 1970 From: ipaton0@gmail.com (Iain Paton) Date: Tue, 19 Aug 2014 07:03:07 +0100 Subject: Oops: 17 SMP ARM (v3.16-rc2) In-Reply-To: References: <20140626151424.GT32514@n2100.arm.linux.org.uk> <20140627163108.GP32514@n2100.arm.linux.org.uk> <20140806095012.GN30282@n2100.arm.linux.org.uk> <20140806125550.GO30282@n2100.arm.linux.org.uk> <20140807121248.GY30282@n2100.arm.linux.org.uk> <20140808180900.GG30282@n2100.arm.linux.org.uk> <53F11FF6.8030303@gmail.com> Message-ID: <53F2E89B.80009@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 17/08/14 22:46, Fabio Estevam wrote: > Iain, > > On Sun, Aug 17, 2014 at 6:34 PM, Iain Paton wrote: >> On 15/08/14 06:42, Mattis Lorentzon wrote: >> >>> We mostly run SSH with benchmarks using NFS, it can probably be >>> triggered by using only SSH with the following loop: >>> >>> # while : ; do ssh arm-card date; done >> >> Mattis, >> >> What sort of time does it take for you to see a problem? >> >> I've been running the above for nearly two days on 3.16.0 on a board >> with fec interrupts routed through gpio_6 and haven't seen a hint of >> a problem. > > Thanks for testing. > > Which mx6 board have you used on this test? It's currently pointed at a RIoTboard (atheros phy) but I'm happy to try it against both a Sabre-Lite and a Wandboard B1, all running the same kernel binary, as well. I'm interested enough in why different people get different results with this that I'll put some time towards testing to try to help narrow down the cause.