From: "Thomas Bächler" <thomas@archlinux.org>
To: "Thomas Bächler" <thomas@archlinux.org>,
"Andi Kleen" <ak@linux.intel.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, tpowa@archlinux.org
Subject: Re: 3.13: <module> disagrees about version of symbol <symbol>
Date: Mon, 07 Apr 2014 22:10:46 +0200 [thread overview]
Message-ID: <53430646.40507@archlinux.org> (raw)
In-Reply-To: <5342E46B.4080603@archlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
Am 07.04.2014 19:46, schrieb Thomas Bächler:
> Am 07.04.2014 19:30, schrieb Andi Kleen:
>>>> Do you have a specific config?
>>>> Specific compiler version?
>>>
>>> Using gcc 4.8 from Arch Linux with the configuration at [1] and Linux 3.14.
>>
>> I tested this configuration (with gcc 4.8 on FC20/19) and it loads
>> ext4 and all the other modules without any problems.
>>
>> Base tree:
>>
>> commit e06df6a7eae1ab1ef4deb076aeeaed90e948e5c0
>> Merge: c0fc3cb 9dd721c
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>> Date: Mon Mar 31 12:34:49 2014 -0700
>>
>> Must be something really archlinux specific. Please do some debugging.
>> Also please double check that all your test procedures are correct.
>
> Tetsuo was so kind to install Arch Linux and reproduce the exact
> procedure I use to create the kernel (which includes the automated
> creation of a pristine build environment) - his kernel booted just fine.
> I will do more tests today on two of my own computers to narrow this down.
I think I found out why nobody could reproduce the problem.
I did a few more tests and it turns out that the problem only occurs
when I boot the kernel with UEFI (using Gummiboot+EFISTUB). Now, except
for OVMF virtual machines, there are barely any 32 Bit UEFI machines
around, so nobody noticed. When I boot the kernel with 32 Bit BIOS, it
boots fine.
Just to clarify: As mentioned in my first mail, some symbols still get a
0x0 CRC (which I still think is wrong), but the mismatch does not occur
in BIOS mode.
On x86_64, the problem does not occur at all.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-04-07 20:10 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
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 [this message]
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=53430646.40507@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 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).