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: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	linux-kernel@vger.kernel.org, dean@arctic.org
Subject: Re: NTP broken with 2.6.14
Date: Thu, 03 Nov 2005 22:28:32 +0100	[thread overview]
Message-ID: <436A8100.6090609@eclis.ch> (raw)
In-Reply-To: <1131048670.27168.573.camel@cog.beaverton.ibm.com>

john stultz a écrit :

>>This is happening on an Asus A7N8X-E-DX with an Athlon XP 2800+.  I have
>>acpi enabled, so who knows if that is what is breaking things.  There
>>does seem to have been time keeping issues on ati chipsets big time in
>>recent kernels, and some other acpi issues at times, so it wouldn't
>>surprise me if a fix for one issue causes problems on another chipset.
>>The chipset on this board is the nforce2.
> 
> 
> Yea, we have some issues with a few specific chipsets, but those were
> not regressions to my knowledge. 
> 
> Hmm. Check bug #5038 to see if sounds familiar.
> http://bugzilla.kernel.org/show_bug.cgi?id=5038

Interresting bug report. You have to know that the machine (nForce2 
based) that have the ntpd problem is NFS root and import via NFS several 
mount points. In fact this machine don't have any hard disk and make 
everything over NFS. ( This way, with a passiv water cooling and passiv 
power supply I enjoy an absolutly silent dektop. )

I have an other machine (VIA based) with a kernel 2.6.12 that is NFS 
root the same way but don't have the ntpd problem.

-- 
Jean-Christian de Rivaz

  parent reply	other threads:[~2005-11-03 21:28 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 [this message]
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
  -- 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=436A8100.6090609@eclis.ch \
    --to=jc@eclis.ch \
    --cc=dean@arctic.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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