From: Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Johannes Engel <j-engel-Mmb7MZpHnFY@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] EC Burst
Date: Fri, 9 Dec 2005 17:57:52 -0500 [thread overview]
Message-ID: <20051209225752.GF24272@redhat.com> (raw)
In-Reply-To: <43993D26.8060700-Mmb7MZpHnFY@public.gmane.org>
On Fri, Dec 09, 2005 at 09:15:34AM +0100, Johannes Engel wrote:
> Hi Len!
>
> Asking the developers at SuSE about my problem they sent me to you. So
> here I am. :)
> With the standard kernel my laptop delays the recognition of ACPI events
> seemingly using a queue of length 8. I found a patch some weeks ago
> which corrects that problem. If it can help others, too, maybe you can
> put it to the mainline. You will find details under
> http://bugzilla.kernel.org/show_bug.cgi?id=5713.
FWIW, we've had a number of Fedora users reporting similar problems
(Things like battery status applets not updating and the like).
Though we've got the upstream default of ec burst being disabled there.
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-09 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 8:15 [PATCH] EC Burst Johannes Engel
[not found] ` <43993D26.8060700-Mmb7MZpHnFY@public.gmane.org>
2005-12-09 22:57 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-10 2:48 Brown, Len
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=20051209225752.GF24272@redhat.com \
--to=davej-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=j-engel-Mmb7MZpHnFY@public.gmane.org \
--cc=len.brown-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