From: Philippe Bergheaud <felix@linux.vnet.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: philippe.bergheaud@fr.ibm.com, mikey@neuling.org,
amodra@gmail.com, rostedt@goodmis.org, ulrich.weigand@de.ibm.com,
mjw@linux.vnet.ibm.com, Anton Blanchard <anton@samba.org>,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [git pull] Please pull abiv2 branch
Date: Tue, 29 Apr 2014 11:38:33 +0200 [thread overview]
Message-ID: <535F7319.8030201@linux.vnet.ibm.com> (raw)
In-Reply-To: <877g69t1my.fsf@rustcorp.com.au>
Rusty Russell wrote:
> Philippe Bergheaud <felix@linux.vnet.ibm.com> writes:
>
>>Anton Blanchard wrote:
>>
>>>Here are the ABIv2 patches rebased against 3.15-rc2.
>>
>>After recompiling 3.15-rc2 with the ABIv2 patches,
>>I see the following line in Modules.symvers:
>>
>> 0x00000000 TOC. vmlinux EXPORT_SYMBOL
>>
>>Kernel will not load modules because TOC. has no CRC.
>>Is this expected ? Shouldn't TOC. have a CRC ?
>
>
> What happens when you try to load a module? It should work...
My mistake, sorry: kernel 3.15-rc2 crashes at boot, in the SLES12
Beta5 environment that I am using, before any module load attempt.
The problem happens with the SLES12 kernel of the day 3.12.17,
plus the backported ABIv2 patch set. Boot fails with:
kernel: ibmveth: no symbol version for TOC.
kernel: ibmveth: Unknown symbol TOC. (err -22)
kernel: scsi_mod: no symbol version for TOC.
kernel: scsi_mod: Unknown symbol TOC. (err -22)
In the rescue shell, repeating a plain modprobe fails again:
:/# modprobe scsi_mod
modprobe: ERROR: could not insert 'scsi_mod': Invalid argument
And finally, modprobe succeeds with --force:
:/# modprobe --force scsi_mod
scsi_mod: module has bad taint, not creating trace events
Philippe
prev parent reply other threads:[~2014-04-29 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 2:49 [git pull] Please pull abiv2 branch Anton Blanchard
2014-04-28 14:39 ` Philippe Bergheaud
2014-04-28 23:46 ` Alan Modra
2014-04-29 0:33 ` Rusty Russell
2014-04-29 9:38 ` Philippe Bergheaud [this message]
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=535F7319.8030201@linux.vnet.ibm.com \
--to=felix@linux.vnet.ibm.com \
--cc=amodra@gmail.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mjw@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=philippe.bergheaud@fr.ibm.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=ulrich.weigand@de.ibm.com \
/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.