From owner-freebsd-questions@FreeBSD.ORG Wed May 27 19:30:28 2009 Return-Path: Delivered-To: FreeBSD-Questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 153D5106567F for ; Wed, 27 May 2009 19:30:28 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2FFD08FC25 for ; Wed, 27 May 2009 19:30:26 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3) with ESMTP id n4RJUKaa054408; Wed, 27 May 2009 21:30:20 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.3/Submit) with ESMTP id n4RJUJfs054405; Wed, 27 May 2009 21:30:19 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 27 May 2009 21:30:19 +0200 (CEST) From: Wojciech Puchar To: FreeBSD Questions Mailing List In-Reply-To: <20090527191357.GD9937@Grumpy.DynDNS.org> Message-ID: References: <20090527191357.GD9937@Grumpy.DynDNS.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Andrew Gould Subject: Re: interrupt storm on irq 10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 19:30:28 -0000 > 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. > anyway very strange controller reaction to that case. i can hardly believe the way cable have to be broken to produce interrupt storm. maybe this way: controller sends message to drive, bad cable causes CRC errors, hard drive reacts with some message for that, interrupt is generated, driver in case of detected transmission problem instantly resends last commands, situation repeats. But it's contrary to what you said that "interrupt storm" are lots of interrupts that are not serviced by any driver. I'm not telling that you are wrong that cable produced this, but i can't find any explanation for that. any idea?