[Top] [All Lists]

RE: Init not working in 64-bit kernel

To: <>
Subject: RE: Init not working in 64-bit kernel
From: <>
Date: Mon, 20 Mar 2006 18:05:51 +0530
Cc: <>
Original-recipient: rfc822;
Thread-index: AcZJzMjTawNWPeDRTf+gdnxFkM91wgCTeVvg
Thread-topic: Init not working in 64-bit kernel
Hi Ralf,
        I've attached the kernel dmesg below for ur reference.


Linux version 2.6.10_mvl401-bcm91250-mips64_fp_be (root@ramkumar) (gcc
version 3
.4.3 (MontaVista 3.4.3- 2005-12-18)) #127 Mon Mar 20
18:00:26 IST
CPU revision is: 00002d30
FPU revision is: 00002d30

rbtx4938_ce_base[0] : 0x1c000000
rbtx4938_ce_base[2] : 0x17f00000
rbtx4938_ce_base[7] : 0x17e00000TX4938 -- 300MHz(M25MHz) CRIR:49380010
427905 PCFG:680000010fbf0100
TX4938 SDRAMC -- CR0:0000007e00000544 TR:35000830c
request resource for internal registers failed
PIOSEL: disabling both ata and nand selection
RBTX4938 --- FPGA(Rev f0) DIPSW:ff,f8
Determined physical RAM map:
 memory: 0000000008000000 @ 0000000000000000 (usable)
Built 1 zonelists
Kernel command line: console=ttyS0,38400 ip=dhcp root=/dev/nfs rw
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (31 instructions).
Synthesized TLB load handler fastpath (44 instructions).
Synthesized TLB store handler fastpath (44 instructions).
Synthesized TLB modify handler fastpath (43 instructions).
PID hash table entries: 1024 (order: 10, 32768 bytes)
Using 150.000 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Memory: 124192k/131072k available (2640k kernel code, 6776k reserved,
496k data,
 200k init, 0k highmem)
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
Checking for 'wait' instruction...  available.
Checking for the multiply/shift bug... no.
Checking for the daddi bug... no.
Checking for the daddiu bug... no.
desched cpu_callback 3/0000000000000000
ksoftirqd started up.
desched cpu_callback 2/0000000000000000
desched thread 0 started up.
NET: Registered protocol family 16
Can't analyze prologue code at ffffffff803907c8
Initializing Cryptographic API
Generic RTC Driver v1.07
TX39/49 Serial driver version 1.04
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)
ne.c:v1.10 9/23/94 Donald Becker (
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x17f20280: 00 60 0a 00 4d 80
eth0: RBHMA4X00/RTL8019 found at 0x17f20280, using IRQ 27.
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
NET: Registered protocol family 24
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Sending BOOTP requests . OK
IP-Config: Got BOOTP answer from, my address is
IP-Config: Complete:
      device=eth0, addr=, mask=,
     host=, domain=, nis-domain=(none),
     bootserver=, rootserver=,
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: 200k freed


It does not boot after this. I'm unable to trace the problem.
If u can plz let me know.


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

On Fri, Mar 17, 2006 at 07:19:08PM +0530, wrote:

> 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?

KX, SX and UX will be set by the kernel itself on startup.

SX doesn't actually matter because Linux doesn't use the supervisor

More for completness sake - there are some slight differences between
the various 64-bit processors if attempting to execute 64-bit
instructions or addresses on a processor configured to 32-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.

Always 64-bit mode on a 64-bit kernels - even for 32-bit software.
Always 32-bit mode on 32-bit kernels - even on 64-bit hardware.


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>