Your message dated Sat, 28 Mar 2026 15:03:34 +0000
with message-id <[email protected]>
and subject line Bug#1127659: fixed in chrony 4.3-2+deb12u2
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.3-2+deb12u2
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: Tue, 17 Feb 2026 16:40:15 +0100
Source: chrony
Architecture: source
Version: 4.3-2+deb12u2
Distribution: bookworm
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 1127659
Changes:
 chrony (4.3-2+deb12u2) bookworm; 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/tests/upstream-simulation-test-suite:
     - Prevent simulation test failures.
Checksums-Sha1:
 1ddfd0ce2c74cec27584e9a4eca88faf78866e30 2873 chrony_4.3-2+deb12u2.dsc
 5d3daa931c6684293806d82f1c7da1c0c6330842 41812 
chrony_4.3-2+deb12u2.debian.tar.xz
 3aa40773ed250178a3d46da5d9fc2cb7089fb4d8 1218304 
chrony_4.3-2+deb12u2.git.tar.xz
 45b090f92519745c14a1ccbb89bcd06bc1830cc9 17314 
chrony_4.3-2+deb12u2_source.buildinfo
Checksums-Sha256:
 9dfac6899d08a306b157ffd016990afd2553b2024c82ef72c2a04e0df677991f 2873 
chrony_4.3-2+deb12u2.dsc
 496943dec4a7592027056170262e9815d3ac33c9cc60c13cf17da3c2b6c634fc 41812 
chrony_4.3-2+deb12u2.debian.tar.xz
 bb23ef5070708fcb234ac9242ac25be97e05d5d3fe1ad16c7b46eceef3d9eb6a 1218304 
chrony_4.3-2+deb12u2.git.tar.xz
 370b43bfecdafe8081768a07112a81221579353526358653d70698b921fb03c5 17314 
chrony_4.3-2+deb12u2_source.buildinfo
Files:
 f649e2dc377e6ce081d3fb854c802957 2873 net optional chrony_4.3-2+deb12u2.dsc
 a2fd4dd3a5ed857a4d0026c8005b6300 41812 net optional 
chrony_4.3-2+deb12u2.debian.tar.xz
 2047243b136b32abecf931dcfaa0b0ed 1218304 net optional 
chrony_4.3-2+deb12u2.git.tar.xz
 d22ed09f6cdd51de93b46886f0edb6d4 17314 net optional 
chrony_4.3-2+deb12u2_source.buildinfo
Git-Tag-Info: tag=1de16794e6e91829eaa07098c7bfe08d614a00bb 
fp=1b939355ac4c35cadfbd739c06a328e00c6ace15
Git-Tag-Tagger: Paul Gevers <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmjKRsACgkQYG0ITkaD
wHnKow//Q35HkSvRltnBeEeqUM3bXTHx21L2v8DfulhSwZTZhxE3sfoaqsThXOcp
NQlMgNuYoJm+9z7ooIfKQIB/U7Wgmzf0XHSTNLxVi68qtXhMlMJsOb8YqnkOgmsk
ZJou/xcBakXe5WinStcIIzHipPy4CKT2A3PK/DD0PiZiFficcsYMJdMLs0fWn0Ck
/vRUHvzegBqiERMN+lqMLGinbMKjJLn72D3xKsK4VDaCyyV+2CxmFQTqNYA1txO/
SV+ydkP1sFhRqe8Ri0rlLhlpNQ7fwdFnoeEGELPv8+iIP82mhRq4rQJew58C6J2b
GJGvfT4LPPV/TGA0oQrZSfHnVOFeITKt37JnvgoCexQUHQs+QCFRw76AG7VpYX/V
xRqof7QV1/TYeE0Dw0J5Ys5yRWyahgWi+ZpnHunv+NIScZ23JwbCWsrMDYh1cIeX
iFSMsGYFbH8sT0zVmmsK44ZdJ8mbcOTg1iN7OXRimSgwwofJHbC7hcF7K6c8lg4i
/yXdAzF1XYPwTltoHd7utdbiOIhZ9+c32oqkgi+aVeOAjggZy5QSWxNPt3Kq8QyB
RjtKznybTbHFPBqlcwvwsr07rOkekvfyar7fPP6qguwFg3IgUsSeyngqVV1TCuXh
qHY2IGGndzs0oVmTo9eSDKx6sZ3SkYMNjZgtaFHcnuCHUfdNcfU=
=RzMg
-----END PGP SIGNATURE-----

Attachment: pgp7Ke28KoNBk.pgp
Description: PGP signature


--- End Message ---

Reply via email to