From owner-freebsd-stable Mon Oct 9 14:37: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 4FC8E37B66C for ; Mon, 9 Oct 2000 14:37:03 -0700 (PDT) Received: from [24.217.130.214] (HELO dave.uhring.com) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.3.2) with ESMTP id 1245049; Mon, 09 Oct 2000 17:37:02 -0400 Received: from localhost (localhost [127.0.0.1]) by dave.uhring.com (8.8.8/8.8.8) with ESMTP id QAA00270; Mon, 9 Oct 2000 16:34:38 -0500 (CDT) Date: Mon, 9 Oct 2000 16:34:34 -0500 (CDT) From: Dave Uhring X-Sender: duhring@dave.uhring.com To: Gary Kline Cc: Gerhard Sittig , freebsd-stable@FreeBSD.ORG Subject: Re: the ``stray irq 7'' is back In-Reply-To: <20001009140940.A17746@tao.thought.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The usual reason for getting these spurious IRQ's is that the equipment is not properly connected, leaving the Centronics ACK pin floating. A floating input can take just about any voltage level, depending on ambient EMI noise. When the pin voltage floats (damn if I remember the exact logic level anymore) the IRQ is triggered. Same thing happened with a firewall box I had on IRQ 15 with no secondary IDE drives attached. The real fun with these spurious IRQ's happens when you are doing a humongous download and one packet out of 5000 gets corrupted by an overflow on your NIC's buffer because the CPU was busy dealing with the IRQ. The NIC drivers apparently do not check for underflow/overflow conditions. Then when you attempt to unzip your tarball, you get the message 'header not found...' I had that happen when I was trying to get the StarOffice-5.1a package from Sun - 69MB shot to hell. Dave On Mon, 9 Oct 2000, Gary Kline wrote: > Date: Mon, 9 Oct 2000 14:09:40 -0700 > From: Gary Kline > To: Gerhard Sittig > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: the ``stray irq 7'' is back > > On Mon, Oct 09, 2000 at 07:53:42PM +0200, Gerhard Sittig wrote: > > On Sun, Oct 08, 2000 at 21:31 -0700, Doug White wrote: > > > > > > Gary, your motherboard is cursed. I have one too; live with it. > > > > > > Stray IRQ 7s are _normal_. > > > > Jumping in late, but ... > > > > I know "stray irqs" from when hardware is "disabled" or you have > > hardware in the machine the OS doesn't support and thus doesn't > > register drivers or resources for. That's when the events end up > > in the "stray" (i.e. "unexpected since not caused by me") > > handler. Sound cards were known to cause this some five to eight > > years ago. Some irq7 got triggered "by chance" without the lpt > > driver thinking it has done it or some such. And I've seem > > machines with crackling sound in the speaker boxes whenever print > > jobs via lpt were executed. It must have been some kind of cross > > over noise, maybe not enough or defective separation of > > electrical paths or something. > > > > After cleaning both ends of the cable, it's possible that > one end or the other (or both) weren't reconnected > correctly; thanks for this information. When something as > mundane as this suddenly quits after several years, > I'm ready to believe anything! > > gary > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message