From owner-freebsd-stable@FreeBSD.ORG Fri Nov 18 22:33:37 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E143E16A41F for ; Fri, 18 Nov 2005 22:33:37 +0000 (GMT) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7560543D45 for ; Fri, 18 Nov 2005 22:33:37 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 50455 invoked by uid 0); 18 Nov 2005 22:33:36 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Nov 2005 22:33:36 -0000 Date: Fri, 18 Nov 2005 17:33:39 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@charles-sprickmans-computer.local To: Uwe Doering In-Reply-To: <437D91FD.8050809@geminix.org> Message-ID: References: <437D91FD.8050809@geminix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org Subject: Re: 4.8 "alternate system clock has died" error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2005 22:33:38 -0000 On Fri, 18 Nov 2005, Uwe Doering wrote: > Charles Sprickman wrote: >> Hello all, >> >> I've been digging through Google for more information on this. I have a >> 4.8 box that's been up for about 430 days. In the last week or so, top and >> ps have started reporting all CPU usage numbers as zero, and running >> "systat -vmstat" results in the message "The alternate system clock has >> died! Reverting to ``pigs'' display". >> >> I've found instances of this message in the archives for some 3.x users, >> some pre 4.8 users and some 5.3 users. >> >> There were a number of suggestions including a patch if pre-4.8, sending >> init a HUP, and setting the following sysctl mib: "kern.timecounter.method: >> 1". >> >> I'm already at 4.8-p24, so I did not look into patching anything, and >> HUP'ing init and setting the sysctl mib does not seem to have any effect. >> >> I'm not quite ready to believe that some hardware has actually failed. >> Perhaps due to the long uptime something has rolled over? > > We had this once at work, quite a while ago. The "alternate system clock" is > in fact the Real Time Clock (RTC) on the mainboard. In our case we were > lucky in that it was just the quartz device that failed due to an improperly > soldered lead which finally came off. We fixed the soldering and the problem > was gone. Are there any tools to verify that the RTC is working? I don't exactly understand what the RTC is, but would the machine not be suffering some other problems if there was an actual hardware failure? Doesn't the system rely on this to time everything from the processors to memory to PCI slots and interrupts? Is there any simple way to figure out if this is hardware or software? > Now, there are of course plenty of other hardware reasons why the RTC can > fail, even temporarily like in your case. Perhaps it is really time for a > new mainboard. Ouch, that would hurt. This machine does not have much room for tinkering (mail server). Thanks, Charles > Uwe > -- > Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers > gemini@geminix.org | http://www.escapebox.net >