From owner-freebsd-questions Sun Jun 18 18:11:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from new-smtp2.ihug.com.au (new-smtp2.ihug.com.au [203.109.250.28]) by hub.freebsd.org (Postfix) with ESMTP id C918C37B6CB for ; Sun, 18 Jun 2000 18:11:39 -0700 (PDT) (envelope-from john@jmv.com.au) Received: from [203.109.165.239] (p47-max66.syd.ihug.com.au [203.109.165.239]) by new-smtp2.ihug.com.au (8.9.3/8.9.3) with ESMTP id LAA10648 for ; Mon, 19 Jun 2000 11:11:33 +1000 X-Sender: john@millennium.e-boxen.com Message-Id: In-Reply-To: <20000618121752.A33022@mashed.turnip.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 19 Jun 2000 11:15:23 +1000 To: freebsd-questions@freebsd.org From: John Vender Subject: Re: serial port silo overflow errors Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had that problem with a Dell Dimension XPS T with 3.1 and 3.4 recently and was tearing my hair out until I found BSD News Article 185853 by Andy Smith in the archives which helped a lot. Apparently it's related to a IDE controller on some motherboard which uses DMA and if it's not turned on results in problems with things resulting in silo overflows. I had to also do the second suggestion, turn off legacy USB in the bios. The box still gets few silo overflows but a tiny fraction of what it was doing before. I didn't save the post, only printed it out, but the article ID should help you find it. If you can't I can type it in I guess :) Cheers...John Jonathan Vaughan wrote: >I am having silo overflow errors like >Jun 18 02:31:55 mashed /kernel: sio1: 1 more silo overflow (total 135) >whenever i download files over a dialup isp. > >My setup: >4.0-STABLE, as of june 16. Problem also occurred with 4.0-RELEASE >amd athlon 700 >abit ka7-100 >usr sportster external 33.6 >serial ports are 16550A. > >I have tried reducing my serial port speed to 57600, but this has no effect. >Looking at the archives, it seems this is a fairly common problem, but one >that's not resolved. Does anyone have any suggestions? > >Thanks in advance > >Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message