From owner-freebsd-current@freebsd.org Wed Apr 4 21:13:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C228BF76C04 for ; Wed, 4 Apr 2018 21:13:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48AB87434F; Wed, 4 Apr 2018 21:13:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w34LDFZ8035045 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 4 Apr 2018 14:13:15 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w34LDFro035044; Wed, 4 Apr 2018 14:13:15 -0700 (PDT) (envelope-from sgk) Date: Wed, 4 Apr 2018 14:13:15 -0700 From: Steve Kargl To: Ed Maste Cc: FreeBSD Current Subject: Re: Can't load linux64.ko module Message-ID: <20180404211315.GA35006@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180403162600.GA23894@troutmask.apl.washington.edu> <20180404190902.GA34292@troutmask.apl.washington.edu> <20180404201955.GA34736@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180404201955.GA34736@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Apr 2018 21:13:18 -0000 On Wed, Apr 04, 2018 at 01:19:55PM -0700, Steve Kargl wrote: > On Wed, Apr 04, 2018 at 12:09:02PM -0700, Steve Kargl wrote: > > > > kernel config file contains > > > > options COMPAT_LINUX32 > > options COMPAT_LINUXKPI > > options LINPROCFS > > > > When booting, the kernel tries to load the module. A manual > > loading of the module results in > > > > % kldload /boot/kernel/linux64.ko > > kldload: an error occurred while loading module /boot/kernel/linux64.ko. > > Please check dmesg(8) for more details. > > sleepdirt:fvwm:root[203] dmesg | tail -2 > > link_elf_obj: symbol elf64_linux_vdso_fixup undefined > > linker_load_file: /boot/kernel/linux64.ko - unsupported file type > > > > Now, that I look at /sys/amd64/conf/NOTES again, I find that > > there is a COMPAT_LINUX as well as the COMPAT_LINUX32. I must > > have conflated that two options into being the same thing. > > OK, so where is elf64_linux_vdso_fixup suppose to come from? cd /boot/kernel foreach i (*.ko) nm $i | grep linux_vdso_fixup end 0000000000018f40 t elf32_linux_vdso_fixup 0000000000017cd0 t elf32_linux_vdso_fixup U elf64_linux_vdso_fixup nm kernel | grep linux_vdso ffffffff80f3cb88 d __set_sysinit_set_sym_elf_linux_vdso_init_sys_init ffffffff80f3e140 d __set_sysuninit_set_sym_elf_linux_vdso_uninit_sys_uninit ffffffff80a3eae0 T elf32_linux_vdso_fixup ffffffff80a3ebe0 T elf32_linux_vdso_reloc ffffffff80a3e9e0 T elf32_linux_vdso_sym_init ffffffff81180e70 B elf32_linux_vdso_syms ffffffff80f32ae0 d elf_linux_vdso_init_sys_init ffffffff80f32af8 d elf_linux_vdso_uninit_sys_uninit ffffffff80a292d0 t linux_vdso_deinstall ffffffff80a29210 t linux_vdso_install -- Steve