[Top] [All Lists]

RE: Init not working in 64-bit kernel

To: <>
Subject: RE: Init not working in 64-bit kernel
From: <>
Date: Fri, 17 Mar 2006 19:19:08 +0530
Cc: <>
Original-recipient: rfc822;
Thread-index: AcZJxVga7OOWTNLfTxiYaSxMZjf+BQAAbCaA
Thread-topic: Init not working in 64-bit kernel
        first thanx for ur reply.

All the following options are enabled in the kernel.


I've another doubt. Is it enough to set only the bits KX,SX and UX of
the status register to work in 64-bit mode?
Though I've used the cross compiler mips64_fp_be-gcc from MontaVista,
the generated vmlinux image seems to boot fine even without setting the
above bits.
I don't know if I'm operating in 32-bit or 64-bit mode.
But I've enabled 64-bit support in kernel configuration.


-----Original Message-----
From: Ralf Baechle []
Sent: Friday, March 17, 2006 6:49 PM
To: Vadivelan M
Subject: Re: Init not working in 64-bit kernel

On Fri, Mar 17, 2006 at 03:36:50PM +0530, wrote:

>       I'm porting a 64-bit linux kernel provided for a mips4
> 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
> Looking up port of RPC 100005/1 on
> 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:


And if you have an N32 root filesystem (unlikely) you also have to set

> 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 ;-)


The information contained in this e-mail message and in any annexure is
confidential to the  recipient and may contain privileged information. If you 
are not
the intended recipient, please notify the sender and delete the message along 
any annexure. You should not disclose, copy or otherwise use the information 
in the message or any annexure. Any views expressed in this e-mail are those of 
individual sender except where the sender specifically states them to be the 
views of
SoCrates Software India Pvt Ltd., Bangalore.

<Prev in Thread] Current Thread [Next in Thread>