Bug 195367 - acpi_cpufreq prevents suspend (Could not power down device <NULL>)
Summary: acpi_cpufreq prevents suspend (Could not power down device <NULL>)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cpuspeed
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jarod Wilson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-14 21:44 UTC by Sitsofe Wheeler
Modified: 2007-11-30 22:11 UTC (History)
5 users (show)

Fixed In Version: 2.6.18-1.2257.fc5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-22 15:27:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sitsofe Wheeler 2006-06-14 21:44:31 UTC
Description of problem:
Having the acpi_cpufreq module loaded vetos suspension (either to ram or to
disk) on certain systems and leaves a cryptic error message in the logs.

Version-Release number of selected component (if applicable):
cpuspeed-1.2.1-1.33
kernel-2.6.16-1.2133_FC5

How reproducible:
Reproducible every time.

Steps to Reproduce:
1. Boot the system.
2. Run pm-suspend .
  
Actual results:
Monitor blanks, disks power down but system powers back up straight away.

Expected results:
System to stay powered down until ACPI wake up event.

Additional info:
This is in the logs:

Jun  5 18:10:23 x kernel: Stopping tasks:
=====================================================================|
Jun  5 18:10:23 x kernel: Shrinking memory... done (29166 pages freed)
Jun  5 18:10:23 x kernel: pnp: Device 00:08 disabled.
Jun  5 18:10:23 x kernel: pnp: Device 00:07 disabled.
Jun  5 18:10:23 x kernel: skge eth0: disabling interface
Jun  5 18:10:23 x kernel: Class driver suspend failed for cpu0
Jun  5 18:10:23 x kernel: Could not power down device <NULL>: error -22
Jun  5 18:10:23 x kernel: Some devices failed to power down, aborting suspend

Using
modprobe -r acpi_cpufreq
beforehand lets the suspend happen successfully. acpi_cpufreq seems to be loaded
by the cpuspeed initscript. On a related note using
/sbin/chkconfig cpuspeed off
leaves cpuspeed turned on at runlevel 1.

(There is only 1 CPU) The output of
cat /proc/acpi/processor/CPU0/throttling
is:
state count:             2
active state:            T0
states:
   *T0:                  00%
    T1:                  50%

cat /proc/cpuinfo says this:
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 7
model name      : AMD Duron(tm) processor
stepping        : 1
cpu MHz         : 1111.051
cache size      : 64 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow ts
bogomips        : 2225.14

Comment 1 Sitsofe Wheeler 2006-09-09 09:34:37 UTC
ccing Alan because it might be a kernel issue and there's been no response...

Comment 2 Jarod Wilson 2006-12-21 20:20:45 UTC
What happens if you try with the latest kernel and cpuspeed builds available
from the updates yum repo?

Comment 3 Sitsofe Wheeler 2006-12-22 15:27:07 UTC
This has been fixed.
modprobe acpi_cpufreq
now says:
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.18-1.2257.fc5/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko):
No such device

And on boot the following is in the logs:
powernow-k8: Processor cpuid 671 not supported

Resolving CURRENTRELEASE.


Note You need to log in before you can comment on or make changes to this bug.