Khadas Edge 2 network interface problem

burak.cakmak · April 23, 2024, 12:15pm

Which system do you use? Android, Ubuntu, OOWOW or others?

OOWOW

Which version of system do you use? Khadas official images, self built images, or others?

Ubuntu 1.6.2 Gnome

Please describe your issue below:

After reboot device lost network connectivity. This device is connected to network via a USB-C → Ethernet adapter.

Post a console log of your issue below:

Apr 17 07:03:27 localhost systemd[1]: var-lib-docker-overlay2-6ead7ea3a4827f1fc67572f6108b909da2d606c0d56482cf4451c751190543e6\x2dinit-merged.mount: Deactivated successfully.
Apr 17 07:04:05 localhost kernel: [  198.130119] ------------[ cut here ]------------
Apr 17 07:04:05 localhost kernel: [  198.130131] NETDEV WATCHDOG: enx00e04c6808f9 (r8152): transmit queue 0 timed out
Apr 17 07:04:05 localhost kernel: [  198.130177] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x1a0/0x1c8
Apr 17 07:04:05 localhost kernel: [  198.130180] Modules linked in: algif_hash algif_skcipher af_alg bnep hci_uart bluetooth ecdh_generic ecc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc overlay zram binfmt_misc joydev sch_fq_codel bcmdhd fuse ip_tables ipv6 btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq cdc_ether usbnet r8152
Apr 17 07:04:05 localhost kernel: [  198.130300] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.198 #1.6.5
Apr 17 07:04:05 localhost kernel: [  198.130303] Hardware name: Khadas Edge2 (DT)
Apr 17 07:04:05 localhost kernel: [  198.130308] pstate: 60400009 (nZCv daif +PAN -UAO -TCO BTYPE=--)
Apr 17 07:04:05 localhost kernel: [  198.130312] pc : dev_watchdog+0x1a0/0x1c8
Apr 17 07:04:05 localhost kernel: [  198.130317] lr : dev_watchdog+0x1a0/0x1c8
Apr 17 07:04:05 localhost kernel: [  198.130320] sp : ffffffc00a0dbd60
Apr 17 07:04:05 localhost kernel: [  198.130323] x29: ffffffc00a0dbd60 x28: 0000000000000101 
Apr 17 07:04:05 localhost kernel: [  198.130330] x27: ffffffc008b9a028 x26: ffffffc00a0dbe58 
Apr 17 07:04:05 localhost kernel: [  198.130337] x25: ffffffc009ebbb00 x24: 0000000000000001 
Apr 17 07:04:05 localhost kernel: [  198.130344] x23: ffffffc009ecb300 x22: ffffffc008b9a028 
Apr 17 07:04:05 localhost kernel: [  198.130351] x21: ffffff810e773480 x20: 0000000000000000 
Apr 17 07:04:05 localhost kernel: [  198.130357] x19: ffffff810e773000 x18: 0000000000000000 
Apr 17 07:04:05 localhost kernel: [  198.130364] x17: 0000000000000000 x16: 0000000000000000 
Apr 17 07:04:05 localhost kernel: [  198.130371] x15: 000000000000000a x14: 64656d6974203020 
Apr 17 07:04:05 localhost kernel: [  198.130378] x13: 6575657571207469 x12: 6d736e617274203a 
Apr 17 07:04:05 localhost kernel: [  198.130384] x11: 2932353138722820 x10: 3966383038366334 
Apr 17 07:04:05 localhost kernel: [  198.130391] x9 : ffffffc0080cc2f0 x8 : 3a474f4448435441 
Apr 17 07:04:05 localhost kernel: [  198.130398] x7 : 572056454454454e x6 : ffffffc009f31845 
Apr 17 07:04:05 localhost kernel: [  198.130405] x5 : 00000000002bffa8 x4 : ffffff83fd54f868 
Apr 17 07:04:05 localhost kernel: [  198.130412] x3 : 0000000000000000 x2 : 0000000000000000 
Apr 17 07:04:05 localhost kernel: [  198.130418] x1 : 0000000000000000 x0 : ffffffc00995f780 
Apr 17 07:04:05 localhost kernel: [  198.130425] Call trace:
Apr 17 07:04:05 localhost kernel: [  198.130430]  dev_watchdog+0x1a0/0x1c8
Apr 17 07:04:05 localhost kernel: [  198.130437]  call_timer_fn+0xa4/0x158
Apr 17 07:04:05 localhost kernel: [  198.130441]  __run_timers+0x1c0/0x1e8
Apr 17 07:04:05 localhost kernel: [  198.130445]  run_timer_softirq+0x34/0x58
Apr 17 07:04:05 localhost kernel: [  198.130450]  __do_softirq+0x29c/0x35c
Apr 17 07:04:05 localhost kernel: [  198.130456]  __irq_exit_rcu+0x54/0x94
Apr 17 07:04:05 localhost kernel: [  198.130460]  irq_exit+0x14/0x20
Apr 17 07:04:05 localhost kernel: [  198.130466]  __handle_domain_irq+0xbc/0xc0
Apr 17 07:04:05 localhost kernel: [  198.130470]  gic_handle_irq+0x2c8/0x318
Apr 17 07:04:05 localhost kernel: [  198.130474]  el1_irq+0xc8/0x180
Apr 17 07:04:05 localhost kernel: [  198.130479]  arch_local_irq_enable+0x8/0x20
Apr 17 07:04:05 localhost kernel: [  198.130483]  cpuidle_enter+0x3c/0x50
Apr 17 07:04:05 localhost kernel: [  198.130489]  do_idle+0x23c/0x25c
Apr 17 07:04:05 localhost kernel: [  198.130493]  cpu_startup_entry+0x28/0x40
Apr 17 07:04:05 localhost kernel: [  198.130498]  rest_init+0xd4/0xe0
Apr 17 07:04:05 localhost kernel: [  198.130504]  arch_call_rest_init+0x14/0x1c
Apr 17 07:04:05 localhost kernel: [  198.130508]  start_kernel+0x510/0x544
Apr 17 07:04:05 localhost kernel: [  198.130512] 
Apr 17 07:04:05 localhost kernel: [  198.130512] PC: 0xffffffc008b9a1c8:

