From: Hans de Goede <hdegoede@redhat.com>
To: Tibor Billes <tbilles@gmx.com>, Zhang Rui <rui.zhang@intel.com>,
Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Aaron Lu <aaron.lu@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Possible regression: sluggish inputs
Date: Sat, 03 May 2014 10:00:38 +0200 [thread overview]
Message-ID: <5364A226.4040900@redhat.com> (raw)
In-Reply-To: <trinity-3958d3e8-f087-4d8d-b313-b1318b5f54f9-1399050238997@msvc011>
Hi,
On 05/02/2014 07:03 PM, Tibor Billes wrote:
> Hi,
>
> I've upgraded my 3.13.5 kernel to 3.14.2 and I noticed that sometimes my mouse is slow to react.
> By slow I mean the pointer on the screen doesn't follow its path smoothly, instead it jumps from one
> position to the next at only a few jumps per second rate. Like if the kernel could only process 2 or 3
> position updates per second from the mouse. (As far as I can tell, the machine is in idle.)
> After experimenting a little I found out that the keyboard is also affected. Keystrokes are delayed,
> letters appearing in bursts. This behaviour (for both the mouse and the keyboard) lasts only for a
> couple of seconds, then it suddenly goes away and everything works as expected. I also noticed that
> this behaviour shows up after I haven't touched the mouse or the keyboard for short time (around
> 10 seconds, but I didn't measure this).
What I think is happening is that you've auto screen dimming on inactivity enabled in your
desktop environment settings, which results in trying to change the backlight after 10 seconds
of inactivity. Then the intel video driver likely directly writes to
/sys/class/backlight/acpi_video0/brightness and gets stuck in that write because the acpi code
gets stuck.
I've seen this happen occasionally on my E6430 both with and without the patch the bisect
points too. I can trigger it by pressing brightness up / down as fast as I can. Likely the
dimming on inactivity code is doing a much better job at sending brightness change commands
as fast as possible, making it easier to trigger this.
As for the commit you've bisected it too, it may be that that subtly changes things to make
the problem easier to trigger, but I distinctly remember having the same issue before I wrote
that patch.
Have you tried updating your BIOS ?
Regards,
Hans
next prev parent reply other threads:[~2014-05-03 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 17:03 Possible regression: sluggish inputs Tibor Billes
2014-05-03 8:00 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-03 17:38 tbilles
2014-05-03 18:14 ` Hans de Goede
2014-05-12 13:26 tbilles
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=5364A226.4040900@redhat.com \
--to=hdegoede@redhat.com \
--cc=aaron.lu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=tbilles@gmx.com \
/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;
as well as URLs for NNTP newsgroup(s).