From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Kozlowski Subject: Re: [PATCH] ARM: exynos_defconfig: Enable DWC2 USB driver and USB ethernet gadget Date: Wed, 26 Aug 2015 10:44:06 +0900 Message-ID: <55DD19E6.6040501@samsung.com> References: <1439889333-11990-1-git-send-email-m.szyprowski@samsung.com> <55D2FC8D.2020007@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mailout4.w1.samsung.com ([210.118.77.14]:59296 "EHLO mailout4.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751859AbbHZBoL (ORCPT ); Tue, 25 Aug 2015 21:44:11 -0400 Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout4.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0NTO003YM25KVL70@mailout4.w1.samsung.com> for linux-samsung-soc@vger.kernel.org; Wed, 26 Aug 2015 02:44:08 +0100 (BST) In-reply-to: Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Tyler Baker Cc: Marek Szyprowski , linux-samsung-soc , Kukjin Kim , Kevin Hilman On 26.08.2015 06:00, Tyler Baker wrote: > Hi Marek/Krzysztof, > > On 18 August 2015 at 02:36, Krzysztof Kozlowski wrote: >> On 18.08.2015 18:15, Marek Szyprowski wrote: >>> DWC2 (s3c-hsotg) hardware module is available on many Exynos based boards, >>> so enable DWC2 driver as well as the most common USB Ethernet gadget. >>> >>> Signed-off-by: Marek Szyprowski > > The kernelci.org bot recently reported a handful of exynos boot > failures in next-20150825[1] only when using exynos_defconfig. I noticed the issue too but I fought it was a temporary network problem. Apparently it's not temporary. :) > I went > ahead and bisected[2] the failure and found this patch was the > offender. Looking a bit closer, the kernelci.org boot tests typically > pass ip=dhcp or ip= as a kernel argument so that networking is > setup by the kernel. These boot failures are due to the kernel network > initialization timing out. Previously, in next-20150821[3] all the > exynos platforms failing in next-20150825 initialized their network > interfaces successfully, so this seems like a regression. Please have > a closer look at the boot logs[4][5] for comparison. Kevin pointed out > that "asix 3-3.2.4:1.0 eth0: register 'asix' at > usb-12110000.usb-3.2.4, ASIX AX88772 USB 2.0 Ethernet" is missing from > the failed boot logs. Anyways, as a summary it looks like this change > broke networking support on the arndale, arndale-octa, odroid xu3, and > odroid x2. I don't have such problem on my Odroid XU3 which also performs netboot (Arch ARM Linux): netboot=tftpboot 0x40008000 zImage; tftpboot 0x44000000 exynos5422-odroidxu3-lite.dtb; bootz 0x40008000 - 0x44000000 TFTP from server 192.168.1.10; our IP address is 192.168.1.11 [ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=/dev/mmcblk0p1 rootwait rw no_console_suspend smsc95xx.macaddr=00:1e:06:61:7a:93 Do you have anything connected to USB ports of the devices? For example on boot-exynos5250-arndale.html I see: [ 2.792934] using random self ethernet address [ 2.797209] using random host ethernet address [ 2.802244] usb0: HOST MAC 46:52:cf:b5:0f:e8 [ 2.805923] usb0: MAC a2:04:5d:a6:2c:fa [ 2.809720] using random self ethernet address [ 2.814137] using random host ethernet address [ 2.818599] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [ 2.825159] g_ether gadget: g_ether ready It looks like that's the difference. Best regards, Krzysztof > > Cheers, > > Tyler > [1] http://kernelci.org/boot/?next-20150825&exynos_defconfig&fail > [2] http://hastebin.com/otafedoxig.vala > [3] http://kernelci.org/boot/?next-20150821&exynos_defconfig > [4] http://storage.kernelci.org/next/next-20150825/arm-exynos_defconfig/lab-khilman/boot-exynos5250-arndale.html > [5] http://storage.kernelci.org/next/next-20150821/arm-exynos_defconfig/lab-khilman/boot-exynos5250-arndale.html >