From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 73781] acpi-cpufreq cannot be loaded.
Date: Fri, 11 Apr 2014 15:17:04 +0000 [thread overview]
Message-ID: <bug-73781-12968-V3QDJoag2K@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 #9 from KATO Hiroshi <katoh@mikage.ne.jp> ---
(In reply to Viresh Kumar from comment #8)
> Do git bisect please and let us know the offending commit.
I'll do as possible.
By the way while glancing through dmesg, one important difference found.
3.13.8
[ 0.087346] acpiphp: Slot [1-1] registered
[ 0.090033] Found 1 acpi root devices
[ 0.140788] Switched to clocksource acpi_pm
[ 1.856854] ACPI: acpi_idle registered with cpuidle
[ 2.101747] thinkpad_acpi: ThinkPad ACPI Extras v0.25
3.14
[ 0.083948] acpiphp: Slot [1-1] registered
[ 0.139115] Switched to clocksource acpi_pm
[ 2.266132] thinkpad_acpi: ThinkPad ACPI Extras v0.25
3.14 kernel does not find an acpi root device.
I think this can be the point of this problem intead of cpufreq.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-11 15:17 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
2014-04-11 14:07 ` bugzilla-daemon
2014-04-11 15:17 ` bugzilla-daemon [this message]
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-V3QDJoag2K@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.