2011-05-03 07:05:50     Stuck at "Starting Kernel"

Document created by Aaronwu Employee on Aug 26, 2013
Version 1Show Document
  • View in full screen mode

2011-05-03 07:05:50     Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100376   

Hello

 

After making tentative changes to 2010R1-RC5, compiling went OK but the kernel is stuck at "Starting kernel":

 

 

ip04>set autostart

ip04>tftp 0x1000000 uImage_r2.ip08

ip04>bootm 0x1000000

## Booting image at 01000000 ...

   Image Name:   uClinux Kernel and ext2

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    2821100 Bytes =  2.7 MB

   Load Address: 00001000

   Entry Point:  001e9d9c

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 1e9d9c

 

 

What are known issues that can prevent the kernel from booting? How can I investigate?

 

Thank you.

QuoteReplyEditDelete

 

 

2011-05-03 07:23:30     Re: Stuck at "Starting Kernel"

Aaron Wu (CHINA)

Message: 100378   

 

please check if your console is correctly given out in for bootargs in u-boot

QuoteReplyEditDelete

 

 

2011-05-03 07:27:15     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100379   

 

please check if your console is correctly given out in for bootargs in u-boot

 

---

 

Thanks but I don't understand: Do you mean the Uboot parameters as saved in the EEPROM, or some settings in the kernel when compiling?

 

FWIW, here are the EEPROM settings:

 

 

 

ip04>print

bootdelay=3

baudrate=115200

loads_echo=1

eth1addr=02:80:ad:20:31:b9

preboot=echo starting from spi flash

rootpath=/bf1/rootfs

hostname=BF1

addnet=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off

nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath);run addnet;

ramboot=tftp 0x01000000 vmImage;run addnet;bootm

nfsboot=tftp 0x01000000 vmImage;run nfsargs;bootm

flashboot=run addnet;bootm 20020000

spiboot=eeprom read 0x01000000 30000 110000;run addnet;bootm 0x01000000

update=tftpboot 0x01000000 u-boot.bin;protect off 0x20000000 0x2001FFFF;erase 0x20000000 0x2001FFFF;cp.b 0x01000000 0x20000000 $(filesize)

ethact=DM9000#0

ethaddr=00:09:45:56:72:9b

ipaddr 192.168.0.9

nandboot=nboot 0x2000000 0x0

bootcmd=run nandboot

console=ttyBF0,115200

root=/dev/mtdblock0 rw

filesize=4a0000

fileaddr=1000000

gatewayip=192.168.0.254

netmask=255.255.255.0

ipaddr=192.168.0.9

serverip=192.168.0.12

autostart=yes

bootargs=ethaddr=00:09:45:56:72:9b console=ttyBF0,115200 root=/dev/mtdblock0 rw

stdin=serial

stdout=serial

stderr=serial

 

Environment size: 1150/65532 bytes

 

QuoteReplyEditDelete

 

 

2011-05-03 07:52:16     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100380   

 

Or could it be that I must upgrade Uboot itself? In which case do we need to upgrade Uboot when booting a more recent uClinux kernel?

QuoteReplyEditDelete

 

 

2011-05-03 08:28:55     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100381   

 

Per this document, I enabled Early Printk Debugging through Kernel hacking  ---> [*] Early printk, but the kernel still gets stuck at the same point, before it's able to output information that could help.

 

FWIW, here's my Uboot's setting:

 

bootargs=ethaddr=00:09:45:56:72:9b console=ttyBF0,115200 root=/dev/mtdblock0 rw earlyprintk=serial,uart0,115200

QuoteReplyEditDelete

 

 

2011-05-03 08:36:03     Re: Stuck at "Starting Kernel"

Andreas Schallenberg (GERMANY)

Message: 100382   

 

To verify that the kernel is really booting you could try and see, if you get the kernel boot messages this way:

 

https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:debug:post_mortem

TranslateQuoteReplyEditDelete

 

 

2011-05-03 09:11:25     Re: Stuck at "Starting Kernel"

