Haha, you got me there ;-). It might be a little more responsive in the bad state, but I am not sure. May be just an apparent feel. The only thing I feel a little different is that in good state, its like periodically I notice a cranking sound from my hard drive as if it got kicked to wake up :p.
Never booted with idle=poll. Shall try that out. Meanwhile, here are the outputs of cat /proc/interrupts within an interval of 60 seconds (see attachments), and also the difference. Seems that they still account for only at most 200 per second.Shall try out oprofile sometime. Thanks, Hirakendu. Andreas Mohr <[EMAIL PROTECTED]> wrote: Hi, On Mon, Jul 16, 2007 at 11:04:11PM -0700, hirakendu das wrote: > Hmm, seems that I can reproduce it frequently (in fact everytime :-). > The lspci outputs are attached. Although there is no difference (diff > -ruN). Yes, there is no clue which program etc is causing it or whats > happening. Don't mind, but I even suspect some powertop flaw, because > doing a cat /proc/acpi/processor/CPU0/power shows only C2 or C3 as > active (starred). And frankly, there is no difference in the way CPU > fan behaves. (Would we not expect the fans to whine if it were indeed > in C0 mostly ?). Umm, excuuuse me, but didn't you just say that the system felt more responsive in bad state? ;) In that case it definitely wouldn't be a powertop flaw. Maybe watching /proc/interrupts provides some clue? And booting with idle=poll provides higher performance about equal to the one the "bad state" provides, right? (due to "bad state" keeping CPU in non-Cx states almost as much as idle=poll does. Just to further nail down whether it's a "powertop flaw" or whether it's a real issue... Maybe running oprofile on an idle system in good and bad state shows some characteristic differences which could nail it down? (but probably most extra "bad state" activity is interrupt-based, thus it could be difficult to trace via oprofile) Andreas Mohr --------------------------------- Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games.
CPU0 CPU1 0: 4774793 0 IO-APIC-edge timer 1: 64895 0 IO-APIC-edge i8042 9: 66221 0 IO-APIC-fasteoi acpi 12: 57375 0 IO-APIC-edge i8042 14: 180084 0 IO-APIC-edge libata 15: 0 0 IO-APIC-edge libata 16: 1498407 0 IO-APIC-fasteoi uhci_hcd:usb5, nvidia 18: 1465760 0 IO-APIC-fasteoi uhci_hcd:usb4, ipw3945, yenta 19: 55489 0 IO-APIC-fasteoi ahci, uhci_hcd:usb3, ohci1394 20: 3 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2 21: 308438 0 IO-APIC-fasteoi HDA Intel, tifm_7xx1 22: 12000 0 IO-APIC-fasteoi sdhci:slot0, eth0 NMI: 0 0 LOC: 917427 3384300 ERR: 0 MIS: 0
CPU0 CPU1 0: 4779568 0 IO-APIC-edge timer 1: 64917 0 IO-APIC-edge i8042 9: 66368 0 IO-APIC-fasteoi acpi 12: 57375 0 IO-APIC-edge i8042 14: 180534 0 IO-APIC-edge libata 15: 0 0 IO-APIC-edge libata 16: 1502109 0 IO-APIC-fasteoi uhci_hcd:usb5, nvidia 18: 1466989 0 IO-APIC-fasteoi uhci_hcd:usb4, ipw3945, yenta 19: 55500 0 IO-APIC-fasteoi ahci, uhci_hcd:usb3, ohci1394 20: 3 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2 21: 308438 0 IO-APIC-fasteoi HDA Intel, tifm_7xx1 22: 12030 0 IO-APIC-fasteoi sdhci:slot0, eth0 NMI: 0 0 LOC: 918738 3386185 ERR: 0 MIS: 0
CPU0 CPU1 0: 4755 0 IO-APIC-edge timer 1: 22 0 IO-APIC-edge i8042 9: 147 0 IO-APIC-fasteoi acpi 12: 0 0 IO-APIC-edge i8042 14: 450 0 IO-APIC-edge libata 15: 0 0 IO-APIC-edge libata 16: 3702 0 IO-APIC-fasteoi uhci_hcd:usb5, nvidia 18: 1229 0 IO-APIC-fasteoi uhci_hcd:usb4, ipw3945, yenta 19: 11 0 IO-APIC-fasteoi ahci, uhci_hcd:usb3, ohci1394 20: 0 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2 21: 0 0 IO-APIC-fasteoi HDA Intel, tifm_7xx1 22: 30 0 IO-APIC-fasteoi sdhci:slot0, eth0 NMI: 0 0 LOC: 1311 1885 ERR: 0 MIS: 0
_______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
