From owner-freebsd-current Thu Dec 16 12:49:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (Postfix) with ESMTP id AAA1B15707 for ; Thu, 16 Dec 1999 12:49:37 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id MAA07935; Thu, 16 Dec 1999 12:49:26 -0800 (PST) Date: Thu, 16 Dec 1999 12:49:27 -0800 (PST) From: Tom Bartol To: Warner Losh Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Serious server-side NFS problem In-Reply-To: <199912162042.NAA73909@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Dec 1999, Warner Losh wrote: > In message Tom Bartol writes: > : IIRC it does update uptime properly after a suspend in 2.2.8 but does not > : do so in 3.X and -current on my ThinkPad 770. > > define correctly. Eg, if I suspend for an hour it adds an hour? > > Warner > Yeah, that's what I meant by "correctly". I don't recall seeing a "thundering herd" effect afterwards. Hmmm... which reminds me, I believe this was not stock 2.2.8 but rather 2.2.8-PAO. I had thought that the lion's share of PAO code got merged into 3.0-current at some point. When I tried 3.0-current after this merge, suspend and resume worked fine on my 770 with the exception of uptime. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message