Date: Wed, 6 Apr 2011 20:03:05 -0400 From: Andrew Duane <aduane@juniper.net> To: Warner Losh <imp@bsdimp.com> Cc: "mips@freebsd.org" <mips@FreeBSD.org> Subject: RE: Trouble making a filesystem Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB52F1950E8@EMBX01-WF.jnpr.net> In-Reply-To: <C8BE6153-5861-4E54-90EC-B84A96FA9C5F@bsdimp.com> References: <AC6674AB7BC78549BB231821ABF7A9AEB52FBD7A34@EMBX01-WF.jnpr.net>, <C8BE6153-5861-4E54-90EC-B84A96FA9C5F@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I was trying to follow the instructions on the MIPS wiki page, but they do = seem to be volatile. I will check my build setup tomorrow and see what I ha= ve for TARGET and TARGET_ARCH and all. I didn't do a distribute step, I was= trying to this afternoon and it just failed completely. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 ________________________________________ From: Warner Losh [imp@bsdimp.com] Sent: Wednesday, April 06, 2011 5:16 PM To: Andrew Duane Cc: mips@freebsd.org Subject: Re: Trouble making a filesystem On Apr 6, 2011, at 2:58 PM, Andrew Duane wrote: > I'm having trouble making a working filesystem for my OCTEON1 kernel to r= un on. I do a "buildworld", but there are three problems: > > 1) Most of the executables won't execute, they give "Exec format error". = The problem seems to be with dynamically linked executables. When I rebuilt= "/bin/sh" as a static executable, it worked OK. I guess I could manually f= ix every Makefile to use static linking, but that seems absurd. I've not seen this. However, I did "recently" change the way to build mips= from TARGET_ARCH=3Dmips to TARGET_ARCH=3Dmips64eb. Maybe that's the issue= ? > 2) Some things aren't being populated. For example, that the only thing i= n the buildworld output of etc is sendmail. In the installworld output ther= e are a handful of subdirectorties, but no "rc" files. Do you have a make distribution step in your build scripts? That's what po= pulates the system with most of /etc and a few other oddities... > 3) Eventually, the kernel tips over with: > > panic: sched_priority: invalid priority 231: nice 0, ticks 1955000 ftic= k 14022821 ltick 14023821 tick pri 59 > > Any thoughts on what I'm missing? Haven't seen that, but I've not run FreeBSD/mips from source built newer th= an mid January. Maybe that's a clue? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC6674AB7BC78549BB231821ABF7A9AEB52F1950E8>