From: "Grant Likely" <grant.likely@secretlab.ca>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Problem in compiling a kernel module
Date: Mon, 12 Mar 2007 12:36:43 -0600 [thread overview]
Message-ID: <528646bc0703121136g628bcaf7if0ef36f87d27dc6b@mail.gmail.com> (raw)
In-Reply-To: <20070312170030.GA5613@server.idefix.lan>
On 3/12/07, Matthias Fechner <idefix@fechner.net> wrote:
> If I try now to compile to kernel I got the following error message:
> WARNING: drivers/i2c/chips/max6633.o - Section mismatch: reference to
> .init.data: from .text after 'cleanup_module' (at offset 0x196)
> WARNING: drivers/i2c/chips/max6633.o - Section mismatch: reference to
> .init.data: from .text after 'cleanup_module' (at offset 0x1a6)
> WARNING: drivers/i2c/chips/max6633.o - Section mismatch: reference to
> .init.data: from .text after 'cleanup_module' (at offset 0x1da)
> WARNING: drivers/i2c/chips/max6633.o - Section mismatch: reference to
> .init.data: from .text after 'cleanup_module' (at offset 0x1e2)
>
> What does that mean or how can debug or solve the problem?
>
Looks like you're trying to access inital data (which is freed after
module load) from regular code (which is not)
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-03-12 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 17:00 Problem in compiling a kernel module Matthias Fechner
2007-03-12 18:36 ` Grant Likely [this message]
2007-03-13 4:30 ` Matthias Fechner
2007-03-13 4:55 ` Grant Likely
2007-03-13 12:55 ` Ben Warren
2007-03-14 4:33 ` Matthias Fechner
2007-03-14 6:54 ` Domen Puncer
2007-03-15 4:27 ` Matthias Fechner
2007-08-07 17:42 ` Fedora 7 on a non FPU system Michael Brian Willis
2007-08-07 19:11 ` Roland Dreier
2007-08-07 19:29 ` Josh Boyer
2007-08-07 21:43 ` Clemens Koller
2007-08-08 22:18 ` Michael Brian Willis
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=528646bc0703121136g628bcaf7if0ef36f87d27dc6b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).