From owner-freebsd-current@FreeBSD.ORG Tue Jul 6 04:44:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C220C16A4CE; Tue, 6 Jul 2004 04:44:46 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65A6F43D1D; Tue, 6 Jul 2004 04:44:46 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-187-74.dsl.snfc21.pacbell.net [64.171.187.74]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i664iira010616; Mon, 5 Jul 2004 21:44:45 -0700 Message-ID: <40EA2D5C.4090006@root.org> Date: Mon, 05 Jul 2004 21:41:00 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Bowman References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "'acpi@freebsd.org'" cc: "'current@freebsd.org'" Subject: Re: acpi interrupt storm when disabling, IPI hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2004 04:44:46 -0000 Don Bowman wrote: > When i run 'acpiconf -d', i get an interrupt storm on irq9... > vmstat -i shows ~1000/s. > > Jun 15 13:41:33 cdata kernel: Interrupt storm detected on "irq9: acpi0"; > throttling interrupt source > > when i try to re-enable, i get an error: > > # acpiconf -e > acpi0: interrupt handler already installed > ACPI-0210: *** Error: Unable to install System Control Interrupt > Handler, AE_ALREADY_EXISTS > acpiconf: enable failed: Device not configured > # > > System is a Supermicro X5DPE motherboard, dual 2.8GHz Xeon, > 533MHz FSB, Intel e7501 chipset. Some systems don't support legacy mode (acpi disabled). Others support legacy mode but don't support transition back to it after acpi has been enabled. In this case, it's likely the flags aren't set right for AcpiEnableSubsystem. I'll look into it. > The system will not boot 5.x if acpi is disabled. > It will run 4.x without trouble tho. What do you mean by "will not boot"? Hangs? Panics? More info is needed. -Nate