Mailinglist Archive: opensuse (4634 mails)

< Previous Next >
Re: [opensuse] Re: 10.2 system clock too fast and NTP
  • From: Darryl Gregorash <raven@xxxxxxxxxxxxx>
  • Date: Sun, 17 Dec 2006 06:45:29 -0600
  • Message-id: <45853BE9.2080702@xxxxxxxxxxxxx>
On 2006-12-17 06:31, Mark Hounschell wrote:
> Darryl Gregorash wrote:
>
>> On 2006-12-17 04:48, Mark Hounschell wrote:
>>
>>> A dmesg output from the OP might shed some light.
>>>
>> That won't help at all, since nothing related to the clocks is logged to
>> the system log (the default xntp configuration is logging to /var/log/ntp).
>>
>> The only clues available are from reading the kernel time variables
>> directly (adjtimex, or ntpdc if ntpd is running), and from comparing the
>> hardware of systems that are having the problem.
>>
>>
>
>
> dmesg | grep clock
> Time: acpi_pm clocksource has been installed.
>
dmesg|grep clock
<null>

All those dropped SYN packets since the last reboot may have a lot to do
with that, but "grep clock /var/log/boot.msg" also shows nada -- whereas
I do have this:
<6>Using pmtmr for high-res timesource

and nothing else related to the clock.

> All the clock source stuff is in kernel not ntp
Of course it is, but not much of any significance gets logged --
apparently just a line or two to say what source is being used. How is
that helpful, unless all you're interested in doing is changing which
timesource is used? ntpd logs more meaningful stuff into the syslog than
what I find in boot.msg.

duh

--
The best way to accelerate a computer running Windows is at 9.81 m/s²

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >