From: Jean-Christian de Rivaz <jc@eclis.ch>
To: Jean-Christian de Rivaz <jc@eclis.ch>
Cc: john stultz <johnstul@us.ibm.com>,
"Brown, Len" <len.brown@intel.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
macro@linux-mips.org, linux-kernel@vger.kernel.org,
dean@arctic.org, zippel@linux-m68k.org
Subject: Re: NTP broken with 2.6.14
Date: Fri, 04 Nov 2005 18:41:03 +0100 [thread overview]
Message-ID: <436B9D2F.5050503@eclis.ch> (raw)
In-Reply-To: <436B8EDD.5050703@eclis.ch>
Jean-Christian de Rivaz a écrit :
> Well, I finally get evidence that my mainboard is a "K7N2 Delta-ILSR"
> not a "K7N2 Delta-L" (from the shipping package, the invoice, and online
> review of the two motherboards). So the BIOS version 7.4 is a valid one.
> I updated the BIOS to the version 7.8. Now the drift is low and ntpd
> happy (me too), all that without the "noapic" option.
>
> Strange is that the kernel log is almost the same but this little
> difference:
>
> --- kernel 2.6.14 BIOS V7.4
> +++ kernel 2.6.14 BIOS V7.8
> talla kernel: Normal zone: 225280 pages, LIFO batch:31
> talla kernel: HighMem zone: 294896 pages, LIFO batch:31
> talla kernel: DMI 2.3 present.
> -talla kernel: ACPI: RSDP (v000 Nvidia )
> @ 0x000f73b0
> +talla kernel: ACPI: RSDP (v000 Nvidia )
> @ 0x000f73d0
> talla kernel: ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
> 0x00000000) @ 0x7fff3000
> talla kernel: ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
> 0x00000000) @ 0x7fff3040
> -talla kernel: ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
> 0x00000000) @ 0x7fff7780
> +talla kernel: ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD
> 0x00000000) @ 0x7fff77c0
> talla kernel: ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT
> 0x0100000e) @ 0x00000000
> talla kernel: ACPI: PM-Timer IO Port: 0x4008
> talla kernel: ACPI: Local APIC address 0xfee00000
>
> The following message is still here:
>
> talla kernel: ENABLING IO-APIC IRQs
> talla kernel: ..TIMER: vector=0x31 pin1=0 pin2=-1
>
> But all work fine with the latest BIOS.
>
> For me the issue is solved. A lot of thanks to all peoples that helped
> to this thread with special mention for John Stultz. I hope that the
> others that have the same problem can solve it the same way.
Just to show how well is the 2.6.14 with the latest BIOS, here is the
drift according to the John Stultz python script:
04 Nov 17:45:23 offset: 1.7e-05 drift: 3.0 ppm
04 Nov 17:46:24 offset: 2e-05 drift: 0.0967741935484 ppm
04 Nov 17:47:24 offset: 2.7e-05 drift: 0.106557377049 ppm
04 Nov 17:48:24 offset: 4.8e-05 drift: 0.186813186813 ppm
04 Nov 17:49:24 offset: 6.5e-05 drift: 0.210743801653 ppm
04 Nov 17:50:24 offset: 9.4e-05 drift: 0.264900662252 ppm
04 Nov 17:51:24 offset: 0.000122 drift: 0.298342541436 ppm
04 Nov 17:52:24 offset: 0.000168 drift: 0.364928909953 ppm
04 Nov 17:53:25 offset: 0.0002 drift: 0.385093167702 ppm
04 Nov 17:54:25 offset: 0.000266 drift: 0.46408839779 ppm
04 Nov 17:55:25 offset: 0.000305 drift: 0.482587064677 ppm
04 Nov 17:56:25 offset: 0.000356 drift: 0.515837104072 ppm
04 Nov 17:57:25 offset: 0.000415 drift: 0.554633471646 ppm
04 Nov 17:58:25 offset: 0.000475 drift: 0.588761174968 ppm
04 Nov 17:59:25 offset: 0.000555 drift: 0.641755634638 ppm
04 Nov 18:00:25 offset: 0.000624 drift: 0.675526024363 ppm
04 Nov 18:01:25 offset: 0.000711 drift: 0.723779854621 ppm
04 Nov 18:02:26 offset: 0.00079 drift: 0.7578125 ppm
04 Nov 18:03:26 offset: 0.000868 drift: 0.787822878229 ppm
04 Nov 18:04:26 offset: 0.000954 drift: 0.821678321678 ppm
04 Nov 18:05:26 offset: 0.001029 drift: 0.843023255814 ppm
04 Nov 18:06:26 offset: 0.001114 drift: 0.870253164557 ppm
04 Nov 18:07:26 offset: 0.001196 drift: 0.892749244713 ppm
04 Nov 18:08:26 offset: 0.001274 drift: 0.910404624277 ppm
04 Nov 18:09:26 offset: 0.00136 drift: 0.932132963989 ppm
04 Nov 18:10:26 offset: 0.001445 drift: 0.951462765957 ppm
04 Nov 18:11:27 offset: 0.001537 drift: 0.973162939297 ppm
04 Nov 18:12:27 offset: 0.001627 drift: 0.992615384615 ppm
It's very very low, far more that with 2.6.9 kernel and old BIOS. MSI
have obviousely fixed a timer issus in the BIOS, but this is not show in
the BIOS history.
--
Jean-Christian de Rivaz
next prev parent reply other threads:[~2005-11-04 17:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 3:44 NTP broken with 2.6.14 Brown, Len
2005-11-04 4:07 ` john stultz
2005-11-04 13:51 ` Lennart Sorensen
2005-11-04 16:39 ` Jean-Christian de Rivaz
2005-11-04 17:41 ` Jean-Christian de Rivaz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 23:05 Jean-Christian de Rivaz
2005-11-02 23:21 ` john stultz
2005-11-02 23:37 ` Jean-Christian de Rivaz
2005-11-03 0:15 ` john stultz
2005-11-03 0:45 ` Jean-Christian de Rivaz
2005-11-03 1:07 ` john stultz
2005-11-03 2:26 ` Jean-Christian de Rivaz
2005-11-03 19:32 ` john stultz
2005-11-03 19:51 ` Lennart Sorensen
2005-11-03 20:11 ` john stultz
2005-11-03 20:48 ` Lennart Sorensen
2005-11-03 21:00 ` john stultz
2005-11-03 21:12 ` Lennart Sorensen
2005-11-03 21:28 ` Jean-Christian de Rivaz
2005-11-03 21:12 ` Jean-Christian de Rivaz
2005-11-03 21:41 ` john stultz
2005-11-03 22:10 ` Jean-Christian de Rivaz
2005-11-03 22:54 ` john stultz
2005-11-04 0:15 ` Jean-Christian de Rivaz
2005-11-04 0:40 ` john stultz
2005-11-04 2:50 ` Jean-Christian de Rivaz
2005-11-06 22:49 ` Hans-Peter Jansen
2005-11-07 21:44 ` Jean-Christian de Rivaz
2005-11-04 12:40 ` Maciej W. Rozycki
2005-11-02 23:24 ` john stultz
2005-11-03 0:36 ` Roman Zippel
2005-11-03 1:13 ` Jean-Christian de Rivaz
2005-11-03 9:42 ` Roman Zippel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=436B9D2F.5050503@eclis.ch \
--to=jc@eclis.ch \
--cc=dean@arctic.org \
--cc=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=macro@linux-mips.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox