RE: Instruction OCM

2008-05-20 Thread mojtaba
Actually there is no overlapping between IOCM and DDR. The IOCM region
addre4sses are:
PARAMETER C_BASEADDR = 0xc0a0
PARAMETER C_HIGHADDR = 0xc0a1
And the DDR addresses are:
PARAMETER C_MEM0_BASEADDR = 0x
PARAMETER C_MEM0_HIGHADDR = 0x0fff
Furthermore, if such a conflict existed, the synthesizer would have
identified it.


-Original Message-
From: Stephen Neuendorffer [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 19, 2008 6:59 PM
To: mojtaba; linuxppc-embedded@ozlabs.org
Subject: RE: Instruction OCM

The traps are down there in low memory.  trap 700 is probably the one
that deals with MMU exceptions.  My guess is your OCM region is
overlapping with the DDR memory containing that code.

Steve

 -Original Message-
 From: [EMAIL PROTECTED]
[mailto:linuxppc-embedded-
 [EMAIL PROTECTED] On Behalf Of mojtaba
 Sent: Monday, May 19, 2008 8:17 AM
 To: linuxppc-embedded@ozlabs.org
 Subject: Instruction OCM
 
 Dear all,
 
 I cannot run Linux when I have an instruction OCM in my design but,
without instruction OCM
 everything is fine. I tried to do some debugging. It seems that the
Linux memory management unit has
 a problem with that.  After entering the MMU initialization phase, it
suddenly jumps to address
 0x0700 it get stuck there. Is there anybody who have tried a
design with instruction OCM? Do I
 need to do special configuration for the Linux kernel?
 
 Regards,
 
 Mojtaba


This email and any attachments are intended for the sole use of the named
recipient(s) and contain(s) confidential information that may be
proprietary, privileged or copyrighted under applicable law. If you are not
the intended recipient, do not read, copy, or forward this email message or
any attachments. Delete this email message and any attachments immediately.


___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


RE: Instruction OCM

2008-05-20 Thread mojtaba
Thank you for your email. But what is the solution to that? I have seen this
in a thesis: 

when using the OCM buses to connect memory, we can only use virtual memory
as long as the virtual address is the same as the physical address, which is
conceptually
the same as using a system without MMU. Therefore porting Linux to a
system based on an OCM memory system is not possible

http://ce.et.tudelft.nl/publicationfiles/1367_700_thesis.pdf

Is that right? What do you suggest?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Sergey Temerkhanov
Sent: Monday, May 19, 2008 8:53 PM
To: linuxppc-embedded@ozlabs.org
Subject: Re: Instruction OCM

mojtaba wrote:

 Dear all,

 I cannot run Linux when I have an instruction OCM in my design but, 
 without instruction OCM everything is fine. I tried to do some 
 debugging. It seems that the Linux memory management unit has a 
 problem with that.  After entering the MMU initialization phase, it 
 suddenly jumps to address 0x0700 it get stuck there. Is there 
 anybody who have tried a design with instruction OCM? Do I need to do 
 special configuration for the Linux kernel?

 Regards,

 Mojtaba

 

 ___
 Linuxppc-embedded mailing list
 Linuxppc-embedded@ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Address 0x700 means invalid opcode exception.
If instruction OCM is same as data OCM (I think it's so) then any MMU 
mapping is not applicable to this region at all as OCM controller 
decodes virtual addresses bypassing any MMU mappings.
In your situation MMU maps virtual address of OCM to physical address 
containing some random data and CPU tries to execute it. So you get 
invalid opcode exception.
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Instruction OCM

2008-05-19 Thread mojtaba
Dear all,

I cannot run Linux when I have an instruction OCM in my design but, without
instruction OCM everything is fine. I tried to do some debugging. It seems
that the Linux memory management unit has a problem with that.  After
entering the MMU initialization phase, it suddenly jumps to address
0x0700 it get stuck there. Is there anybody who have tried a design with
instruction OCM? Do I need to do special configuration for the Linux kernel?


Regards,

Mojtaba

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Booting Linux from an ACE File

2008-05-16 Thread mojtaba
Dear all,

Could you please explain what happens exactly when Linux is booting from a
compact flash?

To my few knowledge, the Linux compressed image will be copied somewhere in
memory, will be uncompressed and the control will jump to the beginning
address of the Linux kernel.

Is there any boot loader that copies the Linux compressed image to the
memory?

Where in memory does it put the Linux kernel? For example, if I have 2 DDRs
in my hardware, in which of them it will be put the kernel?

Can I set the kernel location in memory manually?

Might be an stupid question but: Is it possible for the kernel to be half in
BRAMS and half in DDR?

Regards,
Moji

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


OCM instruction memory

2008-05-16 Thread mojtaba
Dear all,
I have a problem with OCM instruction memory.
When I create a simple hardware design without OCM instruction memory, I can
easily run Linux on it.
But, when I add an OCM instruction cache with the size 128K, the system
freezes at this point:

loaded at: 0040 004CE1A0
board data at: 004CC120 004CC19C
relocated to:  00404050 004040CC
zimage at: 00404E88 004CBE3E
avail ram: 004CF000 1000

Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2
Uncompressing Linux...done.
Now booting the kernel


I already test the memory and it's ok. I asked my pervious question about
system ACE because of this problem. Actually I thought that the linux image
might be copied to the OCM instruction memory. If the linux image is copied
to the address zero which my DDR is mapped there, there should be no
difference between the platform with OCM and without? 

Can you please help me on this issue?

Best regards,
Mojtaba


# 
#

##
# 
# Created by Base System Builder Wizard for Xilinx EDK 9.1.02 Build
EDK_J_SP2.4
# 
# Fri May 16 15:06:06 2008
# 
# Target Board:  Xilinx Virtex-4 ML410 Evaluation Platform Rev B
# Family:virtex4
# Device:XC4VFX60
# Package:   ff1152
# Speed Grade:   -11
# 
# Processor: PPC 405
# Processor clock frequency: 300.00 MHz
# Bus clock frequency: 100.00 MHz
# Debug interface: FPGA JTAG
# On Chip Memory : 256 KB
# Total Off Chip Memory : 256 MB
#   - DDR2_SDRAM_32Mx64 = 256 MB
# 
#

##


 PARAMETER VERSION = 2.1.0


 PORT fpga_0_RS232_Uart_1_ctsN_pin = fpga_0_RS232_Uart_1_ctsN, DIR = I
 PORT fpga_0_RS232_Uart_1_rtsN_pin = fpga_0_RS232_Uart_1_rtsN, DIR = O
 PORT fpga_0_RS232_Uart_1_sin_pin = fpga_0_RS232_Uart_1_sin, DIR = I
 PORT fpga_0_RS232_Uart_1_sout_pin = fpga_0_RS232_Uart_1_sout, DIR = O
 PORT fpga_0_SysACE_CompactFlash_SysACE_CLK_pin =
fpga_0_SysACE_CompactFlash_SysACE_CLK, DIR = I
 PORT fpga_0_SysACE_CompactFlash_clk_enable_n_pin = net_vcc, DIR = O
 PORT fpga_0_SysACE_CompactFlash_SysACE_MPA_pin =
fpga_0_SysACE_CompactFlash_SysACE_MPA, DIR = O, VEC = [6:0]
 PORT fpga_0_SysACE_CompactFlash_SysACE_MPD_pin =
fpga_0_SysACE_CompactFlash_SysACE_MPD, DIR = IO, VEC = [15:0]
 PORT fpga_0_SysACE_CompactFlash_SysACE_CEN_pin =
fpga_0_SysACE_CompactFlash_SysACE_CEN, DIR = O
 PORT fpga_0_SysACE_CompactFlash_SysACE_OEN_pin =
fpga_0_SysACE_CompactFlash_SysACE_OEN, DIR = O
 PORT fpga_0_SysACE_CompactFlash_SysACE_WEN_pin =
fpga_0_SysACE_CompactFlash_SysACE_WEN, DIR = O
 PORT fpga_0_SysACE_CompactFlash_SysACE_MPIRQ_pin =
fpga_0_SysACE_CompactFlash_SysACE_MPIRQ, DIR = I
 PORT fpga_0_ORGate_1_Res_pin = fpga_0_ORGate_1_Res, DIR = O
 PORT fpga_0_ORGate_1_Res_1_pin = fpga_0_ORGate_1_Res, DIR = O
 PORT fpga_0_ORGate_1_Res_2_pin = fpga_0_ORGate_1_Res, DIR = O
 PORT fpga_0_Ethernet_MAC_reset_sgmii_n_pin = net_gnd, DIR = O
 PORT fpga_0_Ethernet_MAC_PHY_tx_clk_pin = fpga_0_Ethernet_MAC_PHY_tx_clk,
DIR = I
 PORT fpga_0_Ethernet_MAC_PHY_rx_clk_pin = fpga_0_Ethernet_MAC_PHY_rx_clk,
DIR = I
 PORT fpga_0_Ethernet_MAC_PHY_dv_pin = fpga_0_Ethernet_MAC_PHY_dv, DIR = I
 PORT fpga_0_Ethernet_MAC_PHY_rx_data_pin = fpga_0_Ethernet_MAC_PHY_rx_data,
DIR = I, VEC = [3:0]
 PORT fpga_0_Ethernet_MAC_PHY_rx_er_pin = fpga_0_Ethernet_MAC_PHY_rx_er, DIR
= I
 PORT fpga_0_Ethernet_MAC_PHY_tx_er_pin = fpga_0_Ethernet_MAC_PHY_tx_er, DIR
= O
 PORT fpga_0_Ethernet_MAC_PHY_tx_en_pin = fpga_0_Ethernet_MAC_PHY_tx_en, DIR
= O
 PORT fpga_0_Ethernet_MAC_PHY_tx_data_pin = fpga_0_Ethernet_MAC_PHY_tx_data,
DIR = O, VEC = [3:0]
 PORT fpga_0_Ethernet_MAC_PHY_Mii_clk_pin = fpga_0_Ethernet_MAC_PHY_Mii_clk,
DIR = IO
 PORT fpga_0_Ethernet_MAC_PHY_Mii_data_pin =
fpga_0_Ethernet_MAC_PHY_Mii_data, DIR = IO
 PORT fpga_0_Ethernet_MAC_PHY_rst_n_pin = fpga_0_Ethernet_MAC_PHY_rst_n, DIR
= O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_ODT_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_ODT, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_Addr_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_Addr, DIR = O, VEC = [0:12]
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_BankAddr_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_BankAddr, DIR = O, VEC = [0:1]
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_CASn_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_CASn, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_CKE_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_CKE, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_CSn_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_CSn, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_RASn_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_RASn, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_WEn_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_WEn, DIR = O
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_DM_pin = fpga_0_DDR2_SDRAM_32Mx64_DDR_DM,
DIR = O, VEC = [0:7]
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_DQS_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_DQS, DIR = IO, VEC = [0:7]
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_DQSn_pin =
fpga_0_DDR2_SDRAM_32Mx64_DDR_DQSn, DIR = IO, VEC = [0:7]
 PORT fpga_0_DDR2_SDRAM_32Mx64_DDR_DQ_pin

Linux on Ml410

2008-05-13 Thread mojtaba
Dear all,

I am trying to run linux 1.6.25 on ML410 board. When the system boot I
receive this error:

loaded at: 0040 004CD19C
board data at: 004CB120 004CB19C
relocated to:  00404050 004040CC
zimage at: 00404E3C 004CA0D1
avail ram: 004CE000 1000

Linux/PPC load: console=ttyS0,115200 root=/dev/xsa2
Uncompressing Linux...inflate returned FFFD
exit

I will appreciate it if somebody can kindly answer me?
Regards,
Mojtaba

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


Linux for ml410

2008-05-06 Thread mojtaba
Dear All,
I am trying to compile Linux 2.6.25(which I got from git.xilinx) for ML410
board and I have a problem during compilation. This is the error message:

 CC  arch/ppc/platforms/4xx/xilinx_generic_mlxxx.o
arch/ppc/platforms/4xx/xilinx_generic_mlxxx.c: In function
'virtex_device_fixup':
arch/ppc/platforms/4xx/xilinx_generic_mlxxx.c:31: error: dereferencing
pointer to incomplete type
make[1]: *** [arch/ppc/platforms/4xx/xilinx_generic_mlxxx.o] Error 1
make: *** [arch/ppc/platforms/4xx] Error 2

it seems that xlltemac_platform_data structure is not recognized by the
compiler so it cannot dereference it. I do not know what this structure is
and where it has been defined. I really appreciate if you can help me.
Best regards,
Mojtaba

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


RE: File system problem

2008-01-04 Thread mojtaba
Hi,
Thank you all for your helps.

Today I tried to make the file system again using buildroot. This time I
included busybox to the packages for target system (Before that, I did not
include the busybox). Surprisingly the system boot correctly.

But, I do not want to use busybox. I already compiled coreutiles and I want
to put them on my target system. After building the root file system I tried
to replace those symbolic links to busybox(such as ls, cp, ...) with the
real commands from coreutiles but I got this error.

Freeing unused kernel memory: 76k init
missing file opeKernel panic - not syncing: Attempted to kill init!
rand
Try `/bin/Rebooting in 180 seconds..sh --help' for more information.

So, how can I use coreutils instead of busybox?

Regards,
Mojtaba

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean-Samuel
Chenard
Sent: Friday, January 04, 2008 12:58 AM
To: linuxppc-embedded@ozlabs.org; [EMAIL PROTECTED]
Subject: RE: File system problem

 Message: 9
 Date: Thu, 3 Jan 2008 18:00:14 +0100
 From: mojtaba

 Actually, I removed the console and null created by buildroot and create
 them manually using make node. This time the system freezes at this point.
 Freeing unused kernel memory: 76k init

Hi Mojtaba,

I just want to comment on your observation that the file size in /dev
was zero.  This is normal as the device files are 'special' since they
are a mean of abstracting the interface to the kernel.  I had to read
the online book listed below before I could understand the inner
workings of those special files.  If you plan on interfacing your FPGA
with the Linux Kernel, I suggest you read it too, as it is a very
insightful book:
http://lwn.net/Kernel/LDD3/

At this point, your system is not frozen, but your init script and
configuration files are probably not all correctly set.  You might
need to read some documentation about buildroot to see what its init
scripts are trying to do.

You might be missing a library or symlink (I got that problem in my
attempt to build the BusyBox root filesystem from scratch).  One way
to go at the problem is to pass the init=/bin/ash or something like
that to your kernel at the boot prompt (you could even make some
trivial 'hello world' program and pass it to the kernel as the init
process).  This way, you can dive right into a shell or your program
and avoid init and its configuration.

After some copying of required libraries in /lib (I'm using uClibc)
and the creation of the required symbolic links, I got my Busybox root
filesystem working on my ML-310 board.

Good luck!

Regards,

Jean-Samuel
-- 
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montréal, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


RE: File system problem

2008-01-03 Thread mojtaba
Hi,
Thank you very much for your answers.

But I have both console and null in /dev.

-rw-rw-rw- 1 mojtaba mojtaba0 2007-12-26 15:50 console
-rw-rw-rw- 1 mojtaba mojtaba0 2007-12-26 15:50 null

They have been created by buildroot. Do I need to create them manually?
Actually the size of both of them is 0 and both are empty files. Is that a
problem?

Thank you in advance and best regards,
Mojtaba

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean-Samuel
Chenard
Sent: Thursday, January 03, 2008 4:33 AM
To: linuxppc-embedded@ozlabs.org; [EMAIL PROTECTED]
Subject: RE: File system problem

 Date: Wed, 2 Jan 2008 19:50:13 +0100
 From: mojtaba
 I am trying to boot a root file system build by buildroot. But I got this
 error init has generated signal 11 but has no handler for it.

 My kernel version is 2.6.24-rc3
 My target system is PPC 405 (XILINX VIRTEX II pro) I am using the
26-12-2007
 snapshot of buildroot.
[ ... ]
 Warning: unable to open an initial console.
 init has generated signal 11 but has no handler for it Kernel panic - not

Hi Mojtaba,

I got a similar error on my ML-310 when I tried a new root filesystem.
 As far as I recall, I needed to make sure that two entries existed in
/dev, namely:

crw---1 root root   5,   1 Jan  1 05:18 console
crw-rw1 root root   1,   3 Dec 10  2007 null

I think that you are missing /dev/console and then init cannot run
since it has nowhere to put its standard output.

You can make those by mounting your CF card on your development host
and (as root) make the nodes:

# mknod -m 660 /dev/console c 5 1
# mknod -m 660 /dev/null c 1 3

In my case, I use the UartLite (ttyUL0) serial port driver, but I'm
pretty sure this is going to fix the problem you are observing.

Regards,

Jean-Samuel
-- 
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montréal, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


RE: File system problem

2008-01-03 Thread mojtaba
 cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 258048k available (1288k kernel code, 436k data, 76k init, 0k
highmem)

Mount-cache hash table entries: 512   
net_namespace: 64 bytes   
NET: Registered protocol family 16  
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy

Call Trace:   
[cfc1fe20] [c0008148] show_stack+0x58/0x188 (unreliable)

[cfc1fe68] [c0038908] set_fail+0x50/0x68

[cfc1fe80] [c0038f7c] sysctl_check_table+0x65c/0x6ac
[cfc1fee8] [c0038f8c] sysctl_check_table+0x66c/0x6ac
[cfc1ff50] [c0026c58] register_sysctl_table+0x64/0xb4
[cfc1ff68] [c019ed4c] register_ppc_htab_sysctl+0x18/0x2c
[cfc1ff70] [c019b228] kernel_init+0x104/0x290
[cfc1fff0] [c0004af8] kernel_thread+0x44/0x60
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x40401003 (irq = 2) is a 16550A
console [ttyS0] enabled
xsysace xsysace.0: Xilinx SystemACE revision 1.0.12
xsysace xsysace.0: capacity: 1981728 sectors
 xsa: xsa1 xsa2 xsa3
Xilinx SystemACE device driver, major=254
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 76k init


-Original Message-
From: mojtaba [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 03, 2008 4:58 PM
To: 'linuxppc-embedded@ozlabs.org'
Subject: RE: File system problem

Hi,
Thank you very much for your answers.

But I have both console and null in /dev.

-rw-rw-rw- 1 mojtaba mojtaba0 2007-12-26 15:50 console
-rw-rw-rw- 1 mojtaba mojtaba0 2007-12-26 15:50 null

They have been created by buildroot. Do I need to create them manually?
Actually the size of both of them is 0 and both are empty files. Is that a
problem?

Thank you in advance and best regards,
Mojtaba

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean-Samuel
Chenard
Sent: Thursday, January 03, 2008 4:33 AM
To: linuxppc-embedded@ozlabs.org; [EMAIL PROTECTED]
Subject: RE: File system problem

 Date: Wed, 2 Jan 2008 19:50:13 +0100
 From: mojtaba
 I am trying to boot a root file system build by buildroot. But I got this
 error init has generated signal 11 but has no handler for it.

 My kernel version is 2.6.24-rc3
 My target system is PPC 405 (XILINX VIRTEX II pro) I am using the
26-12-2007
 snapshot of buildroot.
[ ... ]
 Warning: unable to open an initial console.
 init has generated signal 11 but has no handler for it Kernel panic - not

Hi Mojtaba,

I got a similar error on my ML-310 when I tried a new root filesystem.
 As far as I recall, I needed to make sure that two entries existed in
/dev, namely:

crw---1 root root   5,   1 Jan  1 05:18 console
crw-rw1 root root   1,   3 Dec 10  2007 null

I think that you are missing /dev/console and then init cannot run
since it has nowhere to put its standard output.

You can make those by mounting your CF card on your development host
and (as root) make the nodes:

# mknod -m 660 /dev/console c 5 1
# mknod -m 660 /dev/null c 1 3

In my case, I use the UartLite (ttyUL0) serial port driver, but I'm
pretty sure this is going to fix the problem you are observing.

Regards,

Jean-Samuel
-- 
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montréal, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


File system problem

2008-01-02 Thread mojtaba
Dear all,

I am trying to boot a root file system build by buildroot. But I got this
error init has generated signal 11 but has no handler for it.

My kernel version is 2.6.24-rc3
My target system is PPC 405 (XILINX VIRTEX II pro) I am using the 26-12-2007
snapshot of buildroot.

This is what I get on terminal:

loaded at: 0040 004CE1A0
board data at: 004CC120 004CC19C
relocated to:  0040405C 004040D8
zimage at: 00404E94 004CB08A
avail ram: 004CF000 1000

Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2 init=/bin/sh

Uncompressing Linux...done.   
Now booting the kernel  
Linux version 2.6.24-rc3 ([EMAIL PROTECTED]) (gcc version 4.2.2) #1 Wed Jan 2
14:3

7:58 CET 2008 
Xilinx ML300 Reference System (Virtex-II Pro)

Zone PFN ranges:
  DMA 0 -65536   
  Normal  65536 -65536   
  HighMem 655
Movable zone start PFN for each node
early_node_map[1] active PFN ranges   
0:0 -65536   
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

Kernel command line: console=ttyS0,9600 root=/dev/xsa2 init=/bin/sh

Xilinx INTC #0 at 0x4120 mapped to 0xEF5FE000

PID hash table entries: 1024 (order: 10, 4096 bytes)

Console: colour dummy device 80x25  
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 258048k available (1288k kernel code, 436k data, 76k init, 0k
highmem)

Mount-cache hash table entries: 512   
net_namespace: 64 bytes   
NET: Registered protocol family 16  
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy

Call Trace:   
[cfc1fe20] [c0008148] show_stack+0x58/0x188 (unreliable)

[cfc1fe68] [c0038908] set_fail+0x50/0x68

[cfc1fe80] [c0038f7c] sysctl_check_table+0x65c/0x6ac

[cfc1fee8] [c0038f8c] sysctl_check_table+0x66c/0x6ac

[cfc1ff50] [c0026c58] register_sysctl_table+0x64/0xb4

[cfc1ff68] [c019ed4c] register_ppc_htab_sysctl+0x18/0x2c
[cfc1ff70] [c019b228] kernel_init+0x104/0x290 [cfc1fff0] [c0004af8]
kernel_thread+0x44/0x60 io scheduler noop registered io scheduler
anticipatory registered io scheduler deadline registered io scheduler cfq
registered (default) Generic RTC Driver v1.07 Macintosh non-volatile memory
driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x40401003 (irq = 2) is a 16550A console [ttyS0]
enabled xsysace xsysace.0: Xilinx SystemACE revision 1.0.12 xsysace
xsysace.0: capacity: 1981728 sectors
 xsa: xsa1 xsa2 xsa3
Xilinx SystemACE device driver, major=254
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 76k init
Warning: unable to open an initial console.
init has generated signal 11 but has no handler for it Kernel panic - not
syncing: Attempted to kill init!
Rebooting in 180 seconds..


Regards,
Mojtaba


___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded