On Wed, Sep 2, 2015 at 2:03 AM, John Stultz <john.stultz@xxxxxxxxxx> wrote: > On Tue, Sep 1, 2015 at 5:36 PM, Nuno Gonçalves <nunojpg@xxxxxxxxx> wrote: >> On Tue, Sep 1, 2015 at 9:25 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: >>> On Tue, 1 Sep 2015, Nuno Gonçalves wrote: >>> >>>> There is a regression on the clock system since v3.16-rc5-111-g4396e05 >>>> [1], >>> >>>> [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4396e058c52e167729729cf64ea3dfa229637086 >>> >>> That commit has absolutely nothing to do with NTP. I fear your bisect >>> went down the wrong road somewhere. >> >> You are right. It is v3.16-rc5-114-gdc49159: >> >> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=dc491596f6394382fbc74ad331156207d619fa0a >> >> I've triple checked it this time. Not sure where I did the mistake to >> get it wrong by 3 commits. > > This commit is much more believable (though surprising as that change > was found to greatly improve results for most uses). > > Can you provide any more details about how the problem is reproduced > (kernel config, what userland images are you using, etc)? I've got a > BBB myself so I can try to see whats going on. > > thanks > -john I'm using a clean Debian image: https://rcn-ee.com/rootfs/bb.org/testing/2015-08-31/console/bone-debian-8.1-console-armhf-2015-08-31-2gb.img.xz And just installing chrony from the feeds. With any kernel from 3.17 you'll have wrong estimates at chronyc sourcestats. Miroslav did some tests at a beaglebone I set for him, according to my initial post. Miroslav also dismissed this being related to nohz after some tests. Thanks, Nuno -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html