From owner-freebsd-arm@FreeBSD.ORG Wed Dec 31 19:08:55 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18AE3619 for ; Wed, 31 Dec 2014 19:08:55 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E288B6442F for ; Wed, 31 Dec 2014 19:08:54 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Y6O30-00090K-Ct; Wed, 31 Dec 2014 18:31:06 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sBVIV5n9041372; Wed, 31 Dec 2014 11:31:05 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Fnh9n5FdsP25j95FRQxt9 Message-ID: <1420050665.1018.315.camel@freebsd.org> Subject: Re: BBB translation fault panic with "kldload" From: Ian Lepore To: Keith White Date: Wed, 31 Dec 2014 11:31:05 -0700 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 19:08:55 -0000 On Wed, 2014-12-31 at 08:41 -0500, Keith White wrote: > I get a kernel panic when trying to use kernel modules with recent > BBB kernels. > > Here's what happens when I try to "kldload nullfs" with a freshly > built r276468: > > ======================= [...] Just a quick followup... as of r276047 modules are broken on armv6. This is also the root cause of the problem reported in the thread "vm_fault during BBB-boot". Unfortunately, at this point we can't just revert that single change because lots of commits that have happened since then rely on it. So we're temporarily in a "-current is broken" state and will be until a fix is found. In the meantime, the 10-stable branch doesn't have this problem (and in general is more immune to this type of problem because code doesn't get moved there until it has had some testing), so using it is a viable option for folks who just need to get on with their lives. Or you can sync your -current source directory back to r276046. For those interested in the gory details... when we added -march=armv7 to the kernel compiles it allowed the compiler to start generating new more efficient movw/movt instructions to load an address into a register. It also emits new (for us) types of relocation info for those, and our old linker and runtime loader don't handle that kind of relocation info correctly in kernel modules. -- Ian