Pi 5: continuous Ethernet link flapping since EEE enabled by default in rpi-6.18.y (#7270), mostly with AVM Fritz!Box link partners

Abierto
  • ¿Algo no está bien?
#7,511 2 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, linux
Área
networking, operating-systems

Línea de trabajo

Start by comparing the rpi-6.18.y EEE changes from #7270 with the rpi-6.12.y state and the eee-broken-1000t/eee-broken-100tx workaround from #6900. Reproduce with an affected link partner using dmesg and dtparam=eee=off; done means the Pi 5 link remains stable with EEE enabled across the reported partner setups.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Note: The report below was largely generated with AI assistance. I have read through it to verify that the claims are accurate and reflect what our users report in the Home Assistant OS issue tracker.

Describe the bug

Since Home Assistant OS moved from a rpi-6.12.y based kernel to rpi-6.18.y, we have received multiple reports of Raspberry Pi 5 devices whose onboard Ethernet link flaps continuously:

macb 1f00100000.ethernet end0: Link is Down
macb 1f00100000.ethernet end0: Link is Up - 1Gbps/Full - flow control off

This repeats every few seconds (in some cases starting within seconds after boot), with packet loss towards the default gateway and effectively unusable networking. Rolling back to the 6.12-based OS release restores a stable link on identical hardware, cabling and switch port.

Setting dtparam=eee=off resolves the problem on 6.18. This has been confirmed by three affected users, one of them with a full on/off/on cycle: flapping with EEE enabled, stable for two days with it disabled, flapping returned after re-enabling.

Disabling EEE on the link partner side also resolves the flapping: confirmed on Fritz!Box 7490 and 7590 (LAN port energy setting changed from "automatic" to "none") and on managed switches that offer an EEE toggle. Partners without such an option keep flapping unless EEE is disabled on the Pi.

Our 6.12-based releases used rpi-6.12.y at 89050b1059997d38d55462b323b099a6436dc10d, which still contained the eee-broken-1000t/eee-broken-100tx properties from #6900 — EEE was never negotiated there. rpi-6.18.y enables EEE by default on the RP1 GEM since #7270 (macb EEE/TX LPI support, BCM54213PE switched from AutogrEEEn to native EEE mode, eee_enabled_default = true with a 250 ms TX LPI timer; earlier testing round in #7251). This matches the observed behavior change exactly.

Affected setups (from our issue tracker)

Four users have reported the link flapping so far, one more with the same hardware combination is holding back the update in anticipation. Where the direct link partner is known:

  • AVM Fritz!Box 7590 — three users (at least two directly connected, no switch in between)
  • One of the four reproduced the flapping against a whole range of devices: TP-Link TL-SG608E, TP-Link TL-SG1016DE, TP-Link ER605, Netgear GS105NA, Fritz!Box 7490 and Fritz!Box 7590. This user verified the link behavior (LAN LED fully down and back up in ~5 s intervals, matching the dmesg pattern above) and confirmed that disabling EEE on either side — the Pi or a partner that offers an EEE setting — stops the flapping, while unmanaged partners without an EEE option keep flapping until EEE is disabled on the Pi.

AVM Fritz!Box devices are clearly overrepresented as link partner, but the last report suggests the problem is not limited to a single vendor's LPI handling: on that Pi, every EEE-capable partner tested triggered the flapping.

For scale: we have roughly 100 000 Raspberry Pi 5 installations on 6.18-based OS releases, so the overall incidence is low — most link partners appear to handle the newly negotiated EEE fine.

Environment
  • Raspberry Pi 5 Model B (one confirmed Rev 1.1, revision d04171)
  • Kernels: rpi-6.18.y 6.18.33 (stable_20260527) and 6.18.34 (stable_20260609)
  • Not reproducible on rpi-6.12.y (6.12.75, which contains the #6900 DT workaround)
Steps to reproduce
  1. Raspberry Pi 5 with an affected link partner (e.g. Fritz!Box 7590), rpi-6.18.y kernel with default EEE configuration
  2. Boot and run dmesg | grep "Link is" — the link flaps every few seconds
  3. Add dtparam=eee=off to config.txt and reboot — the link is stable
Additional context
  • Symptom-wise this resembles the Raspberry Pi 4 / bcmgenet situation after EEE was enabled there (#7365): a broad, vendor-diverse set of link partners affected, resolved by Pi-side fixes (#7372, #7373, #7388) rather than by blaming partner equipment. We have not ruled out either direction for the Pi 5 yet — partner devices mishandling LPI vs. marginal TX LPI signaling from the RP1 GEM.
  • Downstream reports: home-assistant/operating-system#4861, home-assistant/operating-system#4881
Device(s)

Raspberry Pi 5

System

Home Assistant OS 18.0/18.1 (rpi-6.18.y 6.18.33 / 6.18.34, stable_20260527 / stable_20260609)

Lenguaje dominante
C
Estrellas
13.3k
Forks
5.5k
Merge medio
3 d 20 h
PR fusionados (30 d)
27

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de raspberrypi/linux

Todos los issues de raspberrypi/linux

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.