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] acpi-cpufreq cannot be loaded.
Date: Fri, 11 Apr 2014 12:52:20 +0000	[thread overview]
Message-ID: <bug-73781-12968-TOm8ebfrSH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73781-12968@https.bugzilla.kernel.org/>

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

--- Comment #7 from KATO Hiroshi <katoh@mikage.ne.jp> ---
(In reply to Viresh Kumar from comment #3)

Thank you for your kindness. I built revert patched drivers/cpufreq, 
and unfortunately the problem has not been solved yet.

I also overwrite drivers/cpufreq with 3.13.8's one, the same problem happens.
So maybe cpufreq does not relate to this.


(In reply to Lukasz Majewski from comment #4)

> Why the "No such device" error show up? This is strange.
>I suppose, that the acpi_cpufreq.ko module was built correctly.

I use an ArchLinux package kernel. And never heard a similar problem
on the bts of archlinux. So I think acpi_cpufreq.ko module was built correctly.

> Also, I've noticed, that the p4-clockmod is also inserted. Could you
> compile it in and left the acpi-cpufreq to be inserted as a standalone module?

When I was searching the solution, I found a tweet of somebody who may be
worrying the same problem.
Though unlike me he uses c2d, he wrote that only p4-clockmod could be used. So
I gave it a try. 

inserted modules 3.13.8
https://bugzilla.kernel.org/attachment.cgi?id=131921
inserted modules 3.14
https://bugzilla.kernel.org/attachment.cgi?id=131931

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

  parent reply	other threads:[~2014-04-11 12:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 14:23 [Bug 73781] New: acpi-cpufreq cannot be loaded bugzilla-daemon
2014-04-10 14:52 ` [Bug 73781] " 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 [this message]
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-TOm8ebfrSH@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).