Hi, I'm pulling my hair about a really weird issue I see on my venerable Odroid C2. This system has been running stably under Leap 15 for me for years. In May, I installed Leap 16.0 on it after creating a boot image for this model [1], and it has been working nicely for me since then. It's doing quite a bit of networking, as it's used as a proxy server in my home network.
Last week I updated the system, and I could hardly boot because the network hardware was experiencing repeated TX queue hangs: [ 18.848070] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=44) [ 18.856099] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found [ 18.858172] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW [ 18.859403] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode [ 22.224053] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 27.873018] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out 5624 ms [ 27.874876] proxy kernel: meson8b-dwmac c9410000.ethernet eth0: Reset adapter. As the update looked pretty harmless in general, I suspected the dtb- amlogic package. And indeed, if I reinstall the system (it has no btrfs and thus no snapshots) and update everything except dtb-amlogic, this issue doesn't occur, and the system boots just fine. However, there are two things that make me doubt this "solution" is correct: 1) I could not fix the issue by downgrading dtb-amlogic after I had once updated it. 2) There seem to be zero differences between dtb-amlogic 6.12.0- 160000.29.1 (the version I originally installed) and the latest 6.12.0- 16000.37.1. That makes totally no sense to me (note that the phenomenon is independent of the kernel). Since then I've repeated the update procedure in a couple of variations, and I keep observing the same thing; Updating dtb-amlogic to 6.12.0-16000.37.1 breaks the network hardware, and downgrading again later doesn't seem to fix it. Reinstalling with a pristine image does, though. Any ideas? Would this deserve a bug report, as the Odroid C2 platform is obviously not an officially supported product? Thanks, Martin [1] https://build.opensuse.org/package/show/home:mwilck:OdroidC2:Leap:16.0/JeOS-odroidc2 -- Dr. Martin Wilck <[email protected]> SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg, Germany Geschäftsführer: Jochen Jaser, Andrew McDonald (HRB 36809,AG Nürnberg)
