From owner-freebsd-current Wed Mar 4 21:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06043 for freebsd-current-outgoing; Wed, 4 Mar 1998 21:34:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA06036 for ; Wed, 4 Mar 1998 21:34:27 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 20269 invoked by uid 1000); 5 Mar 1998 05:34:27 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-021598 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803050520.WAA16381@mt.sri.com> Date: Wed, 04 Mar 1998 21:34:26 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Nate Williams Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Cc: current@FreeBSD.ORG, Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Mar-98 Nate Williams wrote: >> > However the driver has no say in the matter when _someone_else_ >> > disables interrupts for a long period of time, or when the hardware >> > fails to deliver them in the first place. >> >> Unless I misunderstand something, the driver should get interrupts >> delivered, unless another part of the kernel is in spltty(), or another >> spl >> which masks spltty. There should not be all that many of those, and >> they >> should be considered carefully. > > I can tell you that uniquivocally XFree86 causes this to happen. Why, I > don't know, but it's definitely X related. If I don't use X and the > machine gets the same traffic, I get the messages. If I switch from > XFree8 to XIG, the messages go away. > > What is causing the interrupts to go away, I don't know, but it might be > syscons or something. I'm not switching vty's, and neither am I hitting > the caps-lock or causing the LED's to switch. > > But, it occurs none-the-less. I am guessing it is something to do with the S3 chip. The Mach64 I finally pulled out was much worse. It would die/kill serial ports. I think the problem is there and in the FAST_INTR stuff. Now I am going to get myself in trouble all over again :-) Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message