Pi Zero W: intermittent loss of approximately 4295 seconds with 6.12 ARMv6 kernels
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- c, linux
- Área
- operating-systems
Línea de trabajo
Start by examining the BCM2835 clocksource and clockevent handling for the 32-bit 1 MHz timer described in the issue. The report does not identify a failing kernel file or provide a deterministic reproduction, so first gather low-overhead diagnostics that distinguish clock accounting errors, clock-set operations, and prolonged stalls. Done means establishing evidence for the source of the roughly 4295-second clock deficit.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
Two Raspberry Pi Zero W Rev 1.1 boards running 32-bit Raspbian Bookworm have intermittently fallen behind by about 71 min 35 s during operation. The application detects a large NTP offset and corrects the clock forward. The trigger is unknown.
| Board | Running kernel | Observation |
|---|---|---|
| A | 6.12.96+rpt-rpi-v6 | 2026-09-27: NTPsec recorded +4294.936 s and exited; the journal confirms a subsequent clock correction. |
| A | 6.12.109+rpt-rpi-v6 | 2026-10-13: +4294.035920 s measured and corrected. |
| B | 6.12.96+rpt-rpi-v6 | 2026-10-19: application logged a 4294 s correction; no journal confirmation of the step. |
| A | 6.12.109+rpt-rpi-v6 | 2026-11-17: +4294.844522 s measured; residual after correction −0.011612 s. |
On an earlier incident on board A, two public NTP references and the LAN reference independently agreed that the local clock was behind by about 4296 s.
Steps to reproduce the behaviour
No deterministic reproduction. The boards run headless, with Wi-Fi and Bluetooth active, and an application periodically comparing the local clock against NTP. Expected: the clock advances correctly during unattended operation. Observed: a sporadic large deficit, subsequently corrected forward. No stock-image or kernel-only A/B test has been performed.
Device (s)
Raspberry Pi Zero W / WH
System
Raspberry Pi Zero W Rev 1.1; Raspbian GNU/Linux 12 (Bookworm), armv6l.
Board A on 2026-11-17: 6.12.109+rpt-rpi-v6, package 1:6.12.109-1+rpt1 (build 2026-09-11); boot firmware 2026-09-14 (a86983925695); get_throttled=0x0. The refreshed Bookworm ARMv6 candidate 1:6.12.115-1+rpt1 has not yet been tested in this setup.
All four comparison boards reported active clocksource timer, mask 0xffffffff, and a 32-bit 1 MHz timer in the boot journal. All loaded the same BCM43430 WLAN firmware (7.45.98, FWID 01-8e14b897) and used NTPsec 1.2.2.
Logs
2026-11-17, monotonic journal timeline (seconds since boot):
- 313440.978: locally generated Wi-Fi disconnection; connection to a different AP 0.567 s later. DHCP renewed the same IPv4 address about 1.0 s after the disconnection.
- 313613.414: NTPsec stopped normally for the application-initiated correction, about 172 s after disconnection. No panic exit in this window.
- 313619.298: Tailscale detected the forward clock step during correction; this is not evidence of suspend.
- 313620.930: NTPsec started again.
- 313621.682: correction verified at 08:04:45 CET, applied correction +4294.844522 s, residual −0.011612 s.
About 45 minutes after correction two public NTP sources reported offsets below 2 ms. The latest large offset itself was measured against the LAN reference. The October journal also showed a nearby Wi-Fi reassociation but does not establish a causal link. No matching kernel error was found in the available journal.
Additional context
Two comparable Zero W Rev 1.1 boards still running 6.1.21+ with older boot firmware have no known matching incidents. Kernel, boot firmware and some user-space packages changed together, so this is an association, not an isolated kernel regression.
A full 32-bit timer period at 1 MHz is 4294.967296 s. The latest correction was about 0.123 s smaller. Could this signature indicate lost time in BCM2835 clocksource or clockevent handling? What low-overhead diagnostics would help distinguish a clock accounting error, an unexpected clock-set operation, and a prolonged stall?
A historical FreeBSD report gives a similar offset but does not establish a Linux cause: https://lists.freebsd.org/pipermail/freebsd-arm/2012-December/004443.html
- Lenguaje dominante
- C
- Estrellas
- 13.3k
- Forks
- 5.5k
- Merge medio
- 4 d 10 h
- PR fusionados (30 d)
- 31
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de raspberrypi/linux
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
raspberrypi/linux#7415 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace appAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
raspberrypi/linux#7399 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Documentation update requiredAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
raspberrypi/linux#7357 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
raspberrypi/linux#7054 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
raspberrypi/linux#7770 ·
Los mantenedores suelen responder en 1 día
Todos los issues de raspberrypi/linux
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
LedgerHQ/app-bitcoin-legacy#306 ·
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
prusa3d/Prusa-Firmware-Buddy#5629 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 3 días
-
Issue PRL on WindowsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día