From owner-freebsd-questions Wed Mar 12 16:54:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA23052 for questions-outgoing; Wed, 12 Mar 1997 16:54:47 -0800 (PST) Received: from cia-g.com (mail@maslow.cia-g.com [206.206.162.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23046 for ; Wed, 12 Mar 1997 16:54:44 -0800 (PST) Received: (from mail@localhost) by cia-g.com (8.8.5/8.7.3) id RAA13254; Wed, 12 Mar 1997 17:54:39 -0700 (MST) Received: from maslow.cia-g.com(206.206.162.5) by maslow.cia-g.com via smap (V1.3) id sma013249; Wed Mar 12 17:54:20 1997 Date: Wed, 12 Mar 1997 17:54:20 -0700 (MST) From: Joel Yancey To: Keith Leonard cc: questions@freebsd.org Subject: Re: Silo overflow again?? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Mar 1997, Keith Leonard wrote: > Howdy, > > Sorry to bother again - but I've just kicked started the 'old' laptop > again and again with the 'kernel/silo overflow sio0...'. The old machine > uses a 16450 UART and I'm using an intel 14400 fax/modem (external). > > Other than shaking our heads and saying 'tsk - tsk' is there any practical > advice on how to correct this situation. I've tried setting everything to > 9600 baud but still get the message - so maybe I'm missing something. > > Any help would be appreciated I had this problem once as well, except it was with a 16550A UART. Silo OverFlow Means that there is Something wrong happening with your Interrupt Processor, Which could mean a Conflict (thats how i solved mine), or a Bad UART. Regards, Joel Yancey Python@cia-g.com