Date: Tue, 10 Aug 2010 19:56:58 +0530 From: waynegong L <waynegong83@gmail.com> To: "Jayachandran C." <c.jayachandran@gmail.com> Cc: freebsd-mips@freebsd.org Subject: Re: HEADSUP : n64 changes in HEAD. Message-ID: <AANLkTim8r9xEMYz9PO%2BYwYEyVphQQ%2Bd4vZFhFZsVE9Hx@mail.gmail.com> In-Reply-To: <AANLkTi=2x%2BSkzUZLL9wWbfsCHL4NfwUwFonop2_zwj6j@mail.gmail.com> References: <AANLkTimykzp%2Bv-x1V_u%2Bp3Q9BUW=vdbv84D0e%2BTwJ1Em@mail.gmail.com> <AANLkTimXKCPUWvmitNADEakCRxDks51Bd3-0MqhR=kwb@mail.gmail.com> <AANLkTikiTun2GXNnLs%2BwftBBJqjaMr73CXGghbgcLkW5@mail.gmail.com> <AANLkTi=xnCRZPdM8b0kwLjSM_0RPMLf2D2wZp%2BHgFFYy@mail.gmail.com> <AANLkTi=2x%2BSkzUZLL9wWbfsCHL4NfwUwFonop2_zwj6j@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Hi Jayachandran, > On N64 userspace&kernel, During booting ENOENT error is reported from devfs_fixup(), as below. This error was not seen with previous revisions atleast on my Octeon board. Trying to mount root from ufs:/dev/md0 *Lookup of /dev for devfs, error: 2* start_init: trying /sbin/init panic: userret: Returning with 1 locks held. In devfs_fixup, NDINIT is invoked to intialize namei components and, subsequently namei() is invoked to look for /dev directory. But this lookup operation failed in my case. Are any locks acquired in this function not being released and is that causing the issue? Other day, i tried building the sources for n32 ABI, but the kernel build failed with below error. My config file was OCTEON1-32 * Assembler messages: linking kernel.debug hack.So: could not read symbols: Invalid operation* My env. TARGET=mips TARGET_BIG_ENDIAN=y TARGET_CPUTYPE=mips64 TARGET_ARCH=mips TARGET_ABI=n32 Thanks, Wayne. > > Looks like the kernel and userspace are 64bit, and it crashed on > getting into userspace the first time. I am really not sure what > could have caused that lock to be held... > > Have you checked if the exact same source comes up on 32 bit > compilation? This may be worth checking first. After that, may be > enabling debug in trap.c may be a good way to see if the exceptions > generated while jumping to userspace are handled correctly. > > JC. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim8r9xEMYz9PO%2BYwYEyVphQQ%2Bd4vZFhFZsVE9Hx>