Bug 391801
| Summary: | Massive numbers of wakeups (50K) reported after reboot | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Bailey <mark.bailey> | ||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 8 | CC: | chris.brown, pfpschneider, rw | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i386 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2009-01-09 07:28:07 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Mark Bailey
2007-11-20 10:09:34 UTC
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few weeks if there is no additional information lodged. Hi, No change in 2.6.23.15-137.fc8, same symptoms. What additional information/actions can I provide that might help? Thanks, Mark Could you attach the following as text/plain individual attachments to this bug: dmesg > dmesg.out lsmod > lsmod.out If you can cut and paste the powertop output as well that might be helpful. Cheers Chris Created attachment 296501 [details]
lsmod
Created attachment 296502 [details]
dmesg
Created attachment 296503 [details]
powertop high values
I am also experiencing this problem. The number of wakeups is somewhat lower, 8K to 20K per second, but there appears to be no reason for them. I have seen reports of this problem on other distributions, notably Ubuntu. I am running current Fedora 9 on a Thinkpad T60p. The problem does not appear to be a bug in powertop, as sensors-applet is reporting high temperatures, and power manager is reporting high power consumption. The problem is not constant (and I did not experience it at all in recent F8 versions). name -a Linux idefix.research.bell-labs.com 2.6.25.3-18.fc9.i686 #1 SMP Tue May 13 05:38:53 EDT 2008 i686 i686 i386 GNU/Linux I'll attach powertop and top output. Created attachment 306625 [details]
sudo powertop --dump
Created attachment 306626 [details]
top
Hi: This bug is still present in the current version of F9, 2.6.25.4-30.fc9.i686 There is some discussion on it (interspersed with discussion of the rescheduling interrupts behaviour) on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/145377 The bug appears to be related to particular hardware (I have a T60p), my guess being either the wireless card (I have a 3945) or the cardbus bridge (because that misbehaves in other ways). Anyway, my question is whether there are things that I can do to help track down the source of the problem. For example, is there a tool that can analyse DMA activity (because my guess is that the wakeups are not interrupts, but instead are related to DMA). Peter F. Patel-Schneider Rebuilding the kernel with yenta_socket built as a module and adding yenta_socket to the modprobe blacklist works around the problem for me. I've filed Bug #456173 requesting the kernel config to be changed so that the rebuilding step will not be necessary any longer. Rene This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. 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 '8'. 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 8'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 8 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 I haven't seen this for quite some time. I expect that the problem has gone away for some reason or other. Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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. |