Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.bugs.dist    |    Ohh some weird Debian bug report thing    |    28,835 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 27,367 of 28,835    |
|    Vincent Blut to Jan Luebbe    |
|    Re: Bug#1127659: linux-image-6.12.69+deb    |
|    12 Feb 26 16:31:35    |
      XPost: linux.debian.kernel       From: vincent.debian@free.fr       To: 1127659@bugs.debian.org       Copy: debian-kernel@lists.debian.org       Copy: chrony@packages.debian.org              Hi Salvatore,              Le 2026-02-12 16:14, Salvatore Bonaccorso a écrit :       > Control: affects -1 - chrony       > Control: reassign -1 src:chrony 4.6.1-3       > Control: found -1 4.3-2+deb12u1       > Control: found -1 4.3-2       > Control: fixed -1 4.8-1       > Control: tags -1 + upstream fixed-upstream bookworm trixie       >        > Hi Jan,       >        > On Wed, Feb 11, 2026 at 11:40:12AM +0100, Jan Luebbe wrote:       > > Package: src:linux       > > Version: 6.12.69-1       > > Severity: important       > > Tags: upstream       > > X-Debbugs-Cc: jlu@pengutronix.de       > >        > > Dear Maintainer,       > >        > > I've just debugged a new issue with 6.12.69+deb13 vs. 6.12.63+deb13.       > > chrony 4.6.1 (the version in Debian stable) started failing to start       > > with "Fatal error : Could not enable external PHC timestamping".       > >        > > We use the extpps mode with PTP hardware clocks. It seems that       > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux       git/commit/?id=97529630d85f910f4e6dfc615f1d111ada9448e3       > > changes /dev/ptp* to now require FDs open for writing to configure       > > extpps. Chrony has a fix       > > (https://gitlab.com/chrony/chrony/-/commit/f78e4681eff71d941       ab3be5ee406d920a155a20),       > > but that's only in the version in testing/sid.       >        > We talked about this bug on yesterdays team meeting, and it was       > commented as the kernel change is a security fix, it likely won't be       > reverted and the fix should be backported for chrony to the affected       > releases and schedule fixes via the point releases (with ideally the       > option to make an update as well make it as a SUA to get earlier to       > users affected by the issue).              Fair!               > Would you be willing to work on those backports and propose the point       > release updates?              I will handle this. I will provide a build for Jan to test because I do       not have that kind of setup at hand.               > https://salsa.debian.org/kernel-team/meetings/-/wikis/20260211       >        > Regards,       > Salvatore               Cheers,       Vincent              -----BEGIN PGP SIGNATURE-----              iHUEABYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCaY3yVwAKCRAQn1qAt/bg       AY1gAP9zB63i6cS85OlWEmeuBpFo2wMu3dveQnVHlPLQNETb1AEA+gQUDlXnF99R       W3kSwyOOAPmysB2MkLiKO27TjqJVRgY=       =HaRS       -----END PGP SIGNATURE-----              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca