From owner-freebsd-current@freebsd.org Tue May 31 00:26:51 2016 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 2197EB532F5 for ; Tue, 31 May 2016 00:26:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0CBEF113E for ; Tue, 31 May 2016 00:26:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 085CAB532F4; Tue, 31 May 2016 00:26:51 +0000 (UTC) Delivered-To: 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 0803BB532F3 for ; Tue, 31 May 2016 00:26:51 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E01DD113D; Tue, 31 May 2016 00:26:50 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 8FBB717DC; Tue, 31 May 2016 00:26:50 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 31 May 2016 00:26:49 +0000 From: Glen Barber To: David Wolfskill Cc: current@freebsd.org, Konstantin Belousov , bdrewery@freebsd.org Subject: Re: 11.0 -r300944 build attempted WITH_META_MODE failed [amd64 targeting powerpc64 via devel/powerpc64-gcc use] Message-ID: <20160531002649.GW80759@FreeBSD.org> References: <20160530185227.GZ1080@albert.catwhisker.org> <20160531002335.GA1080@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="O7hm+SMpb/lu0d4d" Content-Disposition: inline In-Reply-To: <20160531002335.GA1080@albert.catwhisker.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 31 May 2016 00:26:51 -0000 --O7hm+SMpb/lu0d4d Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 30, 2016 at 05:23:35PM -0700, David Wolfskill wrote: > On Mon, May 30, 2016 at 11:52:27AM -0700, David Wolfskill wrote: > > ... > > > > May 30 11:29:31 g1-252 root: /etc/rc: WARNING: Unable to load kerne= l module linux64 > > > > May 30 11:29:31 g1-252 kernel: KLD linux64.ko: depends on kernel - = not available or version mismatch > > > > May 30 11:29:31 g1-252 kernel: linker_load_file: Unsupported file t= ype > > >=20 > > > Your kernel was built from older sources than you used to build the n= vidia > > > module. I mean, the kernel headers used for the module build where > > > updated comparing with binaries that are installed into /boot/kernel. > >=20 > > Hmmm... I'm ... unlcear ... on how that could have happened. > > ... >=20 > Turns out that Bryan Drewery hit it (in a different thread): >=20 > On Mon, May 30, 2016 at 08:29:40AM -0700, Bryan Drewery wrote: > > This failure is not likely related to META_MODE. > >=20 > > I should have mentioned that to enable META_MODE after not having it on > > you should do a 'make cleanworld' first. > > .... >=20 > Given that hint, in my r300994 source tree, I first did: >=20 > cd /usr/src && make cleanworld >=20 > then re-built everything again (while Spouse and I were at a neighbor's > place for a cookout).... >=20 > On reboot, everything looks good, and linux64.ko (and nvidia.ko) are > loaded: >=20 > g1-252(11.0)[1] uname -a > FreeBSD g1-252.catwhisker.org 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #0 r300994= M/300994:1100115: Mon May 30 14:42:29 PDT 2016 root@g1-252.catwhisker.o= rg:/common/S4/obj/usr/src/sys/CANARY amd64 > g1-252(11.0)[2] kldstat=20 > Id Refs Address Size Name > 1 37 0xffffffff80200000 1e074a8 kernel > 2 1 0xffffffff82009000 232f8 geom_eli.ko > 3 2 0xffffffff8202d000 9d6d8 linux.ko > 4 4 0xffffffff820cb000 d1f0 linux_common.ko > 5 1 0xffffffff820d9000 4c50 coretemp.ko > 6 1 0xffffffff820de000 546b0 iwn5000fw.ko > 7 1 0xffffffff82133000 b67b50 nvidia.ko > 8 1 0xffffffff82c9b000 b838 filemon.ko > 9 1 0xffffffff82e21000 f01c tmpfs.ko > 10 1 0xffffffff82e31000 595a fdescfs.ko > 11 1 0xffffffff82e37000 a9e8 linprocfs.ko > 12 1 0xffffffff82e42000 39672 linux64.ko > g1-252(11.0)[3]=20 >=20 >=20 > Sorry for the false alarm. >=20 I'd much prefer a false alarm over an unreported true alarm. :-) Thanks for the followup, glad it is working now. Glen --O7hm+SMpb/lu0d4d Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXTNpDAAoJEAMUWKVHj+KTg4sP/icCwTTWdy1ud8bfqm7FG81c hCaY1nV+ZpxCO2q3JuqPsGlmLoQx0Ej25Yu0hCqSHAwPd0yFw4uZb+nMcZorNuEp nGZqQhv02ORRkn9U1ecVyERH3syQ8bLIQq+QX/BsUJDTCZelMnxR5oy4NFBz4U3v DTdJgSYUCEtgawgbEGsKuYdLZlvh3H14ERGGF2vYV+1c1JcXxlDscvlWlcbO7CCA OTDPAKZqibv6OC+UALUGBzbu566+ZRGuntAON3/k+3vjjRtqMfY5jCe9NiK4yRAq J6aTPD/qSrIJ04740NN2N7RAs+bTpcZr98NQiR6UUh+2lIxm8C+cyNGyFLHeY2HO Gs1rsJggOz3rn0pZPx9OEZR8XaHcMeQ2HAJQe5P9RabAN/8Iij4YBQMFtmK7uKi7 skz/LIkBnOEZIMgSdjosBmkJM7+PT+7KfxBZLyKpAFlV8OICAmRNQajyWw2E8PR2 7a/0Lm/x+UJXDV1trUx+aMnGvaiH8qaPlIUvLfpAKv0FWsdq2R613YuleeoU+Mdc uv1GaXAXTr2Xzm/IMMxhrR58CPfsFBLsLG7VDTUpX8QyOPjb+2QeWdyj+IZfNrBg Ao6reeS3Jn48i3OQrZX7DBacfYyqTKUmm7p3qnweARC8SOTVVJqbpwsqEr4i9G1U dQra1D2Vh5xqRz19GnZL =Liy8 -----END PGP SIGNATURE----- --O7hm+SMpb/lu0d4d--