Date: Wed, 27 May 2009 14:13:57 -0500 From: David Kelly <dkelly@hiwaay.net> To: Andrew Gould <andrewlylegould@gmail.com> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: interrupt storm on irq 10 Message-ID: <20090527191357.GD9937@Grumpy.DynDNS.org> In-Reply-To: <d356c5630905271051v67e7bc4cy8b7a3371452e0b52@mail.gmail.com> References: <d356c5630905271051v67e7bc4cy8b7a3371452e0b52@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 27, 2009 at 12:51:45PM -0500, Andrew Gould wrote: [...] > Are interrupt storms a problem? Do I need to worry about them? If > so, is there anything I can do about them? Have run across interrupt storms for the first time myself last night. Am thinking they are from interrupt sources that interrupt handlers do not fully support. So the interrupt is not being serviced and is repeatedly being invoked. Probably PCI doesn't behave the same as much simpler embedded hardware that I am used to, but the above is what an interrupt storm looks like on simple embedded hardware. My source of interrupt storms was caused by a bad SATA cable. Installed a new VIA 6421-based SATA card (selected because it was only $15) and two new hard drives for the purpose of copying files off two older drives. New drives were detected but ad4 did not work when ad6 did. Swapped drives and the other drive on ad6 worked. Thought the card was bad but decided to try swapping cables which fixed ad4 and broke ad6. Ergo, bad cable. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090527191357.GD9937>