Chandrashekhar Lavania (INDIA)

Message: 100383   

 

Hi,

 

UART mapping can be on eithert Port G or Port F. Make sure that you are using the correct mapping for your board.

 

The mapping is configured when the kernel is built. It can be done in the following manner:

 

1.do make menuconfig

 

2. goto Linux Kernel configurations -> Blackfin Processor Options-> BF527 Specific Configuration

 

There one can find the option to change UART port.

 

I have BF527......say if you have BF537 then you have to go to BF537 Specific Configuration instead of BF527 Specific Configuration

 

Also, I am not sure but 2010R1 has uart1 and not uart0..............also you need to use ttyBF1 with uart1.

 

Regards,

 

Shekhar

 

QuoteReplyEditDelete

 

 

2011-05-03 09:14:55     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100384   

 

Thanks for the tip, but the memory is empty:

 

================ Ubuntu host

 

 

 

/usr/src/uClinux-dist-2010R1-RC5# grep __log_buf ./linux-2.6.x/System.map

 

001c584c b ___log_buf

================ Blackfin

(Downloaded image from Ubuntu, started with "bootm", then hit reset button)

 

 

 

ip04>set bootargs $(bootargs) panic=3

ip04>set bootcmd

ip04>string 001c584c

Unknown command 'string' - try 'help'

ip04>md.b 001c584c

001c584c: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

001c585c: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

001c586c: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

001c587c: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

================

QuoteReplyEditDelete

 

 

2011-05-03 09:29:14     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100385   

 

Thank you. There is only one information in Blackfin Processor Options > BF533/2/1 Specific Configuration:

 

*** Interrupt Priority Assignment ***                                  ¦ ¦

¦ ¦         Priority  --->

 

 

I looked around, but there's no other section that includes UART information.

 

Until now, using "console=ttyBF0,115200" in Uboot as worked fine, but I tried the following just to check:

 

 

 

bootargs=00:09:45:56:72:9b console=ttyBF1,115200 root=/dev/mtdblock0 rw earlyprintk=serial,uart1,115200 panic=3

 

 

After resetting the device and trying the image, still stuck, with no extra information.

QuoteReplyEditDelete

 

 

2011-05-03 15:57:10     Re: Stuck at "Starting Kernel"

Mike Frysinger (UNITED STATES)

Message: 100393   

 

run `make bugreport` and post the tarball as an attachment

QuoteReplyEditDelete

 

 

2011-05-03 18:45:44     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100394   

 

Here it is.

 

bugreport.tar.gz

QuoteReplyEditDelete

 

 

2011-05-03 22:09:04     Re: Stuck at "Starting Kernel"

Aaron Wu (CHINA)

Message: 100395   

 

Thanks for your info.

 

Why do you set your serial baudrate to 115200 for kernel, since you can get the print output sucessfully so I guess for u-boot you have also changed it to 115200. Have you tried our default setting? You may run the default setting first. Below is a general env setting for a bf537 ezkit board:

 

bfin> print

bootargs=root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

baudrate=57600

loads_echo=1

autoload=no

rootpath=/romfs

hostname=bf537-stamp

loadaddr=0x1000000

nc=set ncip ${serverip};set stdin nc;set stdout nc

ubootfile=u-boot.bin

update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 +$(filesize);erase 0x20000000 +$(filesize);cp.b $(loadaddr) 0x20000000 $(filesi)

addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off

ramargs=set bootargs root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600

ramboot=tftp $(loadaddr) $(ramfile);run ramargs;run addip;bootm

nfsfile=vmImage

nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3

nfsboot=tftp $(loadaddr) $(nfsfile);run nfsargs;run addip;bootm

flashboot=bootm 0x20100000

ethact=Blackfin EMAC

ethaddr=00:E0:22:FE:58:9B

bootcmd=run ramboot

bootdelay=1

gatewayip=10.99.23.1

netmask=255.255.255.0

ipaddr=10.99.23.93

dnsip=10.99.27.40

serverip=10.99.29.99

