From owner-freebsd-current Mon Sep 20 9:46:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles540.castles.com [208.214.165.104]) by hub.freebsd.org (Postfix) with ESMTP id D1B2814CCD for ; Mon, 20 Sep 1999 09:46:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA32335; Mon, 20 Sep 1999 09:39:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909201639.JAA32335@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-reply-to: Your message of "Mon, 20 Sep 1999 17:52:16 +0200." <23502.937842736@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Sep 1999 09:39:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Use a watchdog timeout like you should for any device that may hang. > >Don't waste time running it every clock tick. > > > >ISTR that we thought that the bug might be caused by a bug in unwanted > >SMI interrupt handling. > > If anybody can reproduce this reliably on a *BX chipset I have > code that will block SMI interrupts we can test with... I'm not sure I follow what the alleged problem is here; who is handling the "unwanted" SMIs? If it's the BIOS, the last thing you want to do is block all SMIs. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message