Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Mar 1998 22:14:42 +1030
From:      Matthew Thyer <thyerm@camtech.net.au>
To:        shimon@simon-shapiro.org
Cc:        Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG, Mike Smith <mike@smith.net.au>
Subject:   Re: silo overflows (Was Re: 3.0-RELEASE?)
Message-ID:  <350527AA.3139AD63@camtech.net.au>
References:  <XFMail.980304213426.shimon@simon-shapiro.org>

next in thread | previous in thread | raw e-mail | index | archive | help
My silo overflows seem to have disappeared.

Unfortunately I've just changed 4 things at once!

- I recompiled XFree86 3.3.1 (NOT 3.3.2) recently (whilst running a
  system built from CTM src-cur.3261 [Feb 23] sources)

- I've just made the world at CTM src-cur.3281 [8 Mar 1998 23:07:21 -0800
(PST)]

- I've turned on SoftUpdates on all but the root fs.

- And I've taken Option "pci_retry" out of my /etc/XF86Config file. **

Did anyone change anything that could stop silo overflows between
CTM src-cur.3261 and CTM src-cur.3281 ?

** Personally I think this is the key but have not the time to try
it now (ie I am downloading XF86 3.3.2 in an xterm and thus cant
restart X for a while).

Simon Shapiro wrote:
> 
> On 05-Mar-98 Nate Williams wrote:
> >> > However the driver has no say in the matter when _someone_else_
> >> > disables interrupts for a long period of time, or when the hardware
> >> > fails to deliver them in the first place.
> >>
> >> Unless I misunderstand something, the driver should get interrupts
> >> delivered, unless another part of the kernel is in spltty(), or another
> >> spl
> >> which masks spltty.  There should not be all that many of those, and
> >> they
> >> should be considered carefully.
> >
> > I can tell you that uniquivocally XFree86 causes this to happen.  Why, I
> > don't know, but it's definitely X related.  If I don't use X and the
> > machine gets the same traffic, I get the messages.  If I switch from
> > XFree8 to XIG, the messages go away.
> >
> > What is causing the interrupts to go away, I don't know, but it might be
> > syscons or something.  I'm not switching vty's, and neither am I hitting
> > the caps-lock or causing the LED's to switch.
> >
> > But, it occurs none-the-less.
> 
> I am guessing it is something to do with the S3 chip.  The Mach64 I finally
> pulled out was much worse.  It would die/kill serial ports.  I think the
> problem is there and in the FAST_INTR stuff.  Now I am going to get myself
> in trouble all over again :-)
> 
> Simon
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

-- 
/=====================================================================\
|Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au|
\=====================================================================/
"If it is true that our Universe has a zero net value for all conserved
quantities, then it may simply be a fluctuation of the vacuum of some
larger space in which our Universe is imbedded. In answer to the
question of why it happened, I offer the modest proposal that our
Universe is simply one of those things which happen from time to time."
 E. P. Tryon   from "Nature" Vol.246 Dec.14, 1973

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?350527AA.3139AD63>