+++ This bug was initially created as a clone of Bug #214757 +++ Original bug description: +30 days in the tree, no bugs, please do I've used chrony since ages on amd64 and never had problems with it. So I can see no reason why it should be "~" on amd64.
Arches don't march to stability alone...
(In reply to comment #1) > Arches don't march to stability alone... I didn't want to ask at first but - did You want to tell me that I had to supply further information?
(In reply to comment #2) > (In reply to comment #1) > > Arches don't march to stability alone... > > I didn't want to ask at first but - did You want to tell me that I had to > supply further information? No, not at all. This bug waits for input from me. Sorry. (I guess) he wanted to express that we try to stabilize all aches at once (and not only amd64). Obviously the other arches have it stabilized already. Nontheless, i disabled chrony some time ago because of lockups and didn't had the time to investigate further. Looking at the debian changelog, they disabled the rtcfile directive because of lockups. Do you use it?
(In reply to comment #3) > Looking at the debian changelog, they disabled the rtcfile directive because of > lockups. Do you use it? Yes, I do. Would the outcome normally be a lockup of chrony or a lockup of something else?
The system was unresponsible. Ok. This morning i tried it again and it started to work. I'll test it again on another box and on success i'll CC the amd64 arch team. I don't know what has changed: maybe some kernel rtc stuff?
(In reply to comment #5) > The system was unresponsible. > > Ok. This morning i tried it again and it started to work. I'll test it again on > another box and on success i'll CC the amd64 arch team. > I don't know what has changed: maybe some kernel rtc stuff? > Maybe, indeed. I'm using all the "new" rtc-stuff in kernel where appropriate for my machine - previously I remember there was only "enable enhanced rtc support" somewhere in character devices. Perhaps it would have locked my machine, too, back then, had I ever found the time to correctly configure it...
Please test and stabilize =net-misc/chrony-1.23 TEST: ~~~~ sudo /etc/init.d/chronyd start # see if it is online and queries the servers $ chronyc activity $ chronyc sources -v $ chronyc sourcestats -v # after some time it starts to adjust you clock $ chronyc tracking ~~~~ An untested configuration file: # /etc/chrony/chrony.conf server 0.pool.ntp.org minpoll 10 maxpoll 15 server 1.pool.ntp.org minpoll 10 maxpoll 15 server 2.pool.ntp.org minpoll 10 maxpoll 15 driftfile /var/lib/chrony/chrony.drift dumpdir /var/lib/chrony dumponexit maxupdateskew 100
amd64 stable, all arches done.
