From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Fu,
Michael" <michael.fu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Dell laptop problem with acpid
Date: Wed, 17 Nov 2004 12:18:52 +0100 [thread overview]
Message-ID: <20041117111852.GB8177@hell.org.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041AC092@pdsmsx403>
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
next prev parent reply other threads:[~2004-11-17 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 11:09 Dell laptop problem with acpid Yu, Luming
2004-11-17 11:18 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 11:21 Yu, Luming
2004-11-17 1:13 Cederik de Leon
[not found] ` <b9768e82041116171321b8086f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-11-17 10:32 ` Karol Kozimor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041117111852.GB8177@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=michael.fu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox