From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4 Description of problem: After some period of inactivity, the kernel reports 'irq 10: nobody cared!', a trace (attached), and 'Disabling IRQ #10'. This results in the USB mouse (Logitech optical wheel mouse) being very jumpy, ie large delays and imprecise movements (with F/C 3 2.6.11 vanilla kernels the mouse completely stopped). The problem goes away if I reload the uhci_hcd module (as suggested in bug 157146): rmmod uhci_hcd; modprobe uhci_hcd Version-Release number of selected component (if applicable): kernel-smp-2.6.11-1.1369_FC4 How reproducible: Always Steps to Reproduce: 1. boot 2. login (X) 3. wait until kernel disables IRQ 10 Actual Results: The USB mouse becomes jumpy. Expected Results: The mouse should have been as responsive as it was on bootup (I don't know if the kernel is supposed to jettison IRQ 10). Additional info: Hardware: P III system (VIA VT8633 [Apollo Pro266]) with NVidia Quadro graphics card (and nvidia driver), extra USB 2.0 card (00:0a.2 USB Controller: NEC Corporation USB 2.0 (rev 04)), Creative Labs SB Live! sound card. Perhaps this is a duplicate of Bug 157146 but this happens to me always in normal operation; and the machine is not supposed to ever go into suspend or sleep mode (as is the case for the aforementioned bug).
Created attachment 115918 [details] Kernel message when disabling irq 10; mouse becomes jumpy afterwards Whenevere IRQ 10 is disabled the kernel message looks like the attached. On some occasions, IRQ 11 is disabled with different numbers in the [<c...>] fields.
Well, this is a part of my problem decribed here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160958
The behaviour mentioned above happens at ~ 1 Minute intervals when reading/writing to a USB hard drive, which is attached to the USB 2.0 adaptor card.
[This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you.
The bug persists as described with the new 2.6.12-1.1398_FC4smp kernel.
Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks.
Mass update to all FC4 bugs: An update has been released (2.6.14-1.1637_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks.
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you.
Closing per previous comment.