ntp doesn't work after suspend / resume

Bug #96788 reported by Valient Gough
6
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ntp

My IBM Thinkpad suspends and resumes without any problems, except that the NTP daemon stops working.

This is on Kubuntu 7.04 Beta. NTP suspend/resume worked on SuSE 10.0, which was what this system had on it until a couple days ago.

Perhaps ntp doesn't like the resume.d/50-time.sh command?

Ntp works fine after restarting, but is always in a broken (but still running) state after a resume. The first time it happened, I didn't notice for several hours, and it was still in the broken state, so it is not auto-correcting.

Revision history for this message
Mike Dahlgren (dahlgren) wrote :

Thank you for your bug report. I believe what you are experiencing is identical to bug #76021, and have marked this as a duplicate.

   Thanks,
       ~ Mike

Revision history for this message
Jakob Unterwurzacher (jakobunt) wrote :

IMHO this problem is different and #76021 should be rejected.
No one needed ntpdate if ntpd was working properly.

Ntpd should be fixed to cope with suspend or stopped before standby and restarted on resume.
It will then set the correct time within a few minutes, which is acceptable, because it does useful things within these minutes (select best time source, slow down or speed up clock on small offsets etc. ).

Revision history for this message
Jakob Unterwurzacher (jakobunt) wrote :

BTW: This is still in Gutsy, i am experiencing it.

Revision history for this message
Jakob Unterwurzacher (jakobunt) wrote :

Hmm, probably i am not experiencing this.
My laptop's time drifted away some 20 minutes in *one night* when on standby - causing ntpd to stop doing anything because of
"ntpd[6677]: time correction of 1800 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time."

Revision history for this message
Marc Schiffbauer (mschiff) wrote :

This problem still exists in hardy and I think I have some more information about it:

What I have observed is, that ntpd gets restarted several times on every resume and also on system boot:
It will be restarted for every interface in /etc/network/interfaces that is not loopback by /etc/network/if-up.d/ntpdate

So /etc/network/if-up.d/ntpdate seems to be the problem or at least part of the problem.

Revision history for this message
Hew (hew) wrote :

Confirming based on comments. Thanks for your report.

Changed in ntp:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Valient Gough (vgough) wrote :

I haven't seen this problem on my laptop running Hardy. The laptop that had the problem is now running Fedora.

Revision history for this message
Chuck Short (zulcss) wrote :

Closing based on comments in the bug.

Regards
chuck

Changed in ntp (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.