From: john stultz <johnstul@us.ibm.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Jean-Christian de Rivaz <jc@eclis.ch>,
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: Thu, 03 Nov 2005 20:07:13 -0800 [thread overview]
Message-ID: <1131077233.27168.627.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005117C9B@hdsmsx401.amr.corp.intel.com>
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.
thanks
-john
next prev parent reply other threads:[~2005-11-04 4:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 3:44 Brown, Len
2005-11-04 4:07 ` john stultz [this message]
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
-- 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=1131077233.27168.627.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=dean@arctic.org \
--cc=jc@eclis.ch \
--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
all inboxes | Powered by JetHome®