From: Maximilian Engelhardt <maxi@daemonizer.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [regression] display dimming is slow and laggy
Date: Tue, 17 Jun 2008 15:53:08 +0200 [thread overview]
Message-ID: <200806171553.12880.maxi@daemonizer.de> (raw)
In-Reply-To: <485702F7.6060704@shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On Tuesday 17 June 2008, Robert Hancock wrote:
> Maximilian Engelhardt wrote:
> > Hello,
> >
> > I'm using kernel 2.6.26-rc6 at the moment and with it dimming the display
> > is slow and laggy. Using kernel 2.6.25 doesn't show this problem.
> >
> > Here is a more detailed explanation:
> >
> > I'm dimming my display with the appropriate keys on my laptop (Fn +
> > right/left). Till kernel 2.6.25 this has worked without any problems. Now
> > I'm using 2.6.26-rc6 and using the keys the display is dimming much
> > slower and also laggy. By laggy I mean if I hit the keys for
> > increasing/decreasing brightness it starts dimming and when I release the
> > keys after some time it still continues dimming for some steps.
> >
> > My laptop is a Acer Travelmate 661lci and has an Intel 855 chipset.
> >
> > I'll attach my dmesg output, please tell me if you need any further
> > information.
>
> Think you forgot the dmesg.
Hm, I'm quite sure I did attach it. Here it is again:
http://bugzilla.kernel.org/show_bug.cgi?id=10919
> Are you seeing a "ACPI: EC: GPE storm
> detected, disabling EC GPE" message? See:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=10724
Yes, I see this message.
Maxi
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-17 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.bYtHs6zUqCWUnOriVTRy2wrCy7s@ifi.uio.no>
2008-06-17 0:19 ` [regression] display dimming is slow and laggy Robert Hancock
2008-06-17 13:53 ` Maximilian Engelhardt [this message]
2008-06-14 22:31 Maximilian Engelhardt
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=200806171553.12880.maxi@daemonizer.de \
--to=maxi@daemonizer.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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