From owner-freebsd-current Wed Mar 4 22:16:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11501 for freebsd-current-outgoing; Wed, 4 Mar 1998 22:16:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA11467 for ; Wed, 4 Mar 1998 22:16:00 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA19853; Wed, 4 Mar 1998 22:15:51 -0800 Date: Wed, 4 Mar 1998 22:15:51 -0800 (PST) From: Brian Handy To: Nate Williams Cc: shimon@simon-shapiro.org, current@FreeBSD.ORG, Mike Smith Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) In-Reply-To: <199803050530.WAA16531@mt.sri.com> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > I can tell you that uniquivocally XFree86 causes this to happen. >... >> >> I am guessing it is something to do with the S3 chip. > >But I didn't change boards when I changed X servers. XFree86 caused >them, XIG didn't. The hardware was exactly the same, the only >difference was the Xserver. I have two boxes running Xig: One is a P5-133, the other is a PII-300. I just rummaged through the logs back unto creation, and neither show the dreaded sio overflow. (I complained about this a couple of years back. Somebody accused me of pushing my serial port too hard or something. My serial mouse was triggering the overflows. :-) Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message