From owner-freebsd-bugs@FreeBSD.ORG Thu May 1 10:20:08 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 756A637B401 for ; Thu, 1 May 2003 10:20:08 -0700 (PDT) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEE4E43F93 for ; Thu, 1 May 2003 10:20:07 -0700 (PDT) (envelope-from simonw@matteworld.com) Received: from user-vcauqit.dsl.mindspring.com ([216.175.106.93] helo=matteworld.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19BHj3-0001Dk-00; Thu, 01 May 2003 10:20:05 -0700 Sender: simonw@FreeBSD.ORG Message-ID: <3EB15744.93CBA39E@matteworld.com> Date: Thu, 01 May 2003 10:20:04 -0700 From: Simon Walton Organization: Matte World Digital X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5 IP32) X-Accept-Language: en MIME-Version: 1.0 To: Matthias Buelow References: <200304252230.h3PMUGFS078258@freefall.freebsd.org> <20030426193033.GI1356@moghedien.mukappabeta.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-bugs@FreeBSD.org Subject: Re: i386/43491: microuptime () went backwards X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 17:20:08 -0000 > > Just to add to the record, I have seen this to also be part > of the effects of a broken SCSI drive, apparently with the drive's > electronics gone stale. Sometimes just a massive stream of the > above microuptime()... messages whenever the disk was accessed, > and after some time (but not always) followed by a total lockup > with a bus reset every second (but sometimes just thousands of > microuptime() messages, system was going normal apart from that, > except for time+date and the logfile filling, of course.) > Removing the drive fixed that. I've noticed that the errors sometimes correspond to heavy disk use (on either of its two disks), but I am not seeing bus resets and the disks otherwise seem fine. I can clear the condition by setting the i8254 frequency with sysctl -w machdep.i8254_freq, even if I don't actually change the frequency. I've also noticed this message on startup APIC_IO: MP table broken: 8259->APIC entry missing! so I suspect my problem is related to APIC interrupts. Simon