From owner-freebsd-sparc64@FreeBSD.ORG Mon Feb 16 18:38:47 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB95F16A4CF for ; Mon, 16 Feb 2004 18:38:47 -0800 (PST) Received: from grogged.dyndns.org (c-24-118-162-123.mn.client2.attbi.com [24.118.162.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id A50D143D1D for ; Mon, 16 Feb 2004 18:38:47 -0800 (PST) (envelope-from matt@grogged.dyndns.org) Received: by grogged.dyndns.org (Postfix, from userid 1001) id 8B880212; Mon, 16 Feb 2004 20:36:19 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by grogged.dyndns.org (Postfix) with ESMTP id 87E9D1EA; Mon, 16 Feb 2004 20:36:19 -0600 (CST) Date: Mon, 16 Feb 2004 20:36:19 -0600 (CST) From: matt To: Garance A Drosihn In-Reply-To: Message-ID: <20040216202835.D31791@grogged.dyndns.org> References: <20040215060047.GA62840@dhcp01.pn.xcllnt.net> <20040215165913.M30161@grogged.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: sparc64@freebsd.org Subject: Re: Problem with DHCLIENT vs 64-bit time_t X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 02:38:47 -0000 I hate to add to the problems instead of proposing solutions, but I noticed that /etc/periodic/weekly/310.locate seems to be broken after the 64 bit time_t switch. I'll run another buildworld out of the 64 bit time_t system I have up with cvsup'd sources, see what happens... I haven't had any problems starting dhclient, works fine other than the fact that it absorbs considerable system resources. -m On Mon, 16 Feb 2004, Garance A Drosihn wrote: > At 5:13 PM -0600 2/15/04, matt wrote: > > > > Anyhow, here is the strangeness. After compiling/installing > > the 64 bit time_t world/kernel, I'm getting some serious lag > > on this machine. When logged in via ssh, the shell freezes > > every few seconds for a brief period of time. ... > > And in a later message, he wrote: > > Killing dhclient brought things back to normal - and yes, I > > did remove /var/db/dhcp.leases (had to, dhclient wouldn't > > work until I did). My kernel was just a run of the mill > > GENERIC, no changes. > > Well, there does seem to be some kind of problem here, but I > don't know what to do about it just yet. In my earlier testing, > I did do some testing with a dhcp-configured machine, but not a > lot of it. > > After reading the above report, I took my system which was already > upgraded to 64-bTT, and which also already has all of it's ports > recompiled for 64-bTT. I cvsup'ed the base system, and did a > complete new buildworld/installworld cycle with 64-bTT. So, it > is a system which has successfully gone through two consecutive > 64-bTT builds without error. I have not run into any other > problems with this upgraded system. > > I tried configuring it for DHCP, rebooted it, and the startup > hung at the point of starting dhclient. I ctrl-c'ed out of > the hang. Once the system was up, I tried running dhclient > again. Again it hung. In my case it's hanging before it gets > any information (hme0 is not configured at all). I assume > that in Matt's case, it did get some dhcp address, because he > said he was ssh'ed into it. This testing reminded me that > dhclient did sometimes hang on me in my earlier testing, but > I forgot about that when I had some reboots where it worked. > > That's about as much as I know about the problem so far. Does > anyone have some time to look into this? > > -- > Garance Alistair Drosehn = gad@gilead.netel.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu >