From owner-freebsd-stable@FreeBSD.ORG Wed Mar 18 13:01:07 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 D24B3106564A for ; Wed, 18 Mar 2009 13:01:07 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 983378FC14 for ; Wed, 18 Mar 2009 13:01:07 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LjvOG-000NVv-EX; Wed, 18 Mar 2009 13:01:00 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LjvOF-000Biu-IM; Wed, 18 Mar 2009 13:00:59 +0000 To: amarat@ksu.ru, ns@got2get.net In-Reply-To: <49BFD57C.5010301@ksu.ru> Message-Id: From: Pete French Date: Wed, 18 Mar 2009 13:00:59 +0000 Cc: 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 13:01:08 -0000 > 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.