Description of problem: 2.6.31.5-127 worked after install. Upgrade to 2.6.31.9-174 touchpad gets slower over 3-4 sec and stops responding. Version-Release number of selected component (if applicable): see above How reproducible: 100% Steps to Reproduce: 1.login using GNOME 2. 3. Actual results: 2000-2500 int/sec on acpi int, no touchpad response Expected results: touchpad controls cursor Additional info:see total hardware information from 2.6.31.5 (working) boot http://www.tmr.com/~davidsen/Private/rw3-HWinfo/
Have tried all upgrades up to and including 2.6.31.12-174.2.19 and this is still unusable. With latest kernel 10-12 seconds of touchpad use will move the cursor a pixel or two, but not be remotely useful. Note: 2.6.33-rc6 has working touchpad again, this is something messed up in Fedora recently (since 2.6.31.5). System is old and slow but we have a lot of them around.
A full dmesg and lspci -v are usually useful in cases of kernel bugs. Also your config for the vanilla kernel I understand you're using.
The full information for the working (2.6.31.5), latest non-working (2.6.31.12-174.2.19), and recent kernel.org development kernel are at http://www.tmr.com/~davidsen/Private/rw3/ in standard HWinfo format. The comments indicate some information on the three generated 2/18/2010. The 2.6.31.12-174.2.19 also has the config file installed with the kernel.
First of all, congrats on the files provided, level of detail and thoroughness. That's the good news. Bad news is I see the exact ID and all the rest in the two dmesg's (working and not-working), so my guess is it's the Synaptics driver that doesn't want to play nice with the latest Fedora kernels. Speaking of which, has the driver been updated recently?
Short of trying to find the source for old kernels, I can't say. I just don't have that info. If you grep for serio in the dmesg you can see what fails, but I don't know that it moves us closer to a solution. Hopefully someone would be running the same kernel on a laptop and be able to provide some useful information from their logs. I'm going to try the most recent rc over the weekend, just to see if it behaves better. I didn't see a newer kernel in updates-testing the last time I looked. I will update HWinfo to look in /boot for a config matching the running kernel, and copy it if so.
You might wanna try a kernel from koji and/or stop in #fedora-kernel on IRC (chances are I might be there as jeff_hann), maybe something will come out of this. Best of luck.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.