public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: john stultz <johnstul@us.ibm.com>
Cc: "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 17:39:57 +0100	[thread overview]
Message-ID: <436B8EDD.5050703@eclis.ch> (raw)
In-Reply-To: <1131077233.27168.627.camel@cog.beaverton.ibm.com>

john stultz a écrit :
> On Thu, 2005-11-03 at 22:44 -0500, Brown, Len wrote:
> 
>>NFORCE2 on an ACPI-enabled kernel should automatically invoke
>>the acpi_skip_timer_override BIOS workaround -- as
>>the NFORCE family of chip-sets have the timer interrupt
>>attached to pin-0, but some of them shipped with
>>a bogus BIOS over-ride telling Linux the timer is on pin-2.
>>
>>This issue is quite old -- google NFORCE2 and acpi_skip_timer_override.
>>IIR there are whole web-sites with NFORCE2
>>workarounds provided by its dedicated fans...
> 
> 
> Thanks for the info, Len. Although its odd that the Jean-Christian's
> issue appears to show up around the time the fix you mention shows up. 
> 
> Regardless, Jean-Chistian has some sever BIOS problems, so until those
> are resolved, I suggest he use the workaround (noapic) and ping us if
> the issue persists once he arrives at a supportable configuration.

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.

Best regards,
-- 
Jean-Christian de Rivaz

  parent reply	other threads:[~2005-11-04 16:40 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 [this message]
2005-11-04 17:41     ` Jean-Christian de Rivaz
  -- 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=436B8EDD.5050703@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