cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 73781] New: acpi-cpufreq cannot be loaded.
Date: Thu, 10 Apr 2014 14:23:47 +0000	[thread overview]
Message-ID: <bug-73781-12968@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=73781

            Bug ID: 73781
           Summary: acpi-cpufreq cannot be loaded.
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.14
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: cpufreq@vger.kernel.org
          Reporter: katoh@mikage.ne.jp
        Regression: No

After I upgraded kernel to 3.14, acpi-cpufreq module cannot be loaded.
Accordingly my laptop's cpufreq doesn't run anymore.
Until kernel 3.13.8, acpi-cpufreq has been loaded automatically as expected.

If I try to load acpi-cpufreq manually on 3.14, 

# modprobe acpi-cpufreq
modprobe: ERROR: could not insert 'acpi_cpufreq': No such device

Strangely if p4_clockmod was loaded initially, acpi-cpufreq can be
loaded sucessfully too. My laptop's cpu is PentiumM though.

# modprobe p4-clockmod
# modprobe acpi-cpufreq

In this case, available frequencies are messed up.

# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
212500 425000 637500 850000 1062500 1275000 1487500 1700000

On 3.13.8 (This is correct.)
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
1700000 1400000 1200000 1000000 800000 600000 


/proc/cpuinfo on Linux version 3.13.8
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 9
model name      : Intel(R) Pentium(R) M processor 1700MHz
stepping        : 5
microcode       : 0x7
cpu MHz         : 600.000
cache size      : 1024 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush
dts acpi mmx fxsr sse sse2 tm pbe bts est tm2
bogomips        : 1199.92
clflush size    : 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2014-04-10 14:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 14:23 bugzilla-daemon [this message]
2014-04-10 14:52 ` [Bug 73781] acpi-cpufreq cannot be loaded bugzilla-daemon
2014-04-10 15:44 ` bugzilla-daemon
2014-04-11  3:40 ` bugzilla-daemon
2014-04-11  8:05 ` bugzilla-daemon
2014-04-11 12:44 ` bugzilla-daemon
2014-04-11 12:44 ` bugzilla-daemon
2014-04-11 12:46 ` bugzilla-daemon
2014-04-11 12:52 ` bugzilla-daemon
2014-04-11 14:07 ` bugzilla-daemon
2014-04-11 15:17 ` bugzilla-daemon
2014-04-16  8:57 ` bugzilla-daemon
2014-04-16 12:39 ` bugzilla-daemon
2014-04-17  8:13 ` bugzilla-daemon
2014-04-17 15:07 ` bugzilla-daemon
2014-04-17 15:24 ` bugzilla-daemon
2014-04-18  1:59 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-73781-12968@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).