From: Dave Jones <davej@redhat.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Berthold Cogel <cogel@rrz.uni-koeln.de>,
linux-kernel@vger.kernel.org, "Pallipadi,
Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: BUG linux-2.6-20-rc1: kernel BUG at drivers/cpufreq/cpufreq_userspace.c
Date: Tue, 19 Dec 2006 09:20:03 -0500 [thread overview]
Message-ID: <20061219142003.GC25461@redhat.com> (raw)
In-Reply-To: <200612190421_MC3-1-D58E-782E@compuserve.com>
On Tue, Dec 19, 2006 at 04:18:13AM -0500, Chuck Ebbert wrote:
> In-Reply-To: <45859609.8050502@rrz.uni-koeln.de>
>
> On Sun, 17 Dec 2006 20:10:01 +0100, Berthold Cogel wrote:
> > I've found a kernel bug in linux-2.6-20-rc1 from kernel.org:
> > Dec 17 19:12:56 localhost kernel: kernel BUG at drivers/cpufreq/cpufreq_userspace.c:140!
>
> Does this fix it?
>
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
>
> --- 2.6.20-rc1-32smp.orig/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
> +++ 2.6.20-rc1-32smp/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
> @@ -706,7 +706,7 @@ static int acpi_cpufreq_cpu_init(struct
> break;
> case ACPI_ADR_SPACE_FIXED_HARDWARE:
> acpi_cpufreq_driver.get = get_cur_freq_on_cpu;
> - get_cur_freq_on_cpu(cpu);
> + policy->cur = get_cur_freq_on_cpu(cpu);
> break;
> default:
> break;
A similar fix is in Linus' -git tree as
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a507ac4b01ed379a74eca5060f3553c4a4e5854c
Hopefully one day the kernel.org scripts will get around to making a -git6 patch.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-12-19 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 9:18 BUG linux-2.6-20-rc1: kernel BUG at drivers/cpufreq/cpufreq_userspace.c Chuck Ebbert
2006-12-19 14:20 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-17 19:10 Berthold Cogel
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=20061219142003.GC25461@redhat.com \
--to=davej@redhat.com \
--cc=76306.1226@compuserve.com \
--cc=cogel@rrz.uni-koeln.de \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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