From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 17001] ondemand governor non-functional / ACPI P-states driver
Date: Mon, 6 Sep 2010 10:46:21 GMT [thread overview]
Message-ID: <201009061046.o86AkLgD009484@demeter1.kernel.org> (raw)
In-Reply-To: <bug-17001-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=17001
--- Comment #16 from Peter Ganzhorn <peter.ganzhorn@googlemail.com> 2010-09-06 10:46:19 ---
Yes, I do compile kernels myself. The distro kernels usually are patched and
contain back-ports of all kind, so filing a bug report on bugzilla.kernel.org
with a distro kernel is somewhat pointless I figure...
On top of that I only include drivers and features I need and usually compile
the stuff in - the Linux kernel was designed to be a monolithic kernel, not a
microkernel. ;)
If you want to add some more debugging printks to the ondemand governor
sources, just send me a patch or tell me where I should put them. Although I
guess this will be tricky for me to do right, since you know what you'd like to
see and I'm not a kernel hacker... (I know how to read C and can write small C
programs, but I'm not a professional programmer or something like that)
And here's a bit of a problem: 2.6.27.* still does have EXT4 marked as
experimental, will this work with current EXT4 file systems or am I going to
run into some serious trouble when running this kernel? (My root partition is
an EXT4 partition, and obviously I didn't pay attention when I installed the
system...seems Debian Squeeze uses EXT4 as default FS already?!)
Second problem: 2.6.36-rc3 won't compile, I'm getting an implicit declaration
error in the i915 DRM driver...
Do you think trying 2.6.28 instead of .27 could help since EXT4 was marked
stable in .28 if I recall this right.
Or have there been major changes in the CPUFREQ code after 2.6.27?
I'll tweak my .config to include CPUFREQ as modules as you suggested for now.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2010-09-06 10:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 11:52 [Bug 17001] New: ondemand governor non-functional / ACPI P-states driver bugzilla-daemon
2010-08-25 20:57 ` [Bug 17001] " bugzilla-daemon
2010-08-26 11:14 ` bugzilla-daemon
2010-08-26 14:39 ` bugzilla-daemon
2010-08-26 14:40 ` bugzilla-daemon
2010-08-26 15:14 ` bugzilla-daemon
2010-08-27 12:21 ` bugzilla-daemon
2010-08-27 12:24 ` bugzilla-daemon
2010-08-27 12:27 ` bugzilla-daemon
2010-09-06 1:47 ` bugzilla-daemon
2010-09-06 2:30 ` bugzilla-daemon
2010-09-06 9:20 ` bugzilla-daemon
2010-09-06 9:37 ` bugzilla-daemon
2010-09-06 10:13 ` bugzilla-daemon
2010-09-06 10:22 ` bugzilla-daemon
2010-09-06 10:29 ` bugzilla-daemon
2010-09-06 10:46 ` bugzilla-daemon [this message]
2010-10-15 10:11 ` 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=201009061046.o86AkLgD009484@demeter1.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.