---- There is a huge memory dump here

Apr 17 07:04:05 localhost kernel: [  198.140426] ---[ end trace 953587928f383c7e ]---
Apr 17 07:04:05 localhost kernel: [  198.140484] r8152 8-1:1.0 enx00e04c6808f9: Tx timeout
Apr 17 07:04:05 localhost kernel: [  198.143030] r8152 8-1:1.0 enx00e04c6808f9: Tx status -2
Apr 17 07:04:05 localhost kernel: [  198.143109] r8152 8-1:1.0 enx00e04c6808f9: Tx status -2
Apr 17 07:04:05 localhost kernel: [  198.143188] r8152 8-1:1.0 enx00e04c6808f9: Tx status -2
Apr 17 07:04:05 localhost kernel: [  198.143237] r8152 8-1:1.0 enx00e04c6808f9: Tx status -2
Apr 17 07:04:07 localhost kernel: [  200.008385] usb 8-1: reset SuperSpeed Gen 1 USB device number 3 using xhci-hcd
Apr 17 07:04:20 localhost kernel: [  213.276912] xhci-hcd xhci-hcd.9.auto: xHCI host not responding to stop endpoint command.
Apr 17 07:04:20 localhost kernel: [  213.276923] xhci-hcd xhci-hcd.9.auto: USBSTS: 0x00000000
Apr 17 07:04:20 localhost kernel: [  213.290370] xhci-hcd xhci-hcd.9.auto: xHCI host controller not responding, assume dead
Apr 17 07:04:20 localhost kernel: [  213.290426] xhci-hcd xhci-hcd.9.auto: HC died; cleaning up
Apr 17 07:04:20 localhost kernel: [  213.290551] r8152 8-1:1.0 enx00e04c6808f9: Stop submitting intr, status -108
Apr 17 07:04:20 localhost kernel: [  213.290599] r8152 8-1:1.0 enx00e04c6808f9: get_registers -110
Apr 17 07:04:20 localhost kernel: [  213.290701] r8152 8-1:1.0 enx00e04c6808f9: Tx status -108
Apr 17 07:04:20 localhost kernel: [  213.290729] r8152 8-1:1.0 enx00e04c6808f9: Tx status -108
Apr 17 07:04:20 localhost kernel: [  213.290759] usb 8-1: USB disconnect, device number 3
Apr 17 07:04:20 localhost avahi-daemon[641]: Interface enx00e04c6808f9.IPv6 no longer relevant for mDNS.
Apr 17 07:04:20 localhost avahi-daemon[641]: Leaving mDNS multicast group on interface enx00e04c6808f9.IPv6 with address fe80::5822:9e26:3396:c357.
Apr 17 07:04:20 localhost avahi-daemon[641]: Interface enx00e04c6808f9.IPv4 no longer relevant for mDNS.
Apr 17 07:04:20 localhost avahi-daemon[641]: Leaving mDNS multicast group on interface enx00e04c6808f9.IPv4 with address 192.168.88.18.
Apr 17 07:04:20 localhost avahi-daemon[641]: Withdrawing address record for fe80::5822:9e26:3396:c357 on enx00e04c6808f9.
Apr 17 07:04:20 localhost avahi-daemon[641]: Withdrawing address record for 192.168.88.18 on enx00e04c6808f9.
Apr 17 07:04:20 localhost NetworkManager[651]: <info>  [1713337460.4145] device (enx00e04c6808f9): state change: activated -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Apr 17 07:04:20 localhost NetworkManager[651]: <info>  [1713337460.4342] dhcp4 (enx00e04c6808f9): canceled DHCP transaction
Apr 17 07:04:20 localhost NetworkManager[651]: <info>  [1713337460.4343] dhcp4 (enx00e04c6808f9): activation: beginning transaction (timeout in 45 seconds)
Apr 17 07:04:20 localhost NetworkManager[651]: <info>  [1713337460.4343] dhcp4 (enx00e04c6808f9): state changed no lease
Apr 17 07:04:20 localhost NetworkManager[651]: <info>  [1713337460.4349] manager: NetworkManager state is now DISCONNECTED
Apr 17 07:04:20 localhost dbus-daemon[648]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=651 comm="/usr/sbin/NetworkManager --no-daemon ")
Apr 17 07:04:20 localhost /usr/libexec/gdm-x-session[2360]: dbus-daemon[2360]: [session uid=117 pid=2360] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=117 pid=2472 comm="/usr/libexec/gsd-sharing ")
Apr 17 07:04:20 localhost /usr/libexec/gdm-x-session[2360]: dbus-daemon[2360]: [session uid=117 pid=2360] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Apr 17 07:04:20 localhost gsd-sharing[2472]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Apr 17 07:04:20 localhost gsd-sharing[2472]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Apr 17 07:04:20 localhost systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 17 07:04:20 localhost /usr/libexec/gdm-x-session[2360]: dbus-daemon[2360]: [session uid=117 pid=2360] Activating service name='org.freedesktop.secrets' requested by ':1.5' (uid=117 pid=2397 comm="/usr/bin/gnome-shell ")
Apr 17 07:04:20 localhost dbus-daemon[648]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 17 07:04:20 localhost systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 17 07:04:20 localhost chronyd[949]: Source 185.125.190.57 offline

