public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, len.brown@intel.com
Subject: [BUG] Link problem on drivers/acpi/processor_idle.c
Date: Sun, 28 May 2006 12:04:00 -0400	[thread overview]
Message-ID: <4479C9F0.9090807@rtr.ca> (raw)

In 2.6.17-rc5, the GNU linker gives me this message:

WARNING: drivers/acpi/processor.o - Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset 0xec7) and 'acpi_processor_cst_has_changed'

It is basically pointing out a potential bug on from processor_idle.c,
on this line of code:

     dmi_check_system(processor_power_dmi_table);

The problem here, is that processor_power_dmi_table is declared as __cpuinitdata,
and is not guaranteed to exist when invoked from code other than __init code.

The acpi_processor_power_init() routine is NOT marked as __init code.

Cheers

                 reply	other threads:[~2006-05-28 16:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4479C9F0.9090807@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@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