From owner-freebsd-current Wed Dec 2 17:14:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03751 for freebsd-current-outgoing; Wed, 2 Dec 1998 17:14:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03744 for ; Wed, 2 Dec 1998 17:14:45 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA28540; Wed, 2 Dec 1998 18:14:10 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA10483; Wed, 2 Dec 1998 18:14:09 -0700 Date: Wed, 2 Dec 1998 18:14:09 -0700 Message-Id: <199812030114.SAA10483@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: David Dawes , Peter Jeremy , current@FreeBSD.ORG Subject: Re: sio breakage In-Reply-To: <199812030107.RAA01213@dingo.cdrom.com> References: <19981203115222.A3051@rf900.physics.usyd.edu.au> <199812030107.RAA01213@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >I agree. And whilst I haven't checked why, XFree86 does appear to > > >disable interrupts at times. > > > > I agree too, but it does disable interrupts when probing for fixed pixel > > clocks (which is mostly only done for obsolete hardware), and sometimes > > when programming PLLs. If someone has a better way of handling time > > critical thing like this (preferably in a portable way), please let me > > know. I'd love to dump our disable interrupt code. > > I get the impression from this though that you only do interrupt > disables when probing or changing video modes, is that correct? I get that impression as well. > The entire train of angst here is descended from percieved problems in > interrupt delivery during normal operation; if you're only disabling > interrupts during startup then this prettymuch exonerates the X server. Except that I can say with assurance that at least older versions of the XFree86 server *seem* to be disabling interrupts for long periods, or at least calling code that disables interrupts. When I switched to the XIG (XInside at the time) server, all of my serial overflows went away. That was the *only* configuration difference. To be sure, I even re-configured the XFree86 server and the problem re-occurred. Swapped it back and it went away. Note, this was about a year ago, maybe more so it may have changed. (The box in question has a S3 928 card in it..) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message