From owner-freebsd-doc Sat Aug 12 16: 0:12 2000 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 43DCA37BD73 for ; Sat, 12 Aug 2000 16:00:09 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id QAA46556; Sat, 12 Aug 2000 16:00:09 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sat, 12 Aug 2000 16:00:09 -0700 (PDT) Message-Id: <200008122300.QAA46556@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Bruce Evans Subject: Re: kern/17774: stray irq7 Reply-To: Bruce Evans Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/17774; it has been noted by GNATS. From: Bruce Evans To: Johan Karlsson Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/17774: stray irq7 Date: Sun, 13 Aug 2000 08:55:04 +1000 (EST) On Fri, 11 Aug 2000, Johan Karlsson wrote: > I suggest the following is added to the faq The fwa? :-). > ============= > Q: What does 'stray irq' mean? > A: Stray irq are interupts from some hardware that do not have > a driver assigned to it. J Wunsch writes in a response to a PR No, they are mostly from hardware that removes its interrupt request in the middle of the interrupt request acknowledge cycle. FreeBSD's interrupt handling (toggling the PIC masks at a critical time) probably amplifies this problem. Assigning a driver can "fix" the problem by breaking detection of it. The correct fix is to detect the stray interrupts caused by interrupt timing glitches and decide what to do about them (whatever is done, it shouldn't involve printing a faq magnet). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message