From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karol Kozimor Subject: Re: Dell laptop problem with acpid Date: Wed, 17 Nov 2004 12:18:52 +0100 Message-ID: <20041117111852.GB8177@hell.org.pl> References: <3ACA40606221794F80A5670F0AF15F84041AC092@pdsmsx403> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Return-path: Content-Disposition: inline In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC092@pdsmsx403> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Yu, Luming" Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, "Fu, Michael" List-Id: linux-acpi@vger.kernel.org Thus wrote Yu, Luming: > >There is a regression in event handling visible on some > >hardware (Maxdata > >pro8000x here, but there's been other reports, even on this ml). > >Basically, the ACPI SCI seems to be raised correctly according to > >/proc/interrupts, but the events are reported erratically or > >not reported > >at all. As a sidenote: kacpid doesn't spin when that happens. > >Any hints > >on how to debug this further? > First, check Notify op is existed in AML method, > then, verify acpi_*_notify are installed. > Intuitively, Notify op was executed conditionally. Ugh, it's a regression, it worked well with 2.6.7 but works erratically on 2.6.9. I doubt the AML code has changed since then. Additionally, it also affects standard features like a FF power button. Best regards, -- Karol 'sziwan' Kozimor sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8