From owner-freebsd-current@freebsd.org Fri Jul 28 21:04:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4517DCF13F for ; Fri, 28 Jul 2017 21:04:59 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.geekisp.com", Issuer "mail.geekisp.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A0C4270EAA for ; Fri, 28 Jul 2017 21:04:59 +0000 (UTC) (envelope-from tyler@monkeypox.org) Received: (qmail 22333 invoked by uid 1003); 28 Jul 2017 20:58:16 -0000 Received: from unknown (HELO blackberry.coupleofllamas.com) (tyler@monkeypox.org@50.0.60.24) by mail.geekisp.com with (AES256-SHA encrypted) SMTP; 28 Jul 2017 20:58:16 -0000 Date: Fri, 28 Jul 2017 13:58:12 -0700 From: "R. Tyler Croy" To: Alexander Kabaev Cc: freebsd-current@freebsd.org Subject: Re: linux64.ko fails to load in -CURRENT Message-ID: <20170728205812.5luxebr6t2kjgshy@blackberry.coupleofllamas.com> References: <20170728155032.ok5jkeewzvbe3kti@blackberry.coupleofllamas.com> <20170728123810.3e25acd0@kan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fd2ce6rocvdn3rpk" Content-Disposition: inline In-Reply-To: <20170728123810.3e25acd0@kan> User-Agent: NeoMutt/20170113 (1.7.2) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Fri, 28 Jul 2017 21:05:00 -0000 --fd2ce6rocvdn3rpk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (replies inline) On Fri, 28 Jul 2017, Alexander Kabaev wrote: > On Fri, 28 Jul 2017 08:50:32 -0700 > "R. Tyler Croy" wrote: >=20 > > I have noticed this over the past couple weeks with my -CURRENT > > laptop that 64-bit linux compatibility is failing to load, and I'm > > not entirely sure why. My current kernel is based off of r321626. > >=20 > > When I run `kldload linux64` it fails with the following: > >=20 > > link_elf_obj: symbol elf64_linux_vdso_fixup undefined > > linker_load_file: /boot/kernel/linux64.ko - unsupported file type > >=20 > >=20 > > It's unclear to me whether this is old cruft sitting around, a > > regression, or something else entirely floating around my system. Any > > pointer would help :) > >=20 > >=20 > > Cheers > > - R. Tyler Croy >=20 > I am guessing you have COMPAT_LINUX in your kernel and 32bit emulation > is compiled into it. This does not work for linux64, one needs to build > all three required components as modules: COMPAT_LINUX32 was in the kernel configuration, guess I know that these thi= ngs are incompatible now :) I think the handbook notes on statically linking linux support should proba= bly be removed: - R. Tyler Croy ------------------------------------------------------ Code: Chatter: xmpp: rtyler@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F ------------------------------------------------------ --fd2ce6rocvdn3rpk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSQYoZaRujHSSvxiNcUJsfcP1HhbwUCWXulYgAKCRAUJsfcP1Hh bw+nAKCNapCTuZU78gH92yzsgiRjBWeeCgCeI9GMNJk78BMF+bUWj63/APVeQUs= =HWEj -----END PGP SIGNATURE----- --fd2ce6rocvdn3rpk--