All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ntp problems
Date: Tue, 06 Dec 2005 12:44:13 +0100	[thread overview]
Message-ID: <4395798D.6040201@eclis.ch> (raw)
In-Reply-To: <200512052301.16998.gene.heskett@verizon.net>

Gene Heskett a écrit :

>>Hmmm. Indeed the nforce2 has had a number of problems, but I'm not sure
>>why it would have changed recently. Can you bound at all the kernel
>>versions where it worked and where it broke? Additionally, do be sure
>>you have the most recent BIOS, I've seen a number of nforce2 issues be
>>resolved with a BIOS update.
> 
> 
> I've already put more powerdown cycles (60 some) on my hard drives 
> fighting with the recent tv card problem, I'd like to get some uptime 
> in.  All I know for sure is if I build 2.6.15-rc5 with acpi, ntpd 
> doesn't work.  ntpdate does, but ntpd doesn't.  And both dmesg and the 
> ntp.log (and -d's passed at launch time do not make it more verbose, 
> they just keep it from starting) are silent as to the diffs other than 
> the interrupt number shuffling in dmesg when its on.  But I suspect it 
> may have started with 2.6.15-rc2, and I didn't build rc1.  And I *think* 
> it worked as recently as 2.6.14.1 with it turned on.  I've cleaned house 
> in /usr/src's so I don't have anything older.  Sorry.

I have to agree with John Stultz. I am one with a nForce2 chipset where 
updating to the latest BIOS have totaly solved the excatly same ntpd 
problem.

Regards,
-- 
Jean-Christian de Rivaz

  parent reply	other threads:[~2005-12-06 11:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05  5:31 ntp problems Gene Heskett
2005-12-05 21:39 ` john stultz
2005-12-05 23:33   ` Gene Heskett
2005-12-06  0:14     ` john stultz
2005-12-06  2:07       ` Gene Heskett
2005-12-06  3:20         ` john stultz
2005-12-06  4:01           ` Gene Heskett
2005-12-06  7:33             ` jdow
2005-12-06 16:58               ` Gene Heskett
2005-12-07  0:48                 ` jdow
2005-12-06 11:44             ` Jean-Christian de Rivaz [this message]
2005-12-06 19:02               ` Gene Heskett
2005-12-06 21:22                 ` Gene Heskett
2005-12-07  5:14                   ` Kyle Moffett
2005-12-07  6:08                     ` Gene Heskett
2005-12-07 21:56                       ` Jean-Christian de Rivaz
2005-12-07 22:50                         ` Gene Heskett
2005-12-07 23:34                           ` Jean-Christian de Rivaz
2005-12-08  0:14                             ` Gene Heskett
2005-12-11 19:05                         ` Gene Heskett
2005-12-07  3:44           ` Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2004-01-24 22:08 NTP problems Shaw, Marco
2004-01-26  8:01 ` Erik Hensema

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=4395798D.6040201@eclis.ch \
    --to=jc@eclis.ch \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.