From owner-freebsd-acpi@FreeBSD.ORG  Mon May 17 11:12:54 2004
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 83E5B16A4CE
	for <freebsd-acpi@FreeBSD.org>; Mon, 17 May 2004 11:12:54 -0700 (PDT)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 25EE543D54
	for <freebsd-acpi@FreeBSD.org>; Mon, 17 May 2004 11:12:53 -0700 (PDT)
	(envelope-from nate@root.org)
Received: (qmail 20083 invoked by uid 1000); 17 May 2004 18:12:53 -0000
Date: Mon, 17 May 2004 11:12:53 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Kevin Oberman <oberman@es.net>
In-Reply-To: <20040514164013.0CE795D0D@ptavv.es.net>
Message-ID: <20040517111058.D20078@root.org>
References: <20040514164013.0CE795D0D@ptavv.es.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-acpi@FreeBSD.org
Subject: Re: ACPI interrupt storms during shutdown
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 May 2004 18:12:54 -0000

On Fri, 14 May 2004, Kevin Oberman wrote:
> For about two week my laptop (IBM T30) has started reporting stray
> interrupts from acpi0 or an interrupt storm on IRQ9. This is really not
> a problem as it happens right at the end of the shutdown after disks are
> synced and seems to start as the standard background processes are
> terminated. It usually is reported after vnlru and bufdaemon terminate,
> but before syncer terminates. (It's very hard to tell much as the screen
> blanks immediately.) It may be starting as bufdaemon is terminated.
>
> This is not causing me any problems, but I wanted to mention it as it
> certainly does not seem right.

Yep, I've got that too.  What happens is a series of GPEs occur during the
AcpiTerminate() process.  I'll be changing the ACPI shutdown process after
I do some more debugging of the source of the GPEs.  The interrupt storm
check is probably too sensitive in some non-runtime cases.

This is on the ACPI TODO list:
http://www.root.org/~nate/freebsd/acpi-todo.html

-Nate