Pi Zero W: intermittent loss of approximately 4295 seconds with 6.12 ARMv6 kernels

Aperta
#7,764 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, linux

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C
Stelle
13.3k
Fork
5.5k
Merge medio
4g 10h
PR unite (30g)
31

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di raspberrypi/linux

Tutte le issue di raspberrypi/linux

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.