On 12/29/2014 04:33 AM, Yegor Yefremov wrote: > On Fri, Dec 12, 2014 at 8:19 PM, Yegor Yefremov > <yegorslists@xxxxxxxxxxxxxx> wrote: >> On Fri, Dec 12, 2014 at 6:32 PM, Felipe Balbi <balbi@xxxxxx> wrote: >>> Hi, >>> >>> On Fri, Dec 12, 2014 at 01:00:51PM +0100, Yegor Yefremov wrote: >>>> U-Boot version: 2014.07 >>>> Kernel config is omap2plus with enabled USB >>>> >>>> # cat /proc/version >>>> Linux version 3.18.0 (user@user-VirtualBox) (gcc version 4.8.3 >>>> 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #6 SMP >>>> Mon Dec 8 22:47:43 CET 2014 >>> >>> Wasn't GCC 4.8.x total crap for building ARM kernels ? IIRC it was even >>> blacklisted. Can you try with 4.9.x just to make sure ? >> >> Will do. > > Adding linux-omap. Beginning of this discussion: > http://comments.gmane.org/gmane.linux.network/341427 > > Quick summary: starting with kernel 3.18 or commit > 55601c9f24670ba926ebdd4d712ac3b177232330 am335x (at least BBB and some > custom boards) stalls at high network load. Reproducible via nuttcp > within some minutes > > nuttcp -S (on BBB) > nuttcp -t -N 4 -T30m 192.168.1.235 (on host) > > As Felipe Balbi suggested, I tried both 4.8.3 and 4.9.2 toolchains, > but both show the same behavior. > > Linux version 3.18.0 (user@user-VirtualBox) (gcc version 4.8.3 > 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #6 SMP > Mon Dec 8 22:47:43 CET 2014 > Linux version 3.18.1 (user@user-VirtualBox) (gcc version 4.9.2 > (Buildroot 2015.02-git-00582-g10b9761) ) #1 SMP Mon Dec 29 09:22:29 > CET 2014 > > Let me know, if you can reproduce this issue. I have seen the irq 0 error messages on the black since 3.18+, but didn't bisect it yet. For me, these errors occurred with a slightly misconfigured emacs24-nox, which drove the cpu load way up - over 50% - with just cursor movement (it still gets above 20% which seems unacceptably high). I'm not sure if all the crashes were over ssh; I hadn't considered the cpsw relevant until reading this. I'll retest over the serial console. I have seen abrupt resets without messages on earlier kernels so perhaps the commit is not the root cause. Regards, Peter Hurley -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
