From owner-freebsd-bugs Fri Aug 11 12:10:10 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8927737C1BF for ; Fri, 11 Aug 2000 12:10:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA82457; Fri, 11 Aug 2000 12:10:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Fri, 11 Aug 2000 12:10:05 -0700 (PDT) Message-Id: <200008111910.MAA82457@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Johan Karlsson Subject: Re: kern/17774: stray irq7 Reply-To: Johan Karlsson Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/17774; it has been noted by GNATS. From: Johan Karlsson To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/17774: stray irq7 Date: Fri, 11 Aug 2000 21:10:44 +0200 Hi Every now and then a mail or PR pops up with this question. I search the FreeBSD web pages for info about this but did not find any, maybe I just missed it. I suggest the following is added to the faq ============= 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 "Stray IRQs are a known phenomenon. Obviously (if you think about it :), there's nothing the kernel could do about it. Unless you have misconfigured your kernel so there's no driver assigned to a device that actually issues IRQs, they are a sign of flakey hardware, often caused by glitches on an IRQ line." You have three choices: 1) Live with the warnings 2) Get a driver for the hardware into your kernel 3) Remove the hardware that generates the interrupts ============== The PR refered to is 2017 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=2017 /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message