From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Michal Marek <mmarek@suse.com>
Cc: linux-kernel@vger.kernel.org,
Arthur Marsh <arthur.marsh@internode.on.net>
Subject: Re: 'kbuild' merge before 4.9-rc1 breaks build and boot
Date: Mon, 24 Oct 2016 07:21:42 +0200 [thread overview]
Message-ID: <a30e0a14-ad50-f193-3816-9258af69be85@hartkopp.net> (raw)
In-Reply-To: <4c04b846-3da8-dc42-4fa6-30f72a5c2437@hartkopp.net>
Hello Michal,
your latest patch doesn't help on my system:
http://git.kernel.org/cgit/linux/kernel/git/mmarek/kbuild.git/commit/?h=rc-fixes&id=989cea5c14be024e879c0055dc6d033680a52610
Regards,
Oliver
On 10/21/2016 06:23 PM, Oliver Hartkopp wrote:
> Hello Michal,
>
> I waited some days for a fix - but obviously no one else has this
> problem so far ...
>
> This merge
>
> "Merge branch 'kbuild' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild"
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=84d69848c97faab0c25aa2667b273404d2e2a64a
>
>
> creates a bunch of warnings on my system and the built kernel does not
> boot (it complains about a missing root fs).
>
> In the build process some .ko files are built fine and some don't:
>
> (..)
> MODPOST 176 modules
> AS arch/x86/boot/compressed/efi_thunk_64.o
> GZIP arch/x86/boot/compressed/vmlinux.bin.gz
> CC arch/x86/boot/compressed/misc.o
> 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!
> WARNING: "_copy_to_user" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "memset" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "__put_user_1" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "__put_user_4" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "__fentry__" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "memcpy" [sound/usb/snd-usb-audio.ko] has no CRC!
> WARNING: "__fentry__" [sound/soundcore.ko] has no CRC!
> (..)
> WARNING: "__fentry__" [arch/x86/crypto/crc32c-intel.ko] has no CRC!
> WARNING: "__fentry__" [arch/x86/crypto/crc32-pclmul.ko] has no CRC!
> WARNING: "__fentry__" [arch/x86/crypto/aesni-intel.ko] has no CRC!
> WARNING: "__fentry__" [arch/x86/crypto/aes-x86_64.ko] has no CRC!
> CC arch/x86/crypto/aes-x86_64.mod.o
> CC arch/x86/crypto/aesni-intel.mod.o
> CC arch/x86/crypto/crc32-pclmul.mod.o
> CC arch/x86/crypto/crc32c-intel.mod.o
> (..)
>
> When reverting the entire pull with
>
> git diff 84d69848c97faab0c25aa2667b273404d2e2a64a
> d4d24d2d0a7ea3b62efd7336bfc2344e29b36bc5 | patch -p1
>
> everything is ok again.
>
> My system is a Debian Stretch.
> gcc version 6.2.0 20161010 (Debian 6.2.0-6)
>
> .config is attached - in the case I have an unusual one from your
> perspective.
>
> Regards,
> Oliver
next prev parent reply other threads:[~2016-10-24 5:22 UTC|newest]
Thread overview: 16+ 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 [this message]
2016-10-27 15:42 ` Peter Wu
2016-11-07 19:10 ` Vince Weaver
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 15:04 ` Peter Wu
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=a30e0a14-ad50-f193-3816-9258af69be85@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.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.