← Back to team overview

kernel-packages team mailing list archive

[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

** Changed in: linux (Ubuntu)
       Status: Incomplete => Expired

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  pm-utils hook unable to restore previous CPU state when resuming from

Status in linux package in Ubuntu:

Bug description:
  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 hole translation are activated
  Kernel boot options : /boot/vmlinuz-3.5.0-49-lowlatency root=UUID=xxxxxxxxx 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

  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
  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)

To manage notifications about this bug go to: