Created attachment 694088 [details] benchmark results of 7-zip benchmark before and after suspend-to-ram Description of problem: After suspend to ram, frequency scaling seems to be broken when running on battery. The system feels slow, and the 7zip benchmark shows throughput is reduced to about 20%. Version-Release number of selected component (if applicable): Fedora 17 kernel 3.7.3-101.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. run benchmark on battery 2. suspend-to-ram + resume 3. run benchmark again Actual results: throughput down to 20%, system feels slow Expected results: no impact on performance Additional info: Dell E6320 Notebook General ================================= UUID: 0ca4f454-6194-4680-b876-11db7c1a5b58 OS: Fedora release 17 (Beefy Miracle) Default run level: Unknown Language: en_US.UTF-8 Platform: x86_64 BogoMIPS: 5587.19 CPU Vendor: GenuineIntel CPU Model: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz CPU Stepping: 7 CPU Family: 6 CPU Model Num: 42 Number of CPUs: 4 CPU Speed: 2801 System Memory: 7866 System Swap: 0 Vendor: Dell Inc. System: Latitude E6320 01 Form factor: Laptop Kernel: 3.7.3-101.fc17.x86_64 SELinux Enabled: 0 SELinux Policy: targeted SELinux Enforce: Unknown MythTV Remote: Unknown MythTV Role: Unknown MythTV Theme: Unknown MythTV Plugin: MythTV Tuner: -1 Devices ================================= (32902:7247:4136:1170) pci, lpc_ich, PCI/ISA, QM67 Express Chipset Family LPC Controller (4631:33313:4136:1170) pci, sdhci-pci, BASE, N/A (32902:294:4136:1170) pci, i915, VIDEO, 2nd Generation Core Processor Family Integrated Graphics Controller (32902:7190:4136:1170) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (32902:7184:4136:1170) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (32902:7186:4136:1170) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (32902:7188:4136:1170) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (32902:7200:4136:1170) pci, snd_hda_intel, MULTIMEDIA, 6 Series/C200 Series Chipset Family High Definition Audio Controller (32902:5378:4136:1170) pci, e1000e, ETHERNET, 82579LM Gigabit Network Connection (32902:7213:4136:1170) pci, ehci_hcd, USB, 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (32902:7202:4136:1170) pci, None, SERIAL, 6 Series/C200 Series Chipset Family SMBus Controller (32902:16939:32902:4385) pci, iwlwifi, NETWORK, Centrino Ultimate-N 6300 3x3 AGN (32902:7171:4136:1170) pci, ahci, STORAGE, 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (32902:7229:4136:1170) pci, serial, 16550_SERIAL, 6 Series/C200 Series Chipset Family KT Controller (32902:7206:4136:1170) pci, ehci_hcd, USB, 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (32902:260:4136:1170) pci, None, HOST/PCI, 2nd Generation Core Processor Family DRAM Controller (32902:7226:4136:1170) pci, mei, SIMPLE, 6 Series/C200 Series Chipset Family MEI Controller #1 (32902:7194:4136:1170) pci, pcieport, PCI/PCI, 6 Series/C200 Series Chipset Family PCI Express Root Port 6 Filesystem Information ================================= device mtpt type bsize frsize blocks bfree bavail file ffree favail ------------------------------------------------------------------- /dev/sda2 / ext4 4096 4096 3149608 461397 429403 802816 547925 547925 /dev/sda1 WITHHELD fuseblk 4096 4096 30507006 2927458 2927458 12234120 11800145 11800145 /dev/mapper/ce /home ext4 4096 4096 28354472 2698315 2554281 7208960 6442223 6442223 /dev/loop0 WITHHELD squashfs UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN
Does this still happen with 3.7.9 or 3.8.2 in updates-testing?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Still happends with kernel-3.8.3: Before suspend: Dict Compressing | Decompressing Speed Usage R/U Rating | Speed Usage R/U Rating KB/s % MIPS MIPS | KB/s % MIPS MIPS 22: 9497 306 3020 9239 | 105401 396 2403 9509 23: 9483 317 3047 9662 | 113031 430 2404 10343 24: 10306 348 3180 11081 | 111896 432 2405 10381 25: 9424 324 3320 10760 | 89969 314 2690 8460 ---------------------------------------------------------------- Avr: 324 3142 10186 393 2475 9673 Tot: 358 2809 9929 After suspend on battery: Dict Compressing | Decompressing Speed Usage R/U Rating | Speed Usage R/U Rating KB/s % MIPS MIPS | KB/s % MIPS MIPS 22: 2833 277 996 2756 | 17575 367 431 1585 23: 1792 286 638 1826 | 17708 375 432 1620 24: 1794 288 669 1929 | 17149 358 444 1591 25: 1752 284 705 2001 | 80018 393 1916 7524 ---------------------------------------------------------------- Avr: 284 752 2128 373 806 3080 Tot: 328 779 2604 After suspend with battery, but with external power supply plugged in (performance-wise no difference): Dict Compressing | Decompressing Speed Usage R/U Rating | Speed Usage R/U Rating KB/s % MIPS MIPS | KB/s % MIPS MIPS 22: 1328 243 530 1291 | 13618 284 432 1228 23: 1596 268 607 1627 | 16799 358 430 1537 24: 1619 272 639 1741 | 15495 328 437 1437 25: 1721 283 694 1965 | 16735 362 434 1573 ---------------------------------------------------------------- Avr: 267 618 1656 333 433 1444 Tot: 300 525 1550 Frequency statistics while running the benchmark after suspend: | | Actual 641 MHz 620 MHz Turbo Mode 0.0% | Turbo Mode 0.0% | Turbo Mode 0.0% 0.0% 2.81 GHz 0.0% | 2.81 GHz 0.0% | 2.81 GHz 0.0% 0.0% 2.60 GHz 0.0% | 2.60 GHz 0.0% | 2.60 GHz 0.0% 0.0% 2.40 GHz 0.0% | 2.40 GHz 0.0% | 2.40 GHz 0.0% 0.0% 2.21 GHz 0.0% | 2.21 GHz 0.0% | 2.21 GHz 0.0% 0.0% 2.00 GHz 0.0% | 2.00 GHz 0.0% | 2.00 GHz 0.0% 0.0% 1.80 GHz 0.0% | 1.80 GHz 0.0% | 1.80 GHz 0.0% 0.0% 1.60 GHz 0.0% | 1.60 GHz 0.0% | 1.60 GHz 0.0% 0.0% 1400 MHz 0.0% | 1400 MHz 0.0% | 1400 MHz 0.0% 0.0% 1200 MHz 0.0% | 1200 MHz 0.0% | 1200 MHz 0.0% 0.0% | Core | CPU 1 CPU 3 | | Actual 633 MHz 611 MHz | Turbo Mode 0.0% | Turbo Mode 0.0% 0.0% | 2.81 GHz 0.0% | 2.81 GHz 0.0% 0.0% | 2.60 GHz 0.0% | 2.60 GHz 0.0% 0.0% | 2.40 GHz 0.0% | 2.40 GHz 0.0% 0.0% | 2.21 GHz 0.0% | 2.21 GHz 0.0% 0.0%
Does it make sence at all to report bugs at Fedora's bugzilla, or should I better turn to upstream in the first place? Usually all my bug-reports end up the same way: 1. File bug-Report 2. Is this bug already fixed in updates-testing/rawhide -> Yes: Bug is closed immediatly -> No: Bug is closed a year later by the bug-close daemon
(In reply to comment #4) > Does it make sence at all to report bugs at Fedora's bugzilla, or should I > better turn to upstream in the first place? We encourage users to report bugs upstream whenever they feel comfortable doing so. > Usually all my bug-reports end up the same way: > > 1. File bug-Report > 2. Is this bug already fixed in updates-testing/rawhide > -> Yes: Bug is closed immediatly > -> No: Bug is closed a year later by the bug-close daemon We have a floating average of about 1000 kernels bugs at any given time. There are only 3 people actively looking at them all. Unfortunately, that means some are prioritized lower than others. Machines not booting at all and kernel panics tend to get looked at first. If you do report the bug upstream and that results something that they'd like to see tested, we can certainly build test kernels for users and backport fixes once they are identified.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.