serveraddr=00:0f:cd:7e:e2:01

ramfile=uImage.spi

stdin=serial

stdout=serial

stderr=serial

QuoteReplyEditDelete

 

 

2011-05-04 00:53:23     Re: Stuck at "Starting Kernel"

Mike Frysinger (UNITED STATES)

Message: 100398   

 

you didnt actually enable early printk in that.  please do so and try booting again with earlyprintk=.  then if things hang, when you hit the reset button, the bootloader (if it's an up-to-date 2010R1 version) will automatically parse it and show you the output from before.

 

further, if you're using 2010R1, you should be using initramfs now instead of the older ext2 method.  please disable CONFIG_MTD_UCLINUX.

QuoteReplyEditDelete

 

 

2011-05-04 04:55:21     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100413   

 

I always use 115200 as baud rate, and it worked fine so far.

 

I'd rather leave Uboot as-is for the time being unless it's necessary to investigate this error.

 

After disabling CONFIG_MTD_UCLINUX (presumably to have "make" use an Initramfs instead of a RAM-base ext2 filesystem), I reran "make", copied images/uImage to the tftpd directory, and ran the image. It booted OK, until it crashes, presumably because it doesn't include MTD:

 

 

 

========================

 

# make

...

Image Name:   bf533-2.6.34.7-ADI-2010R1

Created:      Wed May  4 10:26:03 2011

Image Type:   Blackfin Linux Kernel Image (gzip compressed)

Data Size:    1153402 Bytes = 1126.37 kB = 1.10 MB

Load Address: 00001000

Entry Point:  001efb88

make[3]: Leaving directory `/usr/src/baps/uClinux-dist-2010R1-RC5/linux-2.6.x'

cp /usr/src/baps/uClinux-dist-2010R1-RC5/linux-2.6.x/arch/blackfin/boot/vmImage /usr/src/baps/uClinux-dist-2010R1-RC5/images/uImage.initramfs

cp /usr/src/baps/uClinux-dist-2010R1-RC5/linux-2.6.x/System.map /usr/src/baps/uClinux-dist-2010R1-RC5/images/System.map.initramfs

cp /usr/src/baps/uClinux-dist-2010R1-RC5/linux-2.6.x/vmlinux /usr/src/baps/uClinux-dist-2010R1-RC5/images/linux.initramfs

ln -sf uImage.initramfs /usr/src/baps/uClinux-dist-2010R1-RC5/images/uImage

make[2]: Leaving directory `/usr/src/baps/uClinux-dist-2010R1-RC5/vendors/Rowetel/IP04'

make[1]: Leaving directory `/usr/src/baps/uClinux-dist-2010R1-RC5/vendors'

 

========================

 

cp images/uImage /var/lib/tftpboot/

 

========================

 

ip04>tftp 0x1000000 uImage

ip04>bootm 0x1000000

## Booting image at 01000000 ...

   Image Name:   bf533-2.6.34.7-ADI-2010R1

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    1153402 Bytes =  1.1 MB

   Load Address: 00001000

   Entry Point:  001efb88

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 1efb88

Linux version 2.6.34.7-ADI-2010R1 (root@ubuntu) (gcc version 4.3.5 (ADI-2010R1-RC4) ) #2 Wed May 4 10:22:39 CEST 2011

register early platform devices

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x0015c8f0

  rodata    = 0x0015c8f0-0x001c649c

  bss       = 0x001c7000-0x001d8938

  data      = 0x001d8940-0x001ec000

    stack   = 0x001ea000-0x001ec000

  init      = 0x001ec000-0x00206000

  available = 0x00206000-0x03f00000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 6

Blackfin support (C) 2004-2010 Analog Devices, Inc.

Compiled for ADSP-BF532 Rev 0.5

Blackfin Linux support by   blackfin.uclinux.org/

Processor Speed: 400 MHz core clock and 133 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

  External memory: cacheable in instruction cache

Data Cache Enabled for CPU0

  External memory: cacheable (write-back) in data cache

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 16002

Kernel command line: ethaddr=00:09:45:56:72:9b console=ttyBF0,115200 root=/dev/mtdblock0 rw earlyprintk=serial,uart0,115200 panic=3

PID hash table entries: 256 (order: -2, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 61872k/65536k RAM, (104k init code, 1390k kernel code, 574k data, 1024k dma, 572k reserved)

Hierarchical RCU implementation.

RCU-based detection of stalled CPUs is enabled.

NR_IRQS:81

Configuring Blackfin Priority Driven Interrupts

console [ttyBF0] enabled

Calibrating delay loop... 796.67 BogoMIPS (lpj=1593344)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Instruction SRAM: 32 KB (20 KB free)

NET: Registered protocol family 16

Blackfin DMA Controller

ip0x_init(): registering device resources

bio: create slab <bio-0> at 0

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Switching to clocksource bfin_cs_cycles

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

msgmni has been set to 120

Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

io scheduler noop registered

io scheduler cfq registered (default)

bfin_sport: registered sport0

bfin_sport: registered sport1

bfin-uart: Blackfin serial driver

bfin-uart.0: ttyBF0 at MMIO 0xffc00400 (irq = 21) is a BFIN-UART

brd: module loaded

Generic platform RAM MTD, (c) 2004 Simtec Electronics

dm9000 Ethernet Driver, V1.31

eth0: dm9000a at 20100000,20100002 IRQ 48 MAC: 00:09:45:56:72:9b (chip)

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: read wrong id 0x2b2a2928

dm9000 dm9000.1: wrong id: 0x2b2a2928

dm9000 dm9000.1: not found (-19).

usbmon: debugfs is not available

driver isp1362-hcd, 2005-04-04

isp1362-hcd isp1362-hcd.0: ISP1362 Host Controller

isp1362-hcd isp1362-hcd.0: new USB bus registered, assigned bus number 1

isp1362_hc_reset:

isp1362-hcd isp1362-hcd.0: irq 44, io mem 0x20300000

isp1362_hc_start:

isp1362_hc_start: Invalid chip ID f60f

isp1362-hcd isp1362-hcd.0: startup error -19

isp1362-hcd isp1362-hcd.0: USB bus 1 deregistered

isp1362_probe: init error, -19

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

ip_tables: (C) 2000-2006 Netfilter Core Team

TCP cubic registered

NET: Registered protocol family 17

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

dma_alloc_init: dma_page @ 0x020a1000 - 256 pages at 0x03f00000

VFS: Cannot open root device "mtdblock0" or unknown-block(0,0)

Please append a correct "root=" boot option; here are the available partitions:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Hardware Trace:

   0 Target : <0x0015c770> { _dump_stack + 0x0 }

     Source : <0x0015c7ea> { _panic + 0x42 } CALL pcrel

   1 Target : <0x0015c7ea> { _panic + 0x42 }

     Source : <0x0015c86c> { _printk + 0x14 } RTS

   2 Target : <0x0015c868> { _printk + 0x10 }

     Source : <0x0000f9e6> { _vprintk + 0x162 } RTS

   3 Target : <0x0000f9da> { _vprintk + 0x156 }

     Source : <0xffa08c1c> { __common_int_entry + 0xd8 } RTI

   4 Target : <0xffa08bba> { __common_int_entry + 0x76 }

     Source : <0xffa089fc> { _return_from_int + 0x58 } RTS

   5 Target : <0xffa089fc> { _return_from_int + 0x58 }

     Source : <0xffa089d2> { _return_from_int + 0x2e } IF !CC JUMP pcrel

   6 Target : <0xffa089a4> { _return_from_int + 0x0 }

     Source : <0xffa08bb6> { __common_int_entry + 0x72 } JUMP.L

   7 Target : <0xffa08bb4> { __common_int_entry + 0x70 }

     Source : <0xffa0833e> { _asm_do_IRQ + 0x6a } RTS

   8 Target : <0xffa08336> { _asm_do_IRQ + 0x62 }

     Source : <0x00012fda> { __local_bh_enable + 0x3a } RTS

   9 Target : <0x00012fa0> { __local_bh_enable + 0x0 }

     Source : <0x000135f8> { ___do_softirq + 0xa4 } JUMP.L

  10 Target : <0x000135f0> { ___do_softirq + 0x9c }

     Source : <0x000135e4> { ___do_softirq + 0x90 } IF CC JUMP pcrel

  11 Target : <0x000135d6> { ___do_softirq + 0x82 }

     Source : <0x00032240> { _rcu_bh_qs + 0x14 } RTS

  12 Target : <0x0003222c> { _rcu_bh_qs + 0x0 }

     Source : <0x000135d2> { ___do_softirq + 0x7e } JUMP.L

  13 Target : <0x000135ca> { ___do_softirq + 0x76 }

     Source : <0x00032c98> { _rcu_process_callbacks + 0x30 } RTS

  14 Target : <0x00032c94> { _rcu_process_callbacks + 0x2c }

     Source : <0x00032b36> { _rcu_do_batch + 0x12a } RTS

  15 Target : <0x00032b2e> { _rcu_do_batch + 0x122 }

     Source : <0x00032a1e> { _rcu_do_batch + 0x12 } IF CC JUMP pcrel

Stack info:

SP: [0x0201bf3c] <0x0201bf3c> /* kernel dynamic memory (maybe user-space) */

FP: (0x0201bfe4)

Memory from 0x0201bf30 to 0201c000

0201bf30: 0018ec08  0201bf3c  00000000 [0018ecfc] 0015c7ee  0206e000  0018ecfc  001cc37e

0201bf50: 001cc37e  001cc37e  0201bf6c  001eca06  0206e000  0201bf7c  0201bf80  0201bf7c

0201bf70: 00000000  00008000  00000000  6e6b6e75  2d6e776f  636f6c62  2c30286b  02002930

0201bf90: 001ecb1e  001c7234  00000000  00000000  001ecc50  001c7234  001fcf68  00000000

0201bfb0: 00000000  00000000  00000000  001ec1da  00200e6c  00200e6c  00000000  00000000

0201bfd0: 001ec1ee  00200e6c  00200e6c  00000000  00000000 (00000000)<000014ae> 00000000

0201bff0: 00000000  00000000  ffffffff  00000006

Return addresses in stack:

   frame  1 : <0x000014ae> { _kernel_thread_helper + 0x6 }

Rebooting in 3 seconds..U-Boot 1.1.5 (May  5 2007 - 05:46:05)

 

========================

 

Per this thread, I made sure MTD was enabled, which it was already:

 

Device Drivers > <*> Memory Technology Device (MTD) support  --->

[*]   MTD partitioning support

[*]   Direct char device access to MTD devices                             ¦ ¦

[*]   Common interface to block layer for MTD 'translation layers'         ¦ ¦

[*]   Caching block device access to MTD devices

 

Also, Initramfs/initrd was already enabled through General setup > [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support.

 

I included the configuration files made through "make bugreport".

 

Does someone know why the kernel doesn't create a RAM-based MTD partition to hold the root filesystem?

 

Thank you.

 

bugreport.tar.gz

QuoteReplyEditDelete

 

 

2011-05-04 05:03:10     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100414   

 

I'd like to point out that, currently, I'm testing the image by running it entirely from RAM, but once it's OK, I'll save the root filesystem to NAND so it's persistent.

QuoteReplyEditDelete

 

 

2011-05-04 06:31:22     Re: Stuck at "Starting Kernel"

Mike Frysinger (UNITED STATES)

Message: 100415   

 

the initramfs part is taken care of by the vendor-specific uclinux-dist makefile.  so you might have to update yours.  refer to the adi ones and you can see that most code is in a .mak file for all vendors to include (no need to copy & paste anymore).

 

but yes, that is the issue.  you have no rootfs for the kernel to boot.

QuoteReplyEditDelete

 

 

2011-05-04 12:01:34     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100423   

 

Make sense. After disabling CONFIG_MTD_UCLINUX, I just get the kernel, with no filesystem, and the kernel crashes:

 

 

 

"Blackfin Linux Kernel Image (gzip compressed)

 

...

 

VFS: Cannot open root device "mtdblock0" or unknown-block(0,0)"

 

 

 

I'll go through the Makefiles to see how to create + attach a filesystem to the kernel.

 

Thank you.

QuoteReplyEditDelete

 

 

2011-05-05 06:42:12     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100438   

 

Made some progress: Using the board's configuration/etc files and the BP533-STAMP's Makefile, the kernel boots.

 

However, it stops there:

 

 

 

==============

 

Starting Kernel at = 1f1c68

 

Linux version 2.6.34.7-ADI-2010R1 (root@ubuntu) (gcc version 4.3.5 (ADI-2010R1-RC4) ) #9 Thu May 5 12:34:20 CEST 2011

 

register early platform devices

 

Found mtd parition at 0x00208000, (len=0x800000), moving to 0x03700000

 

...

 

dma_alloc_init: dma_page @ 0x020a4000 - 256 pages at 0x03f00000

 

VFS: Mounted root (ext2 filesystem) on device 31:0.

 

Freeing unused kernel memory: 104k freed

 

init: exec rc failed

 

init: Booting to single user mode

 

init: exec of single user shell failed

 

init: -/bin/sh exec failed

 

==============

 

 

 

I checked that romfs/bin/init, romfs/etc/inittab, and romfs/etc/rc are present. Has someone already seen this?

 

Thank you.

QuoteReplyEditDelete

 

 

2011-05-05 06:49:11     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100439   

I also checked whether romfs/bin/init required shared libraries, and if that was the case, that those libraries were part of the filesystem:

 

=================

/usr/src/uClinux-dist-2010R1-RC5# file romfs/bin/init

romfs/bin/init: ELF 32-bit LSB executable, Analog Devices Blackfin, version 1 (SYSV), dynamically linked (uses shared libs), stripped

=================

/usr/src/uClinux-dist-2010R1-RC5# scanelf -qn romfs/bin/init

libcrypt.so.0,libgcc_s.so.1,libc.so.0  romfs/bin/init

=================

/usr/src/uClinux-dist-2010R1-RC5# ll romfs/lib/libcrypt.so.0

-rwxr-xr-x 1 root root 9340 2011-05-05 12:34 romfs/lib/libcrypt.so.0*

 

/usr/src/uClinux-dist-2010R1-RC5# ll romfs/lib/libgcc_s.so.1

-rwxr-xr-x 1 root root 62416 2011-05-05 12:34 romfs/lib/libgcc_s.so.1*

 

/usr/src/uClinux-dist-2010R1-RC5# ll romfs/lib/libc.so.0

-rwxr-xr-x 1 root root 247564 2011-05-05 12:34 romfs/lib/libc.so.0*

=================

 

QuoteReplyEditDelete

 

 

2011-05-05 08:07:03     Re: Stuck at "Starting Kernel"

Mike Frysinger (UNITED STATES)

Message: 100441   

 

make sure your kernel has FLAT and FDPIC support enabled

QuoteReplyEditDelete

 

 

2011-05-05 09:13:24     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100442   

 

In Executable file formats, I left the default settings:

 

[*] Kernel support for FDPIC ELF binaries

 

[*] Kernel support for flat binaries

 

[*]   Enable ZFLAT support

 

[ ]   Enable shared FLAT support

 

< > Kernel support for MISC binaries

 

Could it be that the root filesystem that's appended to the kernel is not correctly loaded, which would make it impossible for the kernel to launch init?

QuoteReplyEditDelete

 

 

2011-05-05 11:27:34     Re: Stuck at "Starting Kernel"

Gilles Ganault (FRANCE)

Message: 100443   

 

Found it: By default, no shell was built, either in Core Applications > Shell Program, or BusyBox > Shells. I saw this by checking the contents of romfs/.

 

Thanks for the help.

Attachments

Outcomes