Bug 223643

So for the sake of clarity, when you say "issue is apparent in the latest kernel
version also", are you saying you can reproduce the mouse lockups without the
madwifi driver loaded?

Also, please provide the output from the following command:

find /sys/devices/system/cpu/cpu0/cpufreq/ -type f -print -exec cat {} \;

The lockups existed before I installed madwifi.  I really didn't intend to
mention madwifi except to explain why I was booting to the previous version of
the kernel.  

[root@localhost ~]# find /sys/devices/system/cpu/cpu0/cpufreq/ -type f -print
-exec cat {} \;
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
700000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
700000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
700000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1000000 700000 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
userspace performance 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver
speedstep-smi
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
userspace
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus
0
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
1000000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
700000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
1000000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
700000
[root@localhost ~]# 

Damn, I thought I had a reproducer, but it appears to be something else, as the
brief freezes are happening with cpuspeed disabled as well. If you would, try
booting with 'cpufreq.debug=7' appended to your kernel line, and grab dmesg
output after one of these hangs. We might see something in there of use in
diagnosing what's going on...

Created attachment 146994 [details]
dmesg output when booted with cpufreq.debug=7

As requested, I booted the kernel with the additional instruction of
cpufreq.debug=7.  The output is in the attached text file.

DaveJ, hey, does any of this ring a bell and/or make sense to you?

Apologies for letting this sit unattended for so long. David, is this still a
problem with the latest kernels? I'm hoping we've since inherited a fix from
upstream...

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.