From owner-freebsd-stable@FreeBSD.ORG Sun Mar 22 22:23:22 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 253EE106566B for ; Sun, 22 Mar 2009 22:23:22 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id EA6298FC17 for ; Sun, 22 Mar 2009 22:23:21 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LlW4f-00057w-0V for freebsd-stable@freebsd.org; Sun, 22 Mar 2009 15:23:21 -0700 Message-ID: <22651491.post@talk.nabble.com> Date: Sun, 22 Mar 2009 15:23:21 -0700 (PDT) From: Nicolais To: freebsd-stable@freebsd.org In-Reply-To: <49BFD57C.5010301@ksu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ns@got2get.net References: <22561413.post@talk.nabble.com> <49BFD57C.5010301@ksu.ru> Subject: Re: Crazy "interrupt storm detected" on atapci0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 22:23:22 -0000 Marat N.Afanasyev wrote: > > Nicolais wrote: >> Also - this was extracted from kenv: >> >> smbios.system.maker="MICRO-STAR INTERANTIONAL CO.,LTD" >> smbios.system.product="MS-7368" > > as I supposed in previous message your MB is MicroStar product. So I > insist that you read thread [1] in freebsd-stable named 'Interrupt > storm' started by Dan Langille > > [1] > http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047645.html > Hi Marat, Thank you for pointing this out. After posting I looked in more archives and found the same threads are you listed. I have now run with DDB and KDB more than 5 days, and the interrupt storms have ceased it seems. This is truly wonderful news, even though I don't really like the solution. I will leave the options on for now, but will continue to monitor the lists for better solutions. I would lie if I said I had not hoped a driver update would have solved the situation, but I guess that is coming sooner or later. Thanks again Best regards - Nicolai -- View this message in context: http://www.nabble.com/Crazy-%22interrupt-storm-detected%22-on-atapic0-tp22560101p22651491.html Sent from the freebsd-stable mailing list archive at Nabble.com.