From owner-freebsd-current  Thu Mar 12 17:30:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA17476
          for freebsd-current-outgoing; Thu, 12 Mar 1998 17:30:19 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17470
          for <freebsd-current@FreeBSD.ORG>; Thu, 12 Mar 1998 17:30:15 -0800 (PST)
          (envelope-from ambrisko@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id RAA13598
	for <freebsd-current@FreeBSD.ORG>; Thu, 12 Mar 1998 17:22:36 -0800 (PST)
Received: from UNKNOWN(), claiming to be "crab.whistle.com"
 via SMTP by alpo.whistle.com, id smtpd013591; Thu Mar 12 17:22:29 1998
Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id RAA02278 for freebsd-current@FreeBSD.ORG; Thu, 12 Mar 1998 17:21:13 -0800 (PST)
From: Doug Ambrisko <ambrisko@whistle.com>
Message-Id: <199803130121.RAA02278@crab.whistle.com>
Subject: Re: Netboot problem: RPC timeout for server 0x0
In-Reply-To: <199803112120.NAA15073@crab.whistle.com> from Doug Ambrisko at "Mar 11, 98 01:20:54 pm"
To: freebsd-current@FreeBSD.ORG
Date: Thu, 12 Mar 1998 17:21:13 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL29 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've narrowed this problem down but haven't really made any progress.
I found the problem is cause by this commit:
  date: 1998/02/20 16:36:17;  author: phk;  state: Exp;  lines: +1 -1
  Replace TOD clock code with more systematic approach.

  Highlights:
    * Simple model for underlying hardware.
    * Hardware basis for timekeeping can be changed on the fly.
    * Only one hardware clock responsible for TOD keeping.
    * Provides a real nanotime() function.
    * Time granularity: .232E-18 seconds.
    * Frequency granularity:  .238E-12 s/s
    * Frequency adjustment is continuous in time.
    * Less overhead for frequency adjustment.
    * Improves xntpd performance.

The files touched are:
   sys/i386/conf/files.i386
   sys/i386/include/clock.h 
   sys/i386/isa/clock.c 
   sys/i386/isa/random_machdep.c 
   sys/kern/kern_clock.c 
   sys/kern/kern_ntptime.c 
   sys/kern/kern_time.c 
   sys/sys/time.h 
   sys/sys/timex.h

If go back in time just before this then it is fine, just after then
it breaks.  The time is 2/20/98 8:40:00 then it breaks, 8:30 is fine.

I couldn't find anything obvious to me that causes this the netboot
stuff to fail.  It seems that packets aren't be sent out.  However,
by removing this change and then doing an update to get to current.
The netbooted machine is much more stable and hasn't died yet.
Before it used to die when building a kernel, tonight the make
world test.  So nfs is looking much better which was what I wanted
to test in the first place.

Doug A.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message