[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319618 Title: pm-utils hook unable to restore previous CPU state when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
Eric_DL, thank you for reporting this bug to Ubuntu. Quantal reached EOL on May 16, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Is this reproducible in the latest release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ ? If so, please execute the following via a terminal in order for the necessary debugging information to be attached: apport-collect 1319618 ** Package changed: pm-utils (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319618 Title: pm-utils hook unable to restore previous CPU state when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
** Package changed: linux-lowlatency (Ubuntu) => pm-utils (Ubuntu) ** Description changed: Distro : Ubuntu Studio 12.10 (low latency kernel) M/B : Tyan Thunder S2915 (not S2915-E) CPU : AMD Opteron Dual-core 2212 (frequency steps from 1 to 2GHz) BIOS version : v3.0 (last version for this M/B) - BIOS config : NUMA + IOMMU + Memory whole translation are activated + BIOS config : NUMA + IOMMU + Memory hole translation are activated Kernel boot options : /boot/vmlinuz-3.5.0-49-lowlatency root=UUID=x ro quiet splash acpi_os_name=linux acpi=strict pcie_aspm=off iommu=noagp - Issue Description : CPU frequency looks normal after cold boot (slows down to 1GHz when CPUs are idle), but then stick to maximum frequency (2GHz) whatever CPU's load, since after resuming from first suspend to ram. Behavior stays the same from this point on. I didn't noticed it at first, until I took a look to my temperature sensors a few days after the update, and saw my CPUs 15C hotter than usual. Behavior has started with kernel update from 3.5.0-48 to 3.5.0-49 (issue doesn't occur when booting back on 3.5.0-48). - ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-49-lowlatency 3.5.0-49.50 ProcVersionSignature: Ubuntu 3.5.0-49.50-lowlatency 3.5.7.32 Uname: Linux 3.5.0-49-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu13 Architecture: amd64 Date: Thu May 15 03:40:49 2014 InstallationDate: Installed on 2013-05-26 (353 days ago) InstallationMedia: Ubuntu-Studio 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: linux-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319618 Title: pm-utils hook unable to restore previous CPU state when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1319618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
** Tags removed: kernel-bug ** Tags added: kernel-power -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319618 Title: pm-utils hook unable to restore previous CPU state when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1319618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
After some testing, I found that the cause of this issue lies within pm-
utils' hook "94cpufreq" (see below excerpts from pm-suspend.log).
Until kernel 3.5.0-48 ("3.5.0-48-lowlatency #49-Ubuntu SMP PREEMPT Tue Mar 18
22:34:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"), everything was running fine
:
/
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/
But, with kernel 3.5.0-49 ("3.5.0-49-lowlatency #50-Ubuntu SMP PREEMPT Tue Apr
8 04:37:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"), things started to get
less happy :
/
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
cat: write error: Invalid argument
cat: write error: Invalid argument
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/
And issue still happens with last kernel update (for my distro) :
3.5.0-51-lowlatency.
I've put some "set -x" here and there inside "94cpufreq" and it appears that
it's actually the restoration of pre-suspend values for "scaling_governor"
pseudo-files, that fails with the above "cat" error message.
To be specific, it's the call of "cat" command inside the generic
"restorestate" pm-function, and redirected to "scaling_governor" pseudo-file,
that fails.
For some unknown reason, just before going into suspend, hook
"94cpufreq" modifies "scaling_governor" values from "ondemand" to
"performance" and this modification succeeds. But when resuming, as
restoration of "ondemand" values fails, CPUs stay with the "performance"
setting (hence max frequency) from this point on, for all subsequent
suspend/resume cycles.
Pseudo-files "scaling_governor" backups do exist
(/var/run/pm-utils/pm-suspend/storage/state:cpuX_governor) and contains the
values that were active before suspend.
Destination pseudo-files are visible too when the "cat" operation is triggered
(/sys/devices/system/cpu/cpuX/cpufreq/scaling_governor).
I've tried to look at it from all angles I can think of, but I don't see
why an operation as simple as a "cat" inside a file would fail
except if kernel has modified in some way, the access policy for these
pseudo-files (hence my adding the "kernel-bug" tag).
Any ideas anyone ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319618
Title:
pm-utils hook unable to restore previous CPU state when resuming from
suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1319618/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319618] Re: pm-utils hook unable to restore previous CPU state when resuming from suspend
** Summary changed: - CPU frequency stuck to highest value after resuming from suspend + pm-utils hook unable to restore previous CPU state when resuming from suspend ** Tags added: kernel-bug pm-utils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319618 Title: pm-utils hook unable to restore previous CPU state when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1319618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
