From owner-freebsd-stable@FreeBSD.ORG Wed Mar 18 14:30:26 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 0BE49106566B for ; Wed, 18 Mar 2009 14:30:26 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.38]) by mx1.freebsd.org (Postfix) with ESMTP id 721098FC16 for ; Wed, 18 Mar 2009 14:30:25 +0000 (UTC) (envelope-from amarat@ksu.ru) X-IronPort-AV: E=Sophos;i="4.38,384,1233522000"; d="scan'208";a="2389646" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 18 Mar 2009 17:30:23 +0300 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n2IESUKt018945; Wed, 18 Mar 2009 14:28:40 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n2IEToHp043716; Wed, 18 Mar 2009 17:29:51 +0300 (MSK) (envelope-from amarat@ksu.ru) Message-ID: <49C1055E.7000303@ksu.ru> Date: Wed, 18 Mar 2009 17:29:50 +0300 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.19) Gecko/20090124 SeaMonkey/1.1.14 MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: ns@got2get.net, freebsd-stable@freebsd.org 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: Wed, 18 Mar 2009 14:30:26 -0000 Pete French wrote: >> 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 > > I (still) have the same problem on my MSI Platinum .... and having re-read > all of those threads in case I missed somehting, there still isn't a > solution there. All the suggested ones (using 'Linux" as ACPI name, moving > com interrupt ports, disabling onboard ether) are reported as failing > after a few days. Luckily I have a colleague who can reboot the remote > machine, and that has been my solution - but it is not really workable > long term. > > (actually this has reminded me to check dmesg, and it seems I need to > reboot this machine due to an interrupt storm right now). > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > did you try to make a kernel with KDB and DDB? DEBUG-kernel? it seems that turning off optimization and place a debugging stuff in kernel solved my problem. -- SY, marat