Kernel panic - not syncing: No init found. Try passing init= option to kernel.

GoogleGroups
1

I have a C4 revision of the board. I am trying to bring up my board to
load from NAND.

I created the SD card based off of this page:

http://code.google.com/p/beagleboard/wiki/BeagleboardRevC3Validation

Every way I have tried I keep getting the Kernel panic that is listed
below. Any help would be greatly appreciated.

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand

U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)

I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 256 MB
NAND: 256 MiB
*** Warning - bad CRC or NAND, using default environment

MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision Ax/Bx
Serial #5c8a0004000000000403951c0700800d
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org # boot
  bootm boot bootd
OMAP3 beagleboard.org # bootargs
Unknown command 'bootargs' - try 'help'
OMAP3 beagleboard.org # boot
No MMC card found
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name: Linux-2.6.28-omap1
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2577980 Bytes = 2.5 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing
Linux.....................................................................................................................................................................
done, booting the kernel.
Linux version 2.6.28-omap1 (root@tiioss) (gcc version 4.2.1
(CodeSourcery Sourcery G++ Lite 2007q3-51)) #2 Thu Feb 19 12:45:34 IST
2009
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.1
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
Reserving 15728640 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mtdblock4 rw
rootfstype=jffs2
Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 1024 (order: 10, 4096 bytes)
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 238848KB available (4776K code, 425K data, 168K init)
Calibrating delay loop... 491.57 BogoMIPS (lpj=1921024)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 532 bytes
regulator: core version 0.5
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
SCSI subsystem initialized
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
Bluetooth: Core ver 2.13
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
        (start_freq - end_freq @ bandwidth), (max_antenna_gain,
max_eirp)
        (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 467
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver zd1211rw
usbcore: registered new interface driver rndis_wlan
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver usb8xxx
usbcore: registered new interface driver rtl8187
usbcore: registered new interface driver rt2500usb
usbcore: registered new interface driver rt73usb
usbcore: registered new interface driver p54usb
i2c /dev entries driver
input: triton2-pwrbutton as /class/input/input0
triton2 power button driver initialized
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x00000000-0x00080000 : "X-Loader"
0x00080000-0x00260000 : "U-Boot"
0x00260000-0x00280000 : "U-Boot Env"
0x00280000-0x00680000 : "Kernel"
0x00680000-0x10000000 : "File System"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 22:c7:b4:54:ef:d6
usb0: HOST MAC c6:d7:41:36:46:0e
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input1
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
twl4030_rtc twl4030_rtc: Power up reset detected.
twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI USB driver ver 2.10
usbcore: registered new interface driver hci_usb
Bluetooth: Broadcom Blutonium firmware driver ver 1.2
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.10
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
Registered led device: beagleboard::usr0
Registered led device: beagleboard::usr1
leds-gpio: probe of leds-gpio failed with error -22
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
usbcore: registered new interface driver snd-usb-audio
ASoC version 0.13.2
OMAP3 Beagle SoC init
TWL4030 Audio Codec init
asoc: twl4030 <-> omap-mcbsp-dai-(link_id) mapping ok
ALSA device list:
  #0: omap3beagle (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ieee80211: 802.11 data/management/control stack, git-1.1.13

2

Forgot to add can get the Kernel to boot off of the SD card.

Anyone able to help?

3

I am able to boot the kernel off of the SD card, I forgot to mention
that before.

Anyone have any insight?

4

you can boot from the SD card…
Its very simple. Just erase the nand completely and then, put the image files in the SD card and boot…
Dont put, boot.scr… load the SD card with mlo, uboot.bin and uimage only…

and that kernel panic comes whn the files system does not match with the one that is supported by nand…
Im not pretty sure about it…
But, you try booting from SD card. that should solve your problem…

regards,

5

Thank you for your reply,

I am able to boot from the card but was hoping to be able to boot from
the NAND. I will search for different files that should work better
with the NAND configuration.

6

Are you able to see the display on DVI monitor or Touchpanel?
I am not able to see it…

because even i face the init problem, which i don’t actually understand.

" Failed to execute /init. Attempting defaults…
INIT: version 2.86 booting "

What could it be?

Thanks…

7

Dear Ashely,

I am not really a expert on this subject but I noticed the following in your log.

I have a C4 revision of the board. I am trying to bring up my board to
load from NAND.

I created the SD card based off of this page:

http://code.google.com/p/beagleboard/wiki/BeagleboardRevC3Validation

This page is hardly discussing how to load the boot loader, uImage and rootfs into your NAND.
How did you do those steps?
Or did you put the ramdisk image into the NAND?

Starting kernel …

Uncompressing
Linux…
done, booting the kernel.
Linux version 2.6.28-omap1 (root@tiioss) (gcc version 4.2.1
(CodeSourcery Sourcery G++ Lite 2007q3-51)) #2 Thu Feb 19 12:45:34 IST
2009
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.1
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
Reserving 15728640 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mtdblock4 rw
rootfstype=jffs2

The Kernel is expecting to have the root file system in /dev/mtdblock4 and the format of the rootfs is jffs2
This mtdblock4 is just one of the sections you (or the script should) have made.
Did you prepare for this?

Creating 5 MTD partitions on “omap2-nand”:
0x00000000-0x00080000 : “X-Loader”
0x00080000-0x00260000 : “U-Boot”
0x00260000-0x00280000 : “U-Boot Env”
0x00280000-0x00680000 : “Kernel”
0x00680000-0x10000000 : “File System”

Here you see the sections. mtdblock4 is indeed the “File System” this should have the rootfs.

JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr
subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead,
0 orphan) found.
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 168K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option
to kernel.

