Date: Sat, 16 Nov 1996 08:00:04 -0800 (PST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: Re: kern/2017: stray irq Message-ID: <199611161600.IAA04042@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/2017; it has been noted by GNATS. From: J Wunsch <j@uriah.heep.sax.de> To: ah@alvman.RoBIN.de Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/2017: stray irq Date: Sat, 16 Nov 1996 16:46:00 +0100 (MET) As Andreas Haakh wrote: > Nov 15 10:15:01 barney /kernel: stray irq 15 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 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. > As You can see there is no device assigned to this irq-channel. Of course. :) They weren't `stray' by definition otherwise (but instead, a driver like wdc1 that has no concern with them would get the IRQs). > >Fix: > > Unknown Fix your hardware. Or live with the warnings. As long as everything else continues to work, they are nothing to worry much about. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611161600.IAA04042>