From owner-freebsd-stable Mon Oct 9 14: 9:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id 81B5337B66C for ; Mon, 9 Oct 2000 14:09:56 -0700 (PDT) Received: from thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id OAA14167; Mon, 9 Oct 2000 14:09:54 -0700 (PDT) Received: (from kline@localhost) by thought.org (8.11.0/8.11.0) id e99L9fQ17813; Mon, 9 Oct 2000 14:09:41 -0700 (PDT) (envelope-from kline) 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 Message-ID: <20001009140940.A17746@tao.thought.org> References: <200010080018.e980IUY02824@thought.org> <20001009195342.U31338@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20001009195342.U31338@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Mon, Oct 09, 2000 at 07:53:42PM +0200 X-Organization: Thought Unlimited. Public service Unix since 1986. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message