And you get this error because there is no valid rootfs at that /dev/mtdblock4
After the kernel starts it tries to start the “init” program to bring the other parts of the system up but that program is not there.

I am not an expert but I think you did not put your rootfs correctly into the NAND or you did not have the correct rootfs. (Missing the init process for instance.)

Greetings,

Han

8

Yeah, That is correct…
The rootfs format mismatch creates init faliures…

But, Han, Do you have any ides about why the display of anykind [ LCD/DVI ] does not work??
All the drivers are installed…

Thanks…

9

I saw your other mails as well. I have no idea why you do not see anything.

Did you solve your “init” problem already?

I will need at least a log and a bit more complete information about where you got your rootfs and kernel etc.
But again, some monitors are not working so well with the beagleboard; did you try with a different monitor already?

Greetings,

Han

10

Here, i have attached the log file…
And i did not solve my init problem… But, it boots up, without giving the display…
Currently i run the board through Hyperterminal of my host computer.

i have tried with different types of displays… But, no progress…

i got the linux kernel from http://code.google.com/p/ema3530/downloads/list
i got the angstrom distribution from Narcissus.

What else…

Thanks…

lognew (32.8 KB)

11

Here, i have attached the log file...
And i did not solve my init problem.. But, it boots up, without giving the
display..
Currently i run the board through Hyperterminal of my host computer.

i have tried with different types of displays.. But, no progress...

i got the linux kernel from http://code.google.com/p/ema3530/downloads/list
i got the angstrom distribution from Narcissus.

Pls check your bootarg and correct it.I think still the Display
definition is missing in your bootarg.

12

I try to understand your problem. Your log looks to be incomplete. The beginning is missing. Do you have a log that really starts with the xloader?
This is needed to see from where you are loading your kernel and rootfs and to see the kernel command line.

So you use the “special” ema3530 kernel in combination with the angstrom rootfs. Which version?

This rootfs is working: you can login into the system?

In case the init process is really not starting then you will be not able to login.

Greetings,

Han

13

Hi han,

I have added the full log file. From beginning till the End…
You may have a look at that…
The rootfs works… i guess.
i can log into the system from hyperterminal.
I cannot see the x-11 environment .

PS: there is no problem with the hardware, since we have tested them completely.

Thanks and regards.

14

OMAP3 Stalker # printenv
bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if ri
bootdelay=3
baudrate=115200
ipaddr=192.168.1.76
serverip=192.168.1.70
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile=uImage
loadaddr=0x82000000
console=ttyS0,115200n8
vram=12M
defaultdisplay=dvi
mpurate=600
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
nandroot=ubi0:rootfs ubi.mtd=4
nandrootfstype=ubifs
mmcargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi:${dvimo}
nandargs=setenv bootargs console=${console} vram=${vram} omapfb.mode=dvi:${dvim}
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc …; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc …; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand …; run nandargs; nand read ${loadaddr} 280000}
ethaddr=02:c0:05:01:b0:05
dieid#=170000040000000004036ac00501b005
ethact=smc911x-0
dvimode=1024x768MR-16@60
default=display dvi
stdin=serial
stdout=serial
stderr=serial
bootargs=rootwait omapfb.video_mode=1024x768MR-16@60

15

I find your environment variables complicated; with so many options is it very easily that something does not work as expected. What do you expect that is happening?
And are you sure that that is also happening?

Are you running from the SD card? What is your kernel command line?

A full boot log would be really helpful.

Greetings, Han

16

here is the full boot log file…
i am running from SD card.
i dont have any clue of what is happening…
please see the full boot log…

log-full (25.6 KB)

17

This is in your log:

OMAP3 Stalker # setenv bootargs console=tty0
OMAP3 Stalker # saveenv
Saving Environment to NAND…
Erasing Nand…
Erasing at 0x260000 – 100% complete.
Writing to Nand… done
OMAP3 Stalker # boot

Here you are overwriting your bootargs, but that does not show up later on.

Uncompressing Linux…
Linux version 2.6.32-rc5 (yashie@dabba) (gcc version 4.3.3 (Sourcery G++ Lite 21
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3 STALKER
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1

  • l2cache : Y
  • iva : Y
  • sgx : Y
  • neon : Y
  • isp : Y
  • 720m : N
    SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
    Reserving 12582912 bytes SDRAM for VRAM
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
    Kernel command line: console=ttyS0,115200n8 vram=12M omapfb.mode=dvi:1024x768MRt
    Unknown boot option omapfb.video_mode=dvi:1024x768MR-16@60': ignoring Unknown boot option omapfb.debug=y’: ignoring
    Unknown boot option `omap-dss.def_disp=dvi’: ignoring
    PID hash table entries: 512 (order: -1, 2048 bytes)

There is for sure going something wrong with your kernel command line. These values are not the values you have defined as bootargs as you have shown in your previous email.

Do you have a boot.src on your SD card?
What is the contents of that script?
You have to clean up your enviroment variables in u-boot, currently are things mixed up.

It can be that your kernel does not support the bootargs for some reason…

18

No, i do not have boot.scr in my SD card…

how do i clean up the environmental variables in u-boot?

In the previous mail… the two logfiles that i have provided are different.
One was when i boot it from SD card, another was when i boot it from NAND.

I do not know the exact reason for why the kernel doesnt accept the boot args…

Thanks…
bumble…