lkml.org 
[lkml]   [1998]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Clue on 2.0.33 crashes
Hi,

On Fri, 20 Feb 1998, Doug Ledford wrote:

> Jos Vos wrote:
> >
> > Thomas Schenk wrote:
> >
> > > And I would add that we have found that prior to every freeze that our
> > > systems have experienced under 2.0.33, we find a syslog message from xntpd
> > > as follows:
> > >
> > > Feb 11 09:18:46 acme xntpd[151]: kernel pll status change 89
> > >
> > > These messages do not occur immediately prior to the crash, but we have
> > > theorized that this status change is a precursor to the lockup and the
> > > number of lockups that we have seen has been greatly reduced since we
> > > stopped using xntpd and started using ntpdate with the -b option in a
> > > cron job to sync the clocks.
>
> Hmmmm, I'm running xntpd on about 5 systems and I've never had a lock nor
> seen this message. Of course, that could be merely luck. The real question
> in my mind is what is that message all about. There were significant
> updates to the kernel time code in 2.0.32 or 2.0.33 (can't remember which).
> It seems (by memory) that the changes were written by either Ulrich
> {Wendel,Drepper} (SP?). Maybe the author would comment?

We're running xntpd on all of our machines. IIRC Ulrich Windl is not
subscribed to the kernel list.

> Doug Ledford <dledford@dialnet.net>

Hubert


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.077 / U:0.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site