Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA1302 ; Tue, 23 Feb 93 14:34:27 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!swrinde!gatech!enterpoop.mit.edu!thunder.mcrcim.mcgill.edu!homer.cs.mcgill.ca!storm
From: storm@cs.mcgill.ca (Marc Wandschneider)
Subject: Re: [386BSD] I keep getting silo overflow
Message-ID: <C2GDyw.FFs@cs.mcgill.ca>
Sender: news@cs.mcgill.ca (Netnews Administrator)
Organization: SOCS - Mcgill University, Montreal, Canada
References: <1993Feb11.135806.24559@njitgw.njit.edu> <1993Feb11.204402.16005@coe.montana.edu> <1993Feb11.223329.13043@netcom.com>
Date: Sun, 14 Feb 1993 19:25:43 GMT
Lines: 22
In article <1993Feb11.223329.13043@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
>That is one way to fix the problem another way which is the root
>of all this problems is that the com driver is locking out interrupts
>for a duration of sometimes hundreds of instructions. Also,
>when you do disk access the com driver never gets a chance to
>respond to interrupts.
What really freaks me out is that I get the silo overflows on com1
errors quite a bit when I am downloading on com2, which has a fifo.
NO Idea what the heck causes that, but it's rather bizarre!
ToodlepiP!
Marc 'em.
--
storm@cs.mcgill.ca McGill P.O.W Camp "Oh crap---It's not
Marc Wandschneider Montreal, CANADA random enough"
Any opinions expressed are not mine, but those of the Demon Lord
Yeegeheeegenogohugu who possessed me whilst I munched on Raisin Bran.