From: "Thomas Bächler" <thomas@archlinux.org>
To: Matt Fleming <matt@console-pimps.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: matt.fleming@intel.com, ak@linux.intel.com,
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, hpa@zytor.com
Subject: Re: 3.13: <module> disagrees about version of symbol <symbol>
Date: Tue, 08 Apr 2014 20:57:05 +0200 [thread overview]
Message-ID: <53444681.1070902@archlinux.org> (raw)
In-Reply-To: <20140408121400.GI5222@console-pimps.org>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Am 08.04.2014 14:14, schrieb Matt Fleming:
> On Tue, 08 Apr, at 06:46:49AM, Tetsuo Handa wrote:
>> Fleming, Matt wrote:
>>> On 7 April 2014 21:42, Andi Kleen <ak@linux.intel.com> wrote:
>>>>
>>>> This sounds like the UEFI boot corrupts some memory?
>>>
>>> Hmpf, yeah. I'll take a look in the morning.
>>>
>>> Thomas, you mention you're running in a 32-bit vm earlier in this
>>> thread. Any chance you're using ovmf because that would make it much
>>> easier to track this down?
>>>
>>
>> I'm not familiar with UEFI boot, but it could happen because what
>> I experienced with BIOS boot was an address dependent behavior.
>>
>> https://lkml.org/lkml/2013/9/4/188
>
> OK, that's a pretty good clue, thanks Tetsuo.
>
> Thomas, could you try this patch? It seems the use of code32_start in
> the EFI boot stub was totally wrong for the case where the boot stub
> relocates the kernel - you're likely to hit this path if using the EFI
> boot stub directly from the EFI shell or gummiboot.
>
> It was pointing at the start of the kernel image and not the protected
> mode code.
Hello Matt,
I am unable to backport this to 3.14 for lack of assembler magic. While
I can test this with git master, I eventually still need a version that
is backported to 3.14. Any chance you could provide that, too?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-04-08 18:57 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
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 [this message]
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=53444681.1070902@archlinux.org \
--to=thomas@archlinux.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.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).