2.6.20-r10 does not. ntpd runs on the machine, and cannot update the clock fast enough to keep sync. This is not an issue for 2.6.20-r10. Configs to follow
Created attachment 133159 [details] 2.6.20-hardened-r10.config (clock works)
Created attachment 133161 [details] 2.6.22-hardened-r7.config (clock fails)
Any idea pipacs ?
uhm, not a clue, i/we don't touch much code on amd64, i can't image what would cause such an effect... i take it that vanilla/non-hardened/grsec-off all work fine on the same box?
(In reply to comment #4) > i take it that vanilla/non-hardened/grsec-off all work fine on the same box? No idea. It would take time to test as I can't reboot into new kernels too often.
kernel: could someone on amd64 check vanilla- or gentoo-sources-2.6.20-r10 against 2.6.22-r7 with Uberlord's configs, please? The configs should work, just the CONFIG_PAX* and CONFIG_GRKERNSEC* settings are irrelevant on vanilla/gentoo-sources. uberlord: presumably simply typing "date" a minute apart will shows problem? 10 seconds a minute should be easily noticeable!
that wouldn't be a meaningful test -- this stuff is bound to be heavily hardware related, not config based.
Well, my test was that every few minutes, `ntpq -p` would show offsets increasing at a rate of knots, too much for it to sync to.
This appears to have been a configuration issue at my end - sorry.
