10269 2016-09-13 20:04:47 +0000 Ethernet is not working 2016-09-13 21:41:44 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-runtime 2.2 MinnowBoard Max x86 RESOLVED NOTABUG http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2_M3.rc1/machines/genericx86/core-image-sato-sdk-genericx86.hddimg Undecided normal 2.2 M3 1 francisco.j.pedraza.gonzalez francisco.j.pedraza.gonzalez california.l.sullivan jose.perez.carranza sonia.delgado yp.kernel.watcher yp.watcher francisco.j.pedraza.gonzalez --- Regression (Found by QA test) No (bug/feature does not impact docs) oldest_to_newest 66101 0 francisco.j.pedraza.gonzalez 2016-09-13 20:04:47 +0000 STATUS: FAILED BUILD: 2.2 M3: 2679a347c576f5411fbe802d2f6201c94036ecb2 ENVIRONMENT: genericx86 - on MMAX32bit STEPS TO REPRODUCE: 1. Open a terminal 2. Type the following command on terminal $ ip addr Expected Result The eth0 interface should be displayed with the corresponding IP. Actual Result No IP is being displayed after this command. Making dmesg | tail gets: r8169 0000:02:00.0 eth0: link down IPV6: ADDRCONF(NETDEV_UP): eth0: link is not ready 66102 1 francisco.j.pedraza.gonzalez 2016-09-13 20:06:05 +0000 You can find the build image here: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2_M3.rc1/machines/genericx86/core-image-sato-sdk-genericx86.hddimg 66106 2 bruce.ashfield 2016-09-13 20:27:21 +0000 I don't have access to this board. This is likely just a change in configuration. Putting cal on this and he can re-assign as need be 66110 3 california.l.sullivan 2016-09-13 21:29:06 +0000 I am unable to reproduce this issue. root@intel-core2-32:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1 link/sit 0.0.0.0 brd 0.0.0.0 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:08:a2:09:bd:af brd ff:ff:ff:ff:ff:ff inet 10.7.201.150/24 brd 10.7.201.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::208:a2ff:fe09:bdaf/64 scope link valid_lft forever preferred_lft forever Please check peripheral/ethernet connections and/or try a different board and let me know the results. 66111 4 francisco.j.pedraza.gonzalez 2016-09-13 21:32:26 +0000 (In reply to comment #3) > I am unable to reproduce this issue. > > root@intel-core2-32:~# ip addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1 > link/sit 0.0.0.0 brd 0.0.0.0 > 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen > 1000 > link/ether 00:08:a2:09:bd:af brd ff:ff:ff:ff:ff:ff > inet 10.7.201.150/24 brd 10.7.201.255 scope global eth0 > valid_lft forever preferred_lft forever > inet6 fe80::208:a2ff:fe09:bdaf/64 scope link > valid_lft forever preferred_lft forever > > > Please check peripheral/ethernet connections and/or try a different board > and let me know the results. I just tried with a different board, and everything went good. Seems like I have a faulty board.