linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alban Browaeys <alban.browaeys@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Unable to boot linux-next build
Date: Wed, 19 Oct 2016 17:15:02 +0200	[thread overview]
Message-ID: <1476890102.2367.3.camel@gmail.com> (raw)
In-Reply-To: <26c842c8-3c0a-d857-d11f-d334b96965d7@gmail.com>

Le dimanche 11 septembre 2016 à 20:00 +0200, Quentin Lambert a écrit :
> 
> On 09/09/2016 10:31, Quentin Lambert wrote:
> >   I have been trying to build and boot the last version available
> > on linux-next.
> >   During the build I am being prompted with "has no CRC!" warnings
> > for a bunch
> >   of modules.

There is a thread about this issue, with patches on the list (lkml)
titled "[GIT PULL] kbuild changes for v4.9-rc1" starting on Mon, 17 Oct
2016, with initial author "Michal Marek".

To sum up, you could disable CONFIG_MODVERSIONS in your config or
downgrade binutils to <= 2.26 or revert 784d5699eddc ("x86: move
exports to actual definitions")  or apply the two patches from the
above thread if on x86:

- first one : from Nicholas Piggin for all archs:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1250340.htm
l

- second from Adam Borowski , x86 specific bits :
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1250599.htm
l

      reply	other threads:[~2016-10-19 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09  8:31 Unable to boot linux-next build Quentin Lambert
2016-09-11 18:00 ` Quentin Lambert
2016-10-19 15:15   ` Alban Browaeys [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=1476890102.2367.3.camel@gmail.com \
    --to=alban.browaeys@gmail.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).