From owner-freebsd-current Mon May 29 7:51: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from wendell.heistand.org (wendell.heistand.org [209.181.116.46]) by hub.freebsd.org (Postfix) with ESMTP id D5DF337BBDD for ; Mon, 29 May 2000 07:50:59 -0700 (PDT) (envelope-from heistand@heistand.org) Received: from heistand.org (localhost.heistand.org [127.0.0.1]) by wendell.heistand.org (Postfix) with ESMTP id 7EE891B242; Mon, 29 May 2000 08:50:51 -0600 (MDT) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: have a couple of problems. In-Reply-To: Your message of "Sun, 28 May 2000 19:34:02 PDT." <200005290234.TAA11414@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 May 2000 08:50:51 -0600 From: Steve Heistand Message-Id: <20000529145051.7EE891B242@wendell.heistand.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch fixes the problem with the overflow message and gets my connection speed back up. Which is good. Unfotunately my display is having problems. Not nearly as much as before but still noticable and a little annoying. steve > :Hi, > : > :ok so I am having a couple of problems. > : > :The first is that I get tons of "sio0: x more silo overflows" messages when I > :boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I > :re'cvs-upped. > : > :I can get rid of these by not booting an SMP kernel but then I get really > :freaky > :X stuff happening. My screen gets all wavy when there is a bunch of stuff > :being sent out of the video card. Which is really annoying and causes > :headaches. > : > :Anyone else having the X problem? I have seen mention and potential fixes for > :the > :silo overflow problems but it hasnt made it into the current source yet. > : > :thanks > : > :steve > : > :Steve Heistand > :heistand@heistand.org > > Steve, please try the patch that Bruce posted a few days ago and tell > us if that fixes your problem too. The patch will almost certainly go > in in some form, it hasn't yet only because I wanted a little time to > be able to trace out the interrupt path to make sure the patch was ok. > Steve Heistand heistand@heistand.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message