numbqq · April 24, 2024, 1:09am

Hello @burak.cakmak

Could you tell us the steps you reproduce this issue?

burak.cakmak · April 24, 2024, 12:47pm

Hello @numbqq

This device was power cycled. Everything normally works when it’s rebooted. But sometimes device cannot activate the network interface as shared above.

Thanks,
Burak

burak.cakmak · April 29, 2024, 4:33pm

Hello @numbqq,

Do you have any findings on this problem?

rubywen · April 30, 2024, 2:07am

Hi Ivan, the client means that the network connection is lost, thus they lost the connection with remote devices. Could you please check whether it’s Khadas related?

ivan.li · April 30, 2024, 2:48am

1.Try changing to another HUB.
2.I need you to provide more details on reproducing this problem. I will continue to follow up after the Labor Day holiday.

rubywen · April 30, 2024, 3:15am

Hi Burak
Could you send some more details for the connections or application scenarios? such as photos, videos.
We’re using a type-c to ethernet hub adapter with Edge2, it works well, the network connected.

burak.cakmak · April 30, 2024, 12:27pm

Hi Ruby,

We’re using a standard type-c to ethernet adaptor. Please see the pictures in the link below. This devices is in a shopping mall and it’s powered off every night and turned on every morning. After it comes back, a few minutes later this crash happens. Your engineers can have more idea about the core dump in the logs.

Deployment Photos

ivan.li · May 6, 2024, 10:03am

Hi @burak.cakmak

What operations did you do after booting up?

If you do not perform any operations after turning on the Edge2 and just perform a restart test, will the network be disconnected?