Hi Marek/Krzysztof, On 18 August 2015 at 02:36, Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx> 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 <m.szyprowski@xxxxxxxxxxx> The kernelci.org bot recently reported a handful of exynos boot failures in next-20150825[1] only when using exynos_defconfig. 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=<ipaddr> 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. 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 -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |