From owner-freebsd-current Wed Mar 4 20:11:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20615 for freebsd-current-outgoing; Wed, 4 Mar 1998 20:11:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20610 for ; Wed, 4 Mar 1998 20:11:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA24061 for ; Wed, 4 Mar 1998 20:09:09 -0800 (PST) Message-Id: <199803050409.UAA24061@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-current@FreeBSD.ORG Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) In-reply-to: Your message of "Wed, 04 Mar 1998 20:04:48 PST." <19980304200448.26184@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Mar 1998 20:09:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith scribbled this message on Mar 4: > > > The solution is to use either a SCSI disk system, or support > > > busmastering IDE. The real problem is the crazy IRQ priorities of > > > the PC architeture. > > > > This last hits the nail square on the head. > > then can you tell my bt946 not to cause sio overflows?? :) I wish. 8( You could try hauling the PCI latency timer right down to see whether that affects things. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message