Your message dated Sun, 01 Mar 2026 10:02:36 +0000
with message-id <[email protected]>
and subject line Bug#1127659: fixed in chrony 4.6.1-3+deb13u1
has caused the Debian Bug report #1127659,
regarding linux-image-6.12.73+deb13-amd64: Recent security kernels break
chrony's use of PHC clock (6.1.162, 6.12.73)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-6.12.73+deb13-amd64
Version: linux-image-6.12.73+deb13-amd64
Severity: normal
Observed on amd64 machines with both Bookworm (6.1.162) and Trixie (6.12.73)
current security linux-image releases. Different CPU familys (Jaguar and
Ryzen). Different chrony versions (4.3-2+deb12u1, 4.6.1-3).
To observe problem, with security kernels installed, setup a PHC clock
source for the existing I210 interface, eg.
refclock PHC /dev/ptp0:extpps
Observe error when starting chrony:
chronyd[837]: Fatal error : Could not enable external PHC timestamping
(wording may be different between the two systems, this was Trixie)
Both work fine under previous kernels 6.1.159 and 6.12.73 (I do not
guarantee there weren't any other versions released between these and the
recent security, neither machine is exposed to the internet and so don't
always get updated immediately.)
In both cases chrony's use of the PHC for timestamping appears unimpaired by
the kernels that fail the PHC refclock. The bookworm platform has linuxptp
installed. phc_ctl and ts2phc work fine with either kernel.
I left the severity at normal, but it's much more serious to a machine
that's syncing to a PPS source like this.
Workaround: roll back those security kernels, of course. And test any future
releases for this issue, of course.
-- System Information:
irrelevant, as I'm reporting from a third machine that has reportbug and
email setup.
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 4.6.1-3+deb13u1
Done: Vincent Blut <[email protected]>
We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Blut <[email protected]> (supplier of updated chrony package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 16 Feb 2026 17:34:12 +0100
Source: chrony
Architecture: source
Version: 4.6.1-3+deb13u1
Distribution: trixie
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 1127659
Changes:
chrony (4.6.1-3+deb13u1) trixie; urgency=medium
.
* debian/patches/:
- Add refclock_phc_open-device-for-writing-with-extpps-option.patch.
Thanks to Jan Lübbe for the report. (Closes: #1127659)
.
* debian/test/upstream-simulation-test-suite:
- Prevent simulation test failures.
Checksums-Sha1:
be597efa555a2317cdd933a0440961c24d274f53 2898 chrony_4.6.1-3+deb13u1.dsc
2deb2b1796d93afced5351dbb41367693b536e91 44308
chrony_4.6.1-3+deb13u1.debian.tar.xz
c812a7667c81425c5e5232d541da7989f8e4c605 1379720
chrony_4.6.1-3+deb13u1.git.tar.xz
39c6743bc36f5c93c180c1dfa9b166b3a54ce3c4 17322
chrony_4.6.1-3+deb13u1_source.buildinfo
Checksums-Sha256:
11590bfa06f7e9b769b8241208839ecee5ec112305d151ed59c11c26448d2234 2898
chrony_4.6.1-3+deb13u1.dsc
fbb0a0ed6e6e532043c18dbffcaaca4440e9ed790c526c205865bb56510fa877 44308
chrony_4.6.1-3+deb13u1.debian.tar.xz
a3f5421cb92f403bafee0597191e99179c9cbe97ab2d79d8c93185e7d3197be0 1379720
chrony_4.6.1-3+deb13u1.git.tar.xz
ebce00489fdbac811c3c63db54cac51f983960ec2fab6d30f4abe74b5a163e03 17322
chrony_4.6.1-3+deb13u1_source.buildinfo
Files:
517cc5db06cc2d2830fc3baa3462de30 2898 net optional chrony_4.6.1-3+deb13u1.dsc
e167dd9ec98b7eb55b1108e715181ea4 44308 net optional
chrony_4.6.1-3+deb13u1.debian.tar.xz
f4354341b5f630b762b5e8451ef8b08b 1379720 net optional
chrony_4.6.1-3+deb13u1.git.tar.xz
c946b0e56fc4fcb2ffa99ece3f776171 17322 net optional
chrony_4.6.1-3+deb13u1_source.buildinfo
Git-Tag-Info: tag=1e799f7fd9ac363ca004fb67bc4ca4e9b9bb0ff6
fp=1b939355ac4c35cadfbd739c06a328e00c6ace15
Git-Tag-Tagger: Paul Gevers <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmjJxUACgkQYG0ITkaD
wHkRVRAAmIR/KZqKfKZFIMo93aY0UwATo6qkwXDAqAoPOc8rqG5sMHy3ytU1NA1f
2yHwLmz4qetfZP5fj/pb3DUjhC5zjLw/CcZZaxsHMm6Wam2jLicH9c+ngY3f4j0c
sJnapvflscn7mi9dhagh0SJe2wflke2RAPOxpNvhBbynelbzRowXDWEMntWy95JJ
RcamXoPODIy0602a3HFTAwK2Ej8aDnod53vPJfGfe4SzfgTrxE+saRRKHkwsHkMh
2Qa/pcNKbt3Q8lnuFgIM8n7TtIcy8Gwa9qpFcpt9yALpF2WWE1nE384sw1vE7aD9
duLPkXEN5zFwMlOTUNKWhMVTCdOcBwbCeJ0S0Eg1obYSz34QkpyWjXMAl0FJu3iX
2f5YVdmGrbUzuJidWIrutpaKt2pbejVjWso4FkWKkaRckhgfbp6QbAgv0LbyEwQ5
qiUV1eGgPjby0DMewNIN2bcLZmr31qSF7zsulKa2U/c0D41HXhXNQlEVTHThNn3L
WyjFheLmDk2mRKua00M/mjXjGIZMCp4TBAqzABAwcGUFFdwGgZXeloQpCKgzft45
+icj9K6dqy37qMOIFFtiwhPzkHiaDZfypZlVg/noesOMdG4UmNuNyxWNyppJR9fc
Uh5T19RUFxlljdZ/n1M4ceEwmKed3y26saABp8ml3FCzKVyEb04=
=jb5k
-----END PGP SIGNATURE-----
pgpwPtIGyrye5.pgp
Description: PGP signature
--- End Message ---
