2009-01-04 12:32:41 Another Kernel panic - not syncing: No init found.... help!
Tom Whiteley (UNITED KINGDOM)
Message: 67331
Hi,
I'm not really sure how I should be going about debugging this issue as I'm not seeing any clues in the output. The following output was produced using uClinux 2008 r1 rc8 built using coLinux. All I have done is select the target board (Bluetechnix CM-BF561) and left all other settings as default. I have successfully loaded other versions of uClinux built by Bluetechnix on r1rc8 any build I produce (I'm currently on attempt 22) always fails with the same error when deploying. Any pointers would be greatly appreciated.
bfin> bootm 0x01000000
## Booting kernel from Legacy Image at 01000000 ...
Image Name: uClinux Kernel and ext2
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 1307414 Bytes = 1.2 MB
Load Address: 00001000
Entry Point: 0013c000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 0013c000
Linux version 2.6.22.18-ADI-2008R1-svn (uclinux@colinux) (gcc version 4.1.2 (AD9
Hardware Trace Active and Enabled
Warning: limiting memory to 26MB due to hardware anomaly 05000263
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF561 Rev 0.3
Warning: Compiled for Rev 3, but running on Rev 5
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 550 MHz core clock and 110 MHz System Clock
Board Memory: 32MB
Kernel Managed Memory: 32MB
Memory map:
text = 0x00001000-0x000ed940
rodata = 0x000ee000-0x0012c380
data = 0x0012d000-0x0013c000
stack = 0x0012e000-0x00130000
init = 0x0013c000-0x0014e000
bss = 0x0014e000-0x0015c7a0
available = 0x0015c7a0-0x01a00000
rootfs = 0x01a00000-0x01f00000
DMA Zone = 0x01f00000-0x02000000
Instruction Cache Enabled
Data Cache Enabled (write-back)
Built 1 zonelists. Total pages: 6604
Kernel command line: root=/dev/mtdblock0 rw mtdparts=physmap-flash.0:256k@0k(U0
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory available: 24932k/32768k RAM, (72k init code, 946k kernel code, 371k dat)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (8 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 16 KB (8 KB free)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
cm_bf561_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
BF561 Core B driver v0.1 initialized.
io scheduler noop registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 35) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
smc91x: not found (-19).
uclinux[mtd]: RAM probe address=0x1a00000 size=0x500000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00500000 : "ROMfs"
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 72k freed
dma_alloc_init: dma_page @ 0x018cb000 - 256 pages at 0x01f00000
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
kernel_config22.txt
uclinux_config22.txt
QuoteReplyEditDelete
2009-01-04 12:35:08 Re: Another Kernel panic - not syncing: No init found.... help!
Mike Frysinger (UNITED STATES)
Message: 67332
run `make Bluetechnix/CM-BF561_default` to generate a default uImage ...
QuoteReplyEditDelete
2009-01-04 13:31:58 Re: Another Kernel panic - not syncing: No init found.... help!
Tom Whiteley (UNITED KINGDOM)
Message: 67334
Hi Mike,
Thanks for the incredibly fast response! I have done as suggested and created a new build using make Bluetechnix/CM-BF561_default. The output unfortunately still ends with the dreaded kernel panic (see below).
Do you know of anyway I can actually look into the uImage that is produced (e.g. something like 'Explore2fs' )? I was hopping to compare a known working image with one I am making.
Do you have any suggestions on how I should be trying to debug this issue? I may be missing something in the output, but there don't seem to be any clues as why it has failed.
bfin> bootm 0x01000000
## Booting kernel from Legacy Image at 01000000 ...
Image Name: uClinux Kernel and ext2
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 1307443 Bytes = 1.2 MB
Load Address: 00001000
Entry Point: 0013c000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 0013c000
Linux version 2.6.22.18-ADI-2008R1-svn (uclinux@colinux) (gcc version 4.1.2 (AD9
Hardware Trace Active and Enabled
Warning: limiting memory to 26MB due to hardware anomaly 05000263
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF561 Rev 0.3
Warning: Compiled for Rev 3, but running on Rev 5
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 550 MHz core clock and 110 MHz System Clock
Board Memory: 32MB
Kernel Managed Memory: 32MB
Memory map:
text = 0x00001000-0x000ed940
rodata = 0x000ee000-0x0012c380
data = 0x0012d000-0x0013c000
stack = 0x0012e000-0x00130000
init = 0x0013c000-0x0014e000
bss = 0x0014e000-0x0015c7a0
available = 0x0015c7a0-0x01a00000
rootfs = 0x01a00000-0x01f00000
DMA Zone = 0x01f00000-0x02000000
Instruction Cache Enabled
Data Cache Enabled (write-back)
Built 1 zonelists. Total pages: 6604
Kernel command line: root=/dev/mtdblock0 rw mtdparts=physmap-flash.0:256k@0k(U0
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory available: 24932k/32768k RAM, (72k init code, 946k kernel code, 371k dat)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (8 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 16 KB (8 KB free)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
cm_bf561_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
BF561 Core B driver v0.1 initialized.
io scheduler noop registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 35) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
smc91x: not found (-19).
uclinux[mtd]: RAM probe address=0x1a00000 size=0x500000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00500000 : "ROMfs"
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 72k freed
dma_alloc_init: dma_page @ 0x018cb000 - 256 pages at 0x01f00000
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
QuoteReplyEditDelete
2009-01-04 19:20:56 Re: Another Kernel panic - not syncing: No init found.... help!
Robin Getz (UNITED STATES)
Message: 67338
Tom:
The file system that is included is simply the ./romfs directory.
There is no way to mount a uImage as a loopback device (that I'm aware of).
-Robin
QuoteReplyEditDelete
2009-01-18 07:12:02 Re: Another Kernel panic - not syncing: No init found.... help!
Tom Whiteley (UNITED KINGDOM)
Message: 68067
Finally solved the problem!
I ditched colinux and installed fedora on sun virtual box (very good product would recommend it to all). I ran the default build and it worked first time!!!! To be honest I'm not really sure what the problem was, I'm guessing I may have not installed the correct toolchain or something similar.
QuoteReplyEditDelete