From: Jean-Christian de Rivaz <jc@eclis.ch>
To: john stultz <johnstul@us.ibm.com>
Cc: rddunlap@osdl.org, Len Brown <len.brown@intel.com>,
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 01:15:30 +0100 [thread overview]
Message-ID: <436AA822.9060403@eclis.ch> (raw)
In-Reply-To: <1131058482.27168.612.camel@cog.beaverton.ibm.com>
john stultz a écrit :
> You might check booting w/ noapic to see if that changes the behaviour
> in 2.6.10.
Yes! With a vanilla 2.6.10, the noapic solve the problem and ntpd is happy.
> Jean-Christian: Since it ACPI is involved, have you verified that you're
> running the current BIOS for your system?
More fun now: it look like the BIOS actually used on this mainboard is
not designed for it, but for an other board!!!
The board is exactly this one "K7N2 Delta-L":
http://www.msi.com.tw/program/support/download/dld/spt_dld_detail.php?UID=436&kind=1
And according to MSI it must use a BIOS version 5.9. But when I enter
into the BIOS setup the version info say "W6570MS V7.4 081203".
Here is the BIOS version history:
http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=436&kind=1
The version 7.4 dated 2003-8-12 has a special note:
1. Only for K7N2 Delta-ILSR
2. This BIOS cannot be used on K7N2 Delta-L
Crasy. I use this board without any issue since around two years and
only found the first problem when upgrading to the kernel 2.6.14!
At least the situation is more clear now.
--
Jean-Christian de Rivaz
next prev parent reply other threads:[~2005-11-04 0:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 23:05 NTP broken with 2.6.14 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 3:44 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
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=436AA822.9060403@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=macro@linux-mips.org \
--cc=rddunlap@osdl.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