From owner-freebsd-current@freebsd.org  Wed Apr  4 21:34:55 2018
Return-Path: <owner-freebsd-current@freebsd.org>
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 A2A4AF78541
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed,  4 Apr 2018 21:34:55 +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 2E34B75558;
 Wed,  4 Apr 2018 21:34:55 +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 w34LYrCL035193
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 4 Apr 2018 14:34:53 -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 w34LYrBX035192;
 Wed, 4 Apr 2018 14:34:53 -0700 (PDT) (envelope-from sgk)
Date: Wed, 4 Apr 2018 14:34:53 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Ed Maste <emaste@freebsd.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Can't load linux64.ko module
Message-ID: <20180404213453.GA35165@troutmask.apl.washington.edu>
Reply-To: sgk@troutmask.apl.washington.edu
References: <20180403162600.GA23894@troutmask.apl.washington.edu>
 <CAPyFy2D7dkUO929htg4Qxu6jQXgc2M4J1fFtd2s_2gZ5wKK3-w@mail.gmail.com>
 <20180404190902.GA34292@troutmask.apl.washington.edu>
 <20180404201955.GA34736@troutmask.apl.washington.edu>
 <20180404211315.GA35006@troutmask.apl.washington.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180404211315.GA35006@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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2018 21:34:55 -0000

On Wed, Apr 04, 2018 at 02:13:15PM -0700, Steve Kargl wrote:
> 
> OK, so where is elf64_linux_vdso_fixup suppose to come from?
> 

The answer is compat/linux/linux_vdso.c where we find

#if defined(__i386__) || (defined(__amd64__) && defined(COMPAT_LINUX32))
#define __ELF_WORD_SIZE 32
#else
#define __ELF_WORD_SIZE 64
#endif

having COMPAT_LINUX32 in my kernel config file gives me
elf32_linux_vdso_fixup.  It seems that one cannot have
a kernel that supports both 32 and 64-bit linux software.

linux(4) states

     for an amd64 kernel use:

           options COMPAT_LINUX32

     Alternatively, to load the ABI as a module at boot time, place the
     following line in loader.conf(5):

           linux_load="YES"

It turns out that I have 'linux_load=YES" in /etc/loader.conf.
When I boot the kernel built with COMPAT_LINUX32 prevents 
the kldload of linux64.ko.

Oh well, learn something new everyday.

-- 
Steve