From: "Thomas Bächler" <thomas@archlinux.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
thomas@archlinux.org, ak@linux.intel.com
Cc: viro@ZenIV.linux.org.uk, geert@linux-m68k.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, tpowa@archlinux.org
Subject: Re: 3.13: <module> disagrees about version of symbol <symbol>
Date: Tue, 28 Jan 2014 08:53:41 +0100 [thread overview]
Message-ID: <52E76205.4080903@archlinux.org> (raw)
In-Reply-To: <201401262322.DDF78613.FVSFOLOOJFHtQM@I-love.SAKURA.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Am 26.01.2014 15:22, schrieb Tetsuo Handa:
> Thomas B臘hler wrote:
>> This looks exactly like the problem experienced by Tetsuo Handa in [1].
>> However, for me, his solution, i.e. setting
>> CONFIG_PHYSICAL_ALIGN=0x1000000
>> instead of
>> CONFIG_PHYSICAL_ALIGN=0x100000
>> doesn't help and the symptoms stay the same (and, according to the
>> documentation and to Kbuild, both are valid values on i686).
>
> I tried your config with "make localmodconfig" and saw the symptoms. I changed
> CONFIG_PHYSICAL_ALIGN from 0x100000 to 0x1000000 and no longer see the symptoms.
No idea why this worked for you. Anyway, if
CONFIG_PHYSICAL_ALIGN=0x1000000 is necessary, then Kconfig should
enforce it.
And none of this changes that symbols without CRC are a bug.
> Did you save your config after changing CONFIG_PHYSICAL_ALIGN ?
Well, of course.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-01-28 7:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 9:01 3.13: <module> disagrees about version of symbol <symbol> Thomas Bächler
2014-01-26 14:22 ` Tetsuo Handa
2014-01-28 7:53 ` Thomas Bächler [this message]
2014-03-31 23:16 ` Thomas Bächler
2014-03-31 23:34 ` Andi Kleen
2014-03-31 23:38 ` Thomas Bächler
2014-04-05 1:13 ` Andi Kleen
2014-04-05 14:29 ` Thomas Bächler
2014-04-05 17:23 ` Tetsuo Handa
2014-04-05 21:47 ` Thomas Bächler
2014-04-07 17:30 ` Andi Kleen
2014-04-07 17:46 ` Thomas Bächler
2014-04-07 20:10 ` Thomas Bächler
2014-04-07 20:42 ` Andi Kleen
2014-04-07 21:25 ` Fleming, Matt
2014-04-07 21:30 ` Thomas Bächler
2014-04-07 21:46 ` Tetsuo Handa
2014-04-08 12:14 ` Matt Fleming
2014-04-08 18:57 ` Thomas Bächler
2014-04-08 20:04 ` Thomas Bächler
2014-04-09 8:25 ` Matt Fleming
2014-04-09 8:30 ` Thomas Bächler
2014-04-09 18:01 ` Thomas Bächler
2014-04-09 20:43 ` Matt Fleming
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=52E76205.4080903@archlinux.org \
--to=thomas@archlinux.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=tpowa@archlinux.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.