From: Pavel Troller <patrol-FIBU9iiavH4@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: 2.6.13-rc4: /proc/acpi/event doesn't report any events
Date: Sat, 30 Jul 2005 21:03:42 +0200 [thread overview]
Message-ID: <20050730190341.GA4108@miro.sinus.cz> (raw)
Hi!
It's exactly as the subject says - /proc/acpi/event is totally dummy, it
doesn't output any event, which it did before.
I've tried buttons and ac adaptor removal/insertion.
I'm really unhappy. I tried to locate the problem, looked at the patch and
reviewed all the acpi stuff and found just fixes of well-known -rc3 problems.
acpi/drivers/event.c is untouched from May. I really don't know what's
happening there.
Otherwise the ACPI susbystem works well including S3/S4, no problems,
no unobvious messages in dmesg.
Any help ?
With regards, Pavel Troller
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-30 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 19:03 Pavel Troller [this message]
[not found] ` <20050730190341.GA4108-xk5YvUdtsdomyzK0JynY2A@public.gmane.org>
2005-07-30 20:00 ` 2.6.13-rc4: /proc/acpi/event doesn't report any events Sanjoy Mahajan
[not found] ` <E1DyxVU-000202-00-KmINTRm7+bkRAIupTkoUWTYRy0cijUJx@public.gmane.org>
2005-07-31 5:25 ` 2.6.13-rc4: /proc/acpi/event doesn't report any events - more debugging Pavel Troller
[not found] ` <20050731052525.GA4649-hxMeMO63rIAUgFT2KJq8fg@public.gmane.org>
2005-07-31 7:13 ` 2.6.13-rc4: /proc/acpi/event doesn't report any events - SOLVED (ec_polling needed) Pavel Troller
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=20050730190341.GA4108@miro.sinus.cz \
--to=patrol-fibu9iiavh4@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.