From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git7: section mismatches woes
Date: Sat, 2 Feb 2008 23:47:29 +0100 [thread overview]
Message-ID: <200802022347.29916.rjw@sisk.pl> (raw)
In-Reply-To: <20080202180828.GC25399@uranus.ravnborg.org>
On Saturday, 2 of February 2008, Sam Ravnborg wrote:
> On Wed, Jan 30, 2008 at 10:32:52PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 30 of January 2008, Sam Ravnborg wrote:
> > > On Wed, Jan 30, 2008 at 07:50:43PM +0100, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > I get these messages, the majority of which seem to be false-positives:
> > > ...
> > > > modpost: Found 35 section mismatch(es).
> > > > To see additional details select "Enable full Section mismatch analysis"
> > > > in the Kernel Hacking menu (CONFIG_SECTION_MISMATCH).
> > > Looking in to these atm.
> > >
> > > >
> > > > and if I compile the kernel with CONFIG_SECTION_MISMATCH, it breaks resuming
> > > > from RAM.
> > >
> > > The only functional difference when you enable CONFIG_SECTION_MISMATCH is the
> > > addition of the -fno-inline-functions-called-once to CFLAGS.
> > > So we have some code somewhere that breaks if it is not inlined by gcc.
> > >
> > > It would be nice to sort out where.
> > > If you have a rough idea where to look
> >
> > No, I don't.
> >
> > It looks like there's somewhere in arch/x86, since I ruled out kernel/power and
> > drivers/acpi already.
>
> Hi Rafael.
Hi,
> Do you plan to look closer into this or do you have an easy receipe so
> I can test myself (on a x86 64 bit box)?
Well, I really don't know how to approach this. Do you have an x86-64 box with
suspend to RAM working?
Rafael
next prev parent reply other threads:[~2008-02-02 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:50 2.6.24-git7: section mismatches woes Rafael J. Wysocki
2008-01-30 19:08 ` Sam Ravnborg
2008-01-30 21:32 ` Rafael J. Wysocki
2008-02-02 18:08 ` Sam Ravnborg
2008-02-02 22:47 ` Rafael J. Wysocki [this message]
2008-02-03 10:12 ` Sam Ravnborg
2008-02-03 12:32 ` Rafael J. Wysocki
2008-02-03 12:37 ` Sam Ravnborg
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=200802022347.29916.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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