From owner-freebsd-current@FreeBSD.ORG Thu Feb 25 19:39:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43E5C106566B; Thu, 25 Feb 2010 19:39:09 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-iw0-f185.google.com (mail-iw0-f185.google.com [209.85.223.185]) by mx1.freebsd.org (Postfix) with ESMTP id ECAE98FC32; Thu, 25 Feb 2010 19:39:08 +0000 (UTC) Received: by iwn15 with SMTP id 15so5448138iwn.7 for ; Thu, 25 Feb 2010 11:39:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=TvBjnP+Eir4NLOf9xG9ah5GcWauHbd9yxVE4TnGiLIA=; b=DjVCV9srv1wHuF0srmd4vzQuFtppW/t+Gl46zEgIDAXAZ+gaaNZoGjQqhNdycWp/vx 8Vlq+IQ5i6WaZbWtt4A8e9PwevOJ4RvknQ0PYz9C3dEA0h7KxaF15UJZGeQTfPBB2nVm FLLkaVSuaoCrnFMhV/K7nBzDLdwkeFRi8oB+Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=Ijb7gfODUjYSmqWRElaBnbjDEbBIeYv1CLPjhIsONUozs8bMtdvhVZbayeoOTICXPN tIoUAzOB0BRTV/0uK0TGDbXT8w8t6/GUhhCRr/rPa226rAKW36ddmQGTcUw6c6qApb/N O1L9RfdO3vOI7Y7XQwv64g2j2zrzIm6UHw9Ok= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.231.154.207 with SMTP id p15mr145001ibw.91.1267126741595; Thu, 25 Feb 2010 11:39:01 -0800 (PST) In-Reply-To: <20100225192301.GI13807@michelle.cdnetworks.com> References: <4B75A801.3040107@delphij.net> <20100217213842.GG1394@michelle.cdnetworks.com> <3bbf2fe11002250748h489ff97dw3f2d0e29721b98d9@mail.gmail.com> <20100225192301.GI13807@michelle.cdnetworks.com> Date: Thu, 25 Feb 2010 20:39:01 +0100 X-Google-Sender-Auth: 5367ba2c784c344a Message-ID: <3bbf2fe11002251139y510467dfwf22f64a7b3d9fc45@mail.gmail.com> From: Attilio Rao To: pyunyh@gmail.com Content-Type: text/plain; charset=UTF-8 Cc: Dima Panov , Gleb Kurtsou , Richard Todd , Gavin Atkinson , Alexander Motin , FreeBSD Current , Alexander Logvinov Subject: Re: time doesn't work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2010 19:39:09 -0000 2010/2/25 Pyun YongHyeon : > On Thu, Feb 25, 2010 at 04:48:28PM +0100, Attilio Rao wrote: >> 2010/2/17 Pyun YongHyeon : >> > On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote: >> >> Hi, >> >> >> >> On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson >> >> wrote: >> >> >> /mnt: write failed, filesystem is full >> >> >> gzip: write: No space left on device >> >> >> gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting >> >> >> gzip: leaving original randomfile >> >> >> 0.000u 85.063s 1:25.10 99.9% ??0+0k 12440+12839io 7pf+0w >> >> > >> >> > Does reverting r202387, 202441 and 202534 make any difference? >> >> >> >> Yes, reverting these revisions makes everything back to normal >> >> (including top -P). >> >> >> > >> > I'm not sure this is also related with breakage of >> > "systat -vmstat 1" on amd64 CURRENT. systat(1) shows "The alternate >> > system clock has died! ??Reverting to ``pigs'' display." message and >> > does not work as expected. >> > When I run systat(1) on sparc64 CURRENT it worked as expected so I vaguely >> > guess it's related with attilio's change.(CCed) >> >> [CC'ing also others that may got this issue] >> >> Can you please upgrade to the newest CURRENT, try the attached patch >> and report if system choiches the right timer alone: >> http://www.freebsd.org/~attilio/Sandvine/STABLE_8/statclock_aliasing/statclock-fixup.diff >> >> with 'alone', I mean that you might strip from config all the helping >> tips (machdep.lapic_allclocks). >> > > With the patch above, systat(1) seems to work as expected. > One thing I see is dmesg output is > > RTC BIOS diagnostic error 11 > > I'm not sure whether I had this message in previous kernel. It is likely you had after the incriminating revision but not because the previous patch broke it, just because the previous patch does enable atrtc (while the old kernel didn't do this). Attilio -- Peace can only be achieved by understanding - A. Einstein