From: Roman Fiala <roman.fiala.novy@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 4.6 - failing compilation Vmware modules
Date: Mon, 30 May 2016 17:14:24 +0200 [thread overview]
Message-ID: <574C58D0.7060800@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
Hello,
this is the first time, when I would like to report kernel problem.
When switching my Debian 8 to kernel 4.4.x, I thought vmware modules
compilation will work smoothly forewer. Unfortunately when I tried 4.5.5
and 4.6, both failed on vmnet module compilation, moreover 4.6 failed
also on module vmmon.
Attaching the log from modules compilation.
Please navigate me, how to submit this one error or submit it instead of me.
Thank you very much,
Roman
[-- Attachment #2: vmware-3997.log --]
[-- Type: text/x-log, Size: 12554 bytes --]
2016-05-30T17:08:50.871+02:00| vthread-4| I125: Log for VMware Workstation pid=3997 version=12.1.1 build=build-3770994 option=Release
2016-05-30T17:08:50.871+02:00| vthread-4| I125: The process is 64-bit.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2016-05-30T17:08:50.871+02:00| vthread-4| I125: Host is Linux 4.6.0-customkernel Debian GNU/Linux stable-updates (sid)
2016-05-30T17:08:50.870+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2016-05-30T17:08:50.870+02:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: PREF Unable to check permissions for preferences file.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.
2016-05-30T17:08:50.871+02:00| vthread-4| I125: PREF Failed to load user preferences.
2016-05-30T17:08:50.984+02:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-3997.log
2016-05-30T17:08:50.991+02:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-30T17:08:50.991+02:00| vthread-4| I125: Created new pathsHash.
2016-05-30T17:08:50.991+02:00| vthread-4| I125: Setting header path for 4.6.0-customkernel to "/lib/modules/4.6.0-customkernel/build/include".
2016-05-30T17:08:50.991+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:50.991+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:50.991+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:50.991+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:50.995+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:50.995+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.048+02:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-customkernel/build/Module.symvers
2016-05-30T17:08:51.048+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-customkernel/build/Module.symvers.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Read 17106 symbol versions
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Reading in info for the vmmon module.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Reading in info for the vmnet module.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Reading in info for the vmblock module.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Reading in info for the vmci module.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Reading in info for the vsock module.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Setting vsock to depend on vmci.
2016-05-30T17:08:51.063+02:00| vthread-4| I125: Invoking modinfo on "vmmon".
2016-05-30T17:08:51.064+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.064+02:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-30T17:08:51.065+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.065+02:00| vthread-4| I125: Invoking modinfo on "vmblock".
2016-05-30T17:08:51.066+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.066+02:00| vthread-4| I125: Invoking modinfo on "vmci".
2016-05-30T17:08:51.068+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.068+02:00| vthread-4| I125: Invoking modinfo on "vsock".
2016-05-30T17:08:51.069+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2016-05-30T17:08:51.078+02:00| vthread-4| I125: to be installed: vmmon status: 0
2016-05-30T17:08:51.078+02:00| vthread-4| I125: to be installed: vmnet status: 0
2016-05-30T17:08:51.088+02:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-30T17:08:51.088+02:00| vthread-4| I125: Setting header path for 4.6.0-customkernel to "/lib/modules/4.6.0-customkernel/build/include".
2016-05-30T17:08:51.088+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:51.088+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:51.088+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:51.088+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:51.093+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:51.093+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.146+02:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-customkernel/build/Module.symvers
2016-05-30T17:08:51.146+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-customkernel/build/Module.symvers.
2016-05-30T17:08:51.160+02:00| vthread-4| I125: Read 17106 symbol versions
2016-05-30T17:08:51.160+02:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.6.0-customkernel/build/include
2016-05-30T17:08:51.160+02:00| vthread-4| I125: Update kernel header path to /lib/modules/4.6.0-customkernel/build/include
2016-05-30T17:08:51.160+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:51.160+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:51.160+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:51.160+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:51.165+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:51.165+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.166+02:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
2016-05-30T17:08:51.168+02:00| vthread-4| I125: Got gcc version "5.3.1".
2016-05-30T17:08:51.168+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-30T17:08:51.168+02:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
2016-05-30T17:08:51.170+02:00| vthread-4| I125: Got gcc version "5.3.1".
2016-05-30T17:08:51.170+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-30T17:08:51.171+02:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.6.0-customkernel".
2016-05-30T17:08:51.171+02:00| vthread-4| I125: No matching PBM set was found for kernel "4.6.0-customkernel".
2016-05-30T17:08:51.171+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-30T17:08:51.171+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:51.171+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:51.171+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:51.171+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:51.175+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:51.175+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.176+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2016-05-30T17:08:51.176+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:51.176+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:51.176+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:51.176+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:51.181+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:51.181+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.181+02:00| vthread-4| I125: Using temp dir "/tmp".
2016-05-30T17:08:51.182+02:00| vthread-4| I125: Obtaining info using the running kernel.
2016-05-30T17:08:51.182+02:00| vthread-4| I125: Setting header path for 4.6.0-customkernel to "/lib/modules/4.6.0-customkernel/build/include".
2016-05-30T17:08:51.182+02:00| vthread-4| I125: Validating path "/lib/modules/4.6.0-customkernel/build/include" for kernel release "4.6.0-customkernel".
2016-05-30T17:08:51.182+02:00| vthread-4| I125: Failed to find /lib/modules/4.6.0-customkernel/build/include/linux/version.h
2016-05-30T17:08:51.182+02:00| vthread-4| I125: /lib/modules/4.6.0-customkernel/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2016-05-30T17:08:51.182+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2016-05-30T17:08:51.186+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.6.0-customkernel".
2016-05-30T17:08:51.186+02:00| vthread-4| I125: The header path "/lib/modules/4.6.0-customkernel/build/include" for the kernel "4.6.0-customkernel" is valid. Whoohoo!
2016-05-30T17:08:51.239+02:00| vthread-4| I125: found symbol version file /lib/modules/4.6.0-customkernel/build/Module.symvers
2016-05-30T17:08:51.239+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.6.0-customkernel/build/Module.symvers.
2016-05-30T17:08:51.254+02:00| vthread-4| I125: Read 17106 symbol versions
2016-05-30T17:08:51.254+02:00| vthread-4| I125: Invoking modinfo on "vmmon".
2016-05-30T17:08:51.255+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.255+02:00| vthread-4| I125: Invoking modinfo on "vmnet".
2016-05-30T17:08:51.256+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2016-05-30T17:08:51.501+02:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.6.0-customkernel/misc/vmmon.ko".
2016-05-30T17:08:51.502+02:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2016-05-30T17:08:51.509+02:00| vthread-4| I125: Successfully extracted the vmmon source.
2016-05-30T17:08:51.509+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-yMUq6i/vmmon-only auto-build HEADER_DIR=/lib/modules/4.6.0-customkernel/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2016-05-30T17:08:52.918+02:00| vthread-4| W115: Failed to build vmmon. Failed to execute the build command.
2016-05-30T17:08:52.919+02:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.6.0-customkernel/misc/vmnet.ko".
2016-05-30T17:08:52.920+02:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2016-05-30T17:08:52.926+02:00| vthread-4| I125: Successfully extracted the vmnet source.
2016-05-30T17:08:52.926+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-yMUq6i/vmnet-only auto-build HEADER_DIR=/lib/modules/4.6.0-customkernel/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2016-05-30T17:08:54.118+02:00| vthread-4| W115: Failed to build vmnet. Failed to execute the build command.
next reply other threads:[~2016-05-30 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 15:14 Roman Fiala [this message]
2016-05-30 19:44 ` Kernel 4.6 - failing compilation Vmware modules Valdis.Kletnieks
2016-05-30 19:51 ` Roman Fiala
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=574C58D0.7060800@gmail.com \
--to=roman.fiala.novy@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).