Ethernet not working with debian stretch 4.14.67-ti-r73

I built a debian stretch image (with 4.14.67-ti-r73) kernel using the current image-builder – I used the rcn-ee_console_debian_stretch_armhf configuration.

Once I’ve flashed it, when it comes up, I notice the green LED on the ethernet is blinking quickly. Once it comes up, it ends up with a self-assigned IP, but eventually picks up a DHCP address. Seems like it’s dropping a lot of packets … cannot SSH into it and ping shows intermittent results.

Nothing obviously wrong in dmesg, here’s the tail end:


[ 13.534669] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
[ 15.044026] net eth0: initializing cpsw version 1.12 (0)
[ 15.116989] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[ 15.146311] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.152982] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[ 17.153073] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 17.361787] 8021q: 802.1Q VLAN Support v1.8
[ 17.361874] 8021q: adding VLAN 0 to HW filter on device eth0
[ 23.030864] random: crng init done
[ 23.030890] random: 7 urandom warning(s) missed due to ratelimiting
[ 32.941240] systemd[1]: apt-daily.timer: Adding 3h 18min 33.058208s random time.
[ 33.917355] systemd[1]: apt-daily.timer: Adding 5h 56min 18.925035s random time.
[ 37.074459] device-mapper: uevent: version 1.0.3
[ 37.075002] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20) initialised: dm-devel@redhat.com
[ 44.261128] using random self ethernet address
[ 44.261148] using random host ethernet address
[ 44.301103] using random self ethernet address
[ 44.301123] using random host ethernet address
[ 44.420543] usb0: HOST MAC b0:d5:cc:xx:xx:xx
[ 44.424277] usb0: MAC b0:d5:cc:xx:xx:xx
[ 44.431951] usb1: HOST MAC b0:d5:cc:xx:xx:xx
[ 44.432459] usb1: MAC b0:d5:cc:xx:xx:xx
[ 44.790231] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 44.907574] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 46.432911] systemd[1]: apt-daily.timer: Adding 3h 49min 1.211334s random time.
[ 47.095854] net eth0: initializing cpsw version 1.12 (0)
[ 47.185601] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[ 47.201861] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 47.201883] 8021q: adding VLAN 0 to HW filter on device eth0
[ 49.216703] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[ 49.216810] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

root@arm:/home/debian# ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether b0:d5:cc:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 169.254.180.191/16 brd 169.254.255.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::b2d5:ccff:fexx:xxxx/64 scope link
valid_lft forever preferred_lft forever

root@arm:/home/debian# uname -a
Linux arm 4.14.67-ti-r73 #1 SMP PREEMPT Thu Aug 30 00:08:52 UTC 2018 armv7l GNU/Linux

I mostly want to try out btrfs as a filesystem (to avoid corruption) and possibly use the overlayroot, but it seems I need stretch for that. Note that I’ve tried the 4.4 kernel version with the same results, so I guess it’s either something in stretch, or a dtb issue.

Any ideas???

Thanks!

-W

Just to confirm details, please restate the steps you did from the output of the image builder script to sdcard.

Regards,

Sure!

This is based on a pull of github.com/beagleboard/image-builder over the long weekend (which I think hasn’t changed since):

time ./RootStock-NG.sh -c rcn-ee_console_debian_stretch_armhf

cd debian-9.5-console-armhf-2018-09-06

sudo ./setup_sdcard.sh --img-4gb …/BBB-eMMC-debian-9.5-console-armhf-2018-09-06 --dtb beaglebone --enable-systemd --bbb-old-bootloader-in-emmc --rootfs btrfs

Now the flashing part is a bit odd but I don’t think it is part of the problem (since I saw the same issue when installing via a flasher). I’m using a variant of BBBlfs and the SPL/uboot binaries from https://github.com/ravikp7/node-beagle-boot to boot the BBB into USB Mass Storage mode and then mount the eMMC as /dev/sda, Finally, I dd the image to /dev/sda, mount /dev/sda1 and fix /etc/fstab (otherwise it won’t boot!).

Just for sanity I will rebuild the rcn-ee_console_debian_stretch_armhf but with a flasher and retry that.

Thanks!

-W

I rebuilt from scratch and generated an eMMC flasher, installed and I get the same results as with USB mass-storage flashing.

I noticed that the fast-blink of the green LED starts almost at power up, which is odd and makes me think it’s a u-boot or dtb issue? Here’s the compete output from power up to login prompt:

U-Boot SPL 2018.03-00002-gac9cce7c6a (Apr 05 2018 - 13:07:46 -0500)
Trying to boot from MMC2
Loading Environment from EXT4… Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)

U-Boot 2018.03-00002-gac9cce7c6a (Apr 05 2018 - 13:07:46 -0500), Build: jenkins-github_Bootloader-Builder-47

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4… Card did not respond to voltage select!
** Bad device mmc 0 **
Failed (-5)
Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] …
board_rev=[00C0] …
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
2102 bytes read in 32 ms (63.5 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-4.14.67-ti-r73 …
10379776 bytes read in 679 ms (14.6 MiB/s)
loading /boot/dtbs/4.14.67-ti-r73/am335x-boneblack.dtb …
60317 bytes read in 61 ms (964.8 KiB/s)
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable…
loading /boot/initrd.img-4.14.67-ti-r73 …
4530206 bytes read in 315 ms (13.7 MiB/s)
debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=btrfs rootwait coherent_pool=1M net.ifnames=0 quiet] …
debug: [bootz 0x82000000 0x88080000:45201e 0x88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fbad000, end 8ffff01e … OK
Loading Device Tree to 8fb9b000, end 8fbacb9c … OK

Starting kernel …

[ 0.000760] timer_probe: no matching timers found
[ 0.542293] dmi: Firmware registration failed.
[ 1.036826] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 1.253210] dmi-sysfs: dmi entry is absent.
[ 1.285511] omap_voltage_late_init: Voltage driver support not added
[ 1.595720] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: no source widget found for Playback
[ 1.604591] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: Failed to add route Playback → direct → TX

Debian GNU/Linux 9 arm ttyS0

rcn-ee.net console Debian Image 2018-09-06

Support/FAQ: http://elinux.org/BeagleBoardDebian

default username:password is [debian:temppwd]

arm login:

Next up, I’ll retry without btrfs (i.e. omitting the --rootfs btrfs on the sdcard_setup step).

Thanks!

FWIW: Without btrfs, I see the same network problems.

I got a new beagle bone and it looks like it was a h/w problem on the old one (after finding both stretch & jessie images doing the same thing … I was beginning to wonder, so I ordered a new BBB).

Very annoying …! that’s 3 BBBs I have gone through in this USB flashing saga. 2 just stopped powering up and this one acting weird.

Sorry for the alarm.