Red Hat Bugzilla – Bug 487875
possible HPET instability on Thinkpad X200
Last modified: 2009-12-18 03:55:52 EST
Description of problem:
In the past week on Fedora 10 with nightly yum updates I started seeing GNOME input/focus misbehaviors which I eventually found in .xsession-errors listed as an error of "last_focus_time" going backwards.
Changing current_clocksource from hpet to acpi_pm immediately stopped this behavior and I have not seen any additional problems.
Version-Release number of selected component (if applicable):
xorg-x11-drv-i810-2.5.0-4.fc10.x86_64 (using intel driver)
Also using iwlagn from kernel.
I am not sure if this happened the first time I rebooted with the new kernel, or if it required a combination of other recent packages (such as Xorg) to manifest.
Steps to Reproduce:
1. with a Thinkpad X200 up to date with repo mirror as of 27 Feb 2009
2. reboot and use normal cpu frequency control for laptops, etc.
3. run a GNOME session with metacity window manager and no compiz
4. start interacting with multiple windows using focus-follows-mouse
5. make sure kernel clocksource is hpet
(I used the fedora repo mirror at mirrors.kernel.org for my 27 Feb 2009 update)
Multiple times per hours (sometimes only seconds apart) you lose the ability to click on anything or move focus to a window, even though you can still move the mouse cursor around the screen. These last_focus_time comparison errors show up in the .xsession-errors file, intermingled with other messages that may be unrelated.
The user input is never disrupted.
The failure seems unrelated to the specific combination of X apps, happening even with just basic gnome-panel interactions at the beginning of a session. It may be more repeatable with frequent task switching between a web browser, xterms, etc. I do not know if a similar error can be manifested without using focus-follows-mouse policy in metacity or with another window manager. However no new metacity package has been released in correlation with this bug appearing (at least according to the metacity RPM changelog).
You can usually recover the focus and control via hot-keys to change virtual desktops. Sometimes, the only recovery is to switch to another VT and run metacity --replace to force things to reset.
Can you isolate the problem by booting older kernels and seeing if the problem happens on those? The two previous kernels should be available on the boot menu.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.