From: Andrew Morton <akpm@osdl.org>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, cpufreq@www.linux.org.uk
Subject: Re: cpufreq stops working after a while
Date: Fri, 11 Aug 2006 12:18:06 -0700 [thread overview]
Message-ID: <20060811121806.51a73fe5.akpm@osdl.org> (raw)
In-Reply-To: <44DCD618.2040700@rtr.ca>
On Fri, 11 Aug 2006 15:10:16 -0400
Mark Lord <lkml@rtr.ca> wrote:
> >> WHY?
> >
> > cpufreq seems to have relatively frequent problems.
> >
> >> And how can I fix it?
> >
> > You could start by telling us which kernel versions are affected ;)
>
>
> Mmm.. since it appears to be related, kbuild dumps this out when building the kernel:
>
> WARNING: drivers/acpi/processor.o - Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset 0xf29) and 'acpi_processor_cst_has_changed'
>
> A possible source for the bug, or total red herring ?
An RH. acpi_processor_power_init() is actually non-buggy, due to its
interesting games with `first_run'.
A section error would usually trigger a wild oops if you're affected by it.
next prev parent reply other threads:[~2006-08-11 19:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 18:25 Mark Lord
2006-08-11 18:39 ` Dave Jones
2006-08-11 19:41 ` Mark Lord
2006-08-11 20:01 ` Mark Lord
2006-08-11 20:12 ` Dave Jones
2006-08-11 18:46 ` Andrew Morton
2006-08-11 19:01 ` Mark Lord
2006-08-11 19:10 ` Mark Lord
2006-08-11 19:18 ` Andrew Morton [this message]
2006-08-11 19:55 Pallipadi, Venkatesh
2006-08-11 20:29 ` Mark Lord
2006-08-11 20:39 ` Mark Lord
2006-08-11 21:01 ` Dave Jones
2006-08-11 21:09 ` Mark Lord
2006-08-11 21:15 ` Mark Lord
2006-08-11 21:17 ` Mark Lord
2006-08-11 21:25 ` Mark Lord
2006-08-18 15:11 ` Pavel Machek
2006-08-24 14:44 ` Mark Lord
2006-08-24 16:15 ` Matthew Garrett
2006-08-11 21:08 Pallipadi, Venkatesh
2006-08-11 21:38 Pallipadi, Venkatesh
2006-08-11 21:53 ` Mark Lord
2006-08-11 22:18 Pallipadi, Venkatesh
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=20060811121806.51a73fe5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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
Powered by JetHome