From: Ralf Baechle <ralf@linux-mips.org>
To: Vadivelan@soc-soft.com
Cc: linux-mips@linux-mips.org
Subject: Re: Init not working in 64-bit kernel
Date: Fri, 17 Mar 2006 13:18:50 +0000 [thread overview]
Message-ID: <20060317131850.GA3771@linux-mips.org> (raw)
In-Reply-To: <4BF47D56A0DD2346A1B8D622C5C5902C01524CFE@soc-mail.soc-soft.com>
On Fri, Mar 17, 2006 at 03:36:50PM +0530, Vadivelan@soc-soft.com wrote:
> I'm porting a 64-bit linux kernel provided for a mips4
> architecture to a mips3 target board. The existing NFS root file system
> has been compiled for a 64-bit mips4 architecture.
> If I mount this file system, the init does not run.
> After mounting the filesystem, I get the following messages and the
> kernel hangs.
>
> -------------------------------------------------
> Looking up port of RPC 100003/2 on 192.168.5.93
> Looking up port of RPC 100005/1 on 192.168.5.93
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 132k freed
That's a rather generic kind of death uppon entry of userspace sympthom,
so I cannot really give alot of advice other than below:
> I also tried to mount a 32-bit working NFS root filesystem.
> Still I get the same problem. I thought 32-bit binaries will execute
> fine in 64-bit kernel.
They do - but you need to enable 32-bit compatibility:
CONFIG_MIPS32_COMPAT=y
CONFIG_MIPS32_O32=y
And if you have an N32 root filesystem (unlikely) you also have to set
CONFIG_MIPS32_N32=y.
> Do I have to recompile the binutils and glibc for my target file system?
No. The entire software should just work.
> Kindly ignore the confidentiality notice attached at the end of the
> mail. It is an automatically generated one and I cannot remove it.I'm
> extremely sorry for the inconvenience.
We're fabulous at ignoring things ;-)
Ralf
next prev parent reply other threads:[~2006-03-17 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 10:06 Init not working in 64-bit kernel Vadivelan
2006-03-17 10:06 ` Vadivelan
2006-03-17 13:18 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 13:49 Vadivelan
2006-03-17 13:49 ` Vadivelan
2006-03-17 14:12 ` Ralf Baechle
2006-03-20 12:35 Vadivelan
2006-03-20 12:35 ` Vadivelan
2006-03-20 13:14 ` Ralf Baechle
2006-03-20 14:38 ` Atsushi Nemoto
2006-04-11 4:20 Vadivelan
2006-04-11 4:20 ` Vadivelan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060317131850.GA3771@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Vadivelan@soc-soft.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox