From owner-freebsd-current Wed Mar 4 21:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02892 for freebsd-current-outgoing; Wed, 4 Mar 1998 21:20:43 -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 VAA02837 for ; Wed, 4 Mar 1998 21:20:33 -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 WAA19243; Wed, 4 Mar 1998 22:20:19 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA16381; Wed, 4 Mar 1998 22:20:16 -0700 Date: Wed, 4 Mar 1998 22:20:16 -0700 Message-Id: <199803050520.WAA16381@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: shimon@simon-shapiro.org Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) In-Reply-To: References: <199803050248.SAA23631@dingo.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message