From owner-freebsd-current Wed Mar 4 20:38:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26128 for freebsd-current-outgoing; Wed, 4 Mar 1998 20:38:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26073 for ; Wed, 4 Mar 1998 20:38:08 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id OAA21951; Thu, 5 Mar 1998 14:46:07 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma021915; Thu, 5 Mar 98 14:45:38 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id OAA10898; Thu, 5 Mar 1998 14:37:08 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id OAA09160; Thu, 5 Mar 1998 14:37:03 +1000 (EST) Message-Id: <199803050437.OAA09160@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Mike Smith cc: current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) References: <199803050357.TAA24001@dingo.cdrom.com> In-Reply-To: <199803050357.TAA24001@dingo.cdrom.com> from Mike Smith at "Wed, 04 Mar 1998 19:57:39 -0800" Date: Thu, 05 Mar 1998 14:37:03 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 4th March 1998, Mike Smith wrote: >> I didn't do enough investigation to even guess at the cause. I looked in >> the XFree86 server code for interrupt disabling but found nothing >> interesting. > >Does the server disable interrupts for extended periods of time? If it does, I couldn't find where. >> I was wondering though if any PCI experts knew if a PCI video card could >> starve the PCI-ISA bridge of cycles. Any experts out there? > >It's quite possible; it would depend on the PCI latency timer settings, >but generally the latency provided for there is only of the order of a >few microseconds. So, how would I print these latency timer settings from FreeBSD? Would I just get a meaningless jumble of numbers anyway? ;-) >I would be more interested in knowing whether the X >server did interrupt-related things specific to the Matrox driver... This was my first thought. I couldn't find any place that it disabled interrupts. There were routines to fiddle processor interrupts but I could find no code that called them. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message