From: Vince Weaver <vincent.weaver@maine.edu>
To: Peter Wu <peter@lekensteyn.nl>
Cc: Michal Marek <mmarek@suse.com>, Al Viro <viro@zeniv.linux.org.uk>,
Oliver Hartkopp <socketcan@hartkopp.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: 'kbuild' merge before 4.9-rc1 breaks build and boot
Date: Mon, 7 Nov 2016 14:10:12 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.1611071408040.24418@macbook-air> (raw)
In-Reply-To: <20161027154202.GE27017@al>
On Thu, 27 Oct 2016, Peter Wu wrote:
> I can confirm Olivers issue, the current mainline kernel fails to boot
> on kernels with CONFIG_MODVERSIONS=y. Bisection points to:
>
> commit 784d5699eddc55878627da20d3fe0c8542e2f1a2
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Mon Jan 11 11:04:34 2016 -0500
> > WARNING: "memset" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > WARNING: "__fentry__" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > WARNING: "memcpy" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > WARNING: "__sw_hweight32" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
Has any progress been made with this problem?
I'm also encountering it on my debian-unstable box on any kernel more
recent than 4.9-rc1 (up to and including 4.9-rc4). I am glad someone
managed to isolate it as I was unable to get a clean bisect.
Vince
next prev parent reply other threads:[~2016-11-07 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 16:23 'kbuild' merge before 4.9-rc1 breaks build and boot Oliver Hartkopp
2016-10-24 5:21 ` Oliver Hartkopp
2016-10-27 15:42 ` Peter Wu
2016-11-07 19:10 ` Vince Weaver [this message]
2016-11-07 21:39 ` Peter Wu
2016-11-08 1:33 ` Nicholas Piggin
2016-11-20 18:26 ` Peter Wu
2016-11-21 5:49 ` Nicholas Piggin
2016-11-21 6:39 ` [PATCH resend] kbuild: provide include/asm/asm-prototypes.h for x86 Adam Borowski
2016-11-21 7:27 ` Nicholas Piggin
2016-11-21 8:00 ` Peter Wu
2016-11-21 14:52 ` [PATCH reworded] x86/kbuild: enable modversions for symbols exported from asm Adam Borowski
2016-11-21 15:04 ` Peter Wu
2016-11-21 16:49 ` Oliver Hartkopp
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=alpine.DEB.2.20.1611071408040.24418@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=peter@lekensteyn.nl \
--cc=socketcan@hartkopp.net \
--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).