From owner-freebsd-current Thu Nov 7 18:26:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29394 for current-outgoing; Thu, 7 Nov 1996 18:26:14 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA29387 for ; Thu, 7 Nov 1996 18:26:09 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id SAA00756 for ; Thu, 7 Nov 1996 18:24:48 -0800 (PST) Message-ID: <328299DD.41C67EA6@whistle.com> Date: Thu, 07 Nov 1996 18:24:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: "the alternate system clock has died" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "the alternate system clock has died" is the message that system -vmstat is giving me.. vmstat -i shows the rtc0 interupt rate (over the whole booted uptime) gradually dropping so I guess it's right.. rtc0 has stopped interrupting.. there was discussion of this a few weeks agao but I skimmed it, and now I can't find it in the archives. was there a resolution? this is from a -current of about 3 weeks ago. it seems to die at some stage when we have both network operation and sio action. (and disk too I guess) I can get it to happen pretty reliably on one machine. I'll substitute hardware and see if it can be made to happen there too. any leads? julian