From owner-freebsd-amd64@FreeBSD.ORG Tue Mar 17 06:02:50 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 676EC106566B for ; Tue, 17 Mar 2009 06:02:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with ESMTP id EB7A98FC08 for ; Tue, 17 Mar 2009 06:02:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 10670 invoked by uid 399); 17 Mar 2009 05:36:08 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 17 Mar 2009 05:36:08 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <49BF36C6.7060303@FreeBSD.org> Date: Mon, 16 Mar 2009 22:36:06 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.19 (X11/20090312) MIME-Version: 1.0 To: Kostik Belousov References: <200903081531.n28FVcqv005104@freefall.freebsd.org> <20090316161042.GN41617@deviant.kiev.zoral.com.ua> In-Reply-To: <20090316161042.GN41617@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org, Mark Atkinson Subject: Re: amd64/132418: Kernel not detect time-of-day clock [regression] X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 06:02:50 -0000 Kostik Belousov wrote: > On Mon, Mar 16, 2009 at 08:01:40AM -0700, Mark Atkinson wrote: >> kib@FreeBSD.org wrote: >>> Synopsis: Kernel not detect time-of-day clock [regression] >>> >>> State-Changed-From-To: open->closed >>> State-Changed-By: kib >>> State-Changed-When: Sun Mar 8 15:24:39 UTC 2009 >>> State-Changed-Why: >>> >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=132418 >> Any reason why this was closed? I have a box with this problem as well >> in -current. > > I mis-managed vi session, thus no reason for close was recorded. Check that > your /boot/device.hints is properly merged, in particular, look for the hints > for real-time clock. You can re-open the pr and add the reason. It won't be mailed out, but at least it will be there for posterity. Doug -- This .signature sanitized for your protection