Network boot - Kernel panic - not syncing: No init found.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Network boot - Kernel panic - not syncing: No init found.

Jump to solution
4,537 Views
pt
Senior Contributor I

Hi PeterChan

I am using linux 2.6.35 kernel version on MCIMX28EVK.

uboot version: 2009

MX28 U-Boot > printenv

bootargs=console=ttyAM0,115200n8

bootdelay=3

baudrate=115200

ipaddr=192.168.1.103

netmask=255.255.255.0

bootfile="uImage"

loadaddr=0x42000000

bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp fec_mac=${ethaddr}

bootcmd_net=run bootargs_nfs; dhcp; bootm

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhcp fec_mac=${ethaddr}

bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm

ethact=FEC0

serverip=192.168.2.107

nfsroot=/home/dtsuser/ltib/ltib/rootfs/boot/

bootcmd=run bootcmd_net

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Sep 26 2014 - 16:03:20)

/*.................................................................*/

I am facing "no init found" issue.Please help me to solve this.

PowerPrep start initialize power...

Battery Voltage = 4.24VSep  1 201417:27:27

FRAC 0x92925552

memory type is DDR2

                   Wait for ddr ready 1power 0x00820710

Frac 0x92925552

start change cpu freq

hbus 0x00000003

cpu 0x00010001

U-Boot 2009.08 (Sep 26 2014 - 16:03:20)

Freescale i.MX28 family

CPU:   454 MHz

BUS:   151 MHz

EMI:   205 MHz

GPMI:   24 MHz

DRAM:  128 MB

MMC:   IMX_SSP_MMC: 0, IMX_SSP_MMC: 1

In:    serial

Out:   serial

Err:   serial

Net:   got MAC address from IIM: 00:04:9f:02:b6:94

FEC0

Hit any key to stop autoboot:  0

BOOTP broadcast 1

FEC: Link is down 7809

BOOTP broadcast 2

DHCP client bound to address 192.168.2.110

Using FEC0 device

TFTP from server 192.168.2.107; our IP address is 192.168.2.110

Filename 'uImage'.

Load address: 0x42000000

Loading: #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #

done

Bytes transferred = 2998056 (2dbf28 hex)

## Booting kernel from Legacy Image at 42000000 ...

   Image Name:   Linux-2.6.35.3-g779560d-dirty

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2997992 Bytes =  2.9 MB

   Load Address: 40008000

   Entry Point:  40008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Linux version 2.6.35.3-g779560d-dirty (dtsuser@dtsmachine) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #21 PREEMPT Wed Sep 17 12:49:16 IST 2014

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: Freescale MX28EVK board

Memory policy: ECC disabled, Data cache writeback

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512

Kernel command line: console=ttyAM0,115200n8 root=/dev/nfs ip=dhcp nfsroot=192.168.2.107:/home/dtsuser/ltib/ltib/rootfs/boot/,v3,tcp fec_mac=

PID hash table entries: 512 (order: -1, 2048 bytes)

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

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

Memory: 128MB = 128MB total

Memory: 123432k/123432k available, 7640k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)

    vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)

    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)

    modules : 0xbf000000 - 0xc0000000   (  16 MB)

      .init : 0xc0008000 - 0xc0034000   ( 176 kB)

      .text : 0xc0034000 - 0xc05ce000   (5736 kB)

      .data : 0xc05ce000 - 0xc0611400   ( 269 kB)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

        RCU-based detection of stalled CPUs is disabled.

        Verbose stalled-CPUs detection is disabled.

NR_IRQS:288

Console: colour dummy device 80x30

console [ttyAM0] enabled

Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)

pid_max: default: 32768 minimum: 301

Security Framework initialized

SELinux:  Initializing.

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

regulator: core version 0.5

NET: Registered protocol family 16

regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal

regulator: vdddbo: 800 <--> 1575 mV fast normal

regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal

vddio = 3380000, val=10

regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal

regulator: overall_current: fast normal

regulator: vbus5v:

regulator: mxs-duart-1: fast normal

regulator: mxs-bl-1: fast normal

regulator: mxs-i2c-1: fast normal

regulator: mmc_ssp-1: fast normal

regulator: mmc_ssp-2: fast normal

regulator: charger-1: fast normal

regulator: power-test-1: fast normal

regulator: cpufreq-1: fast normal

i.MX IRAM pool: 124 KB@0xc8820000

usb DR wakeup device is registered

IMX usb wakeup probe

audit: cannot initialize inotify handle

bio: create slab <bio-0> at 0

SCSI subsystem initialized

Freescale USB OTG Driver loaded, $Revision: 1.55 $

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Advanced Linux Sound Architecture Driver Version 1.0.23.

Bluetooth: Core ver 2.15

NET: Registered protocol family 31

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

cfg80211: Calling CRDA to update world regulatory domain

NetLabel: Initializing

NetLabel:  domain hash size = 128

NetLabel:  protocols = UNLABELED CIPSOv4

NetLabel:  unlabeled traffic allowed by default

Switching to clocksource mxs clock source

NET: Registered protocol family 2

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

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

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

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Bus freq driver module loaded

IMX usb wakeup probe

usb h1 wakeup device is registered

mxs_cpu_init: cpufreq init finished

audit: initializing netlink socket (disabled)

type=2000 audit(0.660:1): initialized

VFS: Disk quotas dquot_6.5.2

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.

msgmni has been set to 241

alg: No test for stdrng (krng)

cryptodev: driver loaded.

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

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

Console: switching to colour frame buffer device 100x30

mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART

mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0

Found APPUART 3.1.0

mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1

Found APPUART 3.1.0

mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2

Found APPUART 3.1.0

mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3

Found APPUART 3.1.0

mxs-auart.4: ttySP4 at MMIO 0x80072000 (irq = 116) is a mxs-auart.4

Found APPUART 3.1.0

brd: module loaded

loop: module loaded

i.MX GPMI NFC

NFC: Version 1, 8-chip GPMI and BCH

gpmi-nfc: probe of gpmi-nfc.0 failed with error 1

mxs-spi mxs-spi.0: Max possible speed 120000 = 120000000/2 kHz

mxs-spi mxs-spi.0: at 0x80014000 mapped to 0xF0014000, irq=84, bus 1, DMA ver_major 4

FEC Ethernet Driver

fec_enet_mii_bus: probed

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci: irq 93, io base 0x80080000

fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.0: irq 92, io base 0x80090000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

ARC USBOTG Device Controller driver (1 August 2005)

mice: PS/2 mouse device common for all mice

input: mxs-kbd as /devices/platform/mxs-kbd.0/input/input0

input: MXS touchscreen as /devices/virtual/input/input1

MXS RTC driver v1.0 hardware v2.3.0

mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

mxs-pxp mxs-pxp.0: initialized

mxs watchdog: initialized, heartbeat 19 sec

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCI H4 protocol initialized

Bluetooth: HCI BCSP protocol initialized

Bluetooth: Generic Bluetooth SDIO driver ver 0.1

mxs-mmc: MXS SSP Controller MMC Interface driver

mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96

__mxs_reset_block(f0012000): timeout when resetting

mxs-mmc mxs-mmc.1: mmc1: MXS SSP MMC DMAIRQ 83 ERRIRQ 97

dcp dcp.0: DCP crypto enabled.!

usbcore: registered new interface driver hiddev

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

sgtl5000-i2c 0-000a: SGTL5000 revision 17

mmc0: new high speed SDHC card at address e624

mmcblk0: mmc0:e624 SU04G 3.69 GiB

mmcblk0: p1 p2 p3

mxs-spdif mxs-spdif.0: MXS SPDIF Audio Transmitter

No device for codec mxs spdif

No device for DAI mxs spdif

No device for DAI mxs-saif

No device for DAI mxs-spdif

asoc: SGTL5000 <-> mxs-saif mapping ok

Failed to add route LINE_OUT->Ext Spk

asoc: mxs spdif <-> mxs-spdif mapping ok

ALSA device list:

  #0: mxs-evk (SGTL5000)

  #1: mxs-evk (mxs spdif)

Netfilter messages via NETLINK v0.30.

nf_conntrack version 0.5.0 (1928 buckets, 7712 max)

CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use

nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or

sysctl net.netfilter.nf_conntrack_acct=1 to enable it.

ctnetlink v0.93: registering with nfnetlink.

xt_time: kernel timezone is -0000

ip_tables: (C) 2000-2006 Netfilter Core Team

ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully

arp_tables: (C) 2002 David S. Miller

TCP cubic registered

NET: Registered protocol family 17

Bridge firewalling registered

Ebtables v2.0 registered

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

Bluetooth: L2CAP ver 2.14

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO (Voice Link) ver 0.6

Bluetooth: SCO socket layer initialized

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>

All bugs added by David S. Miller <davem@redhat.com>

lib80211: common routines for IEEE802.11 drivers

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 06:14:01 UTC (22441)

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)

eth1: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)

Sending DHCP requests .

PHY: 0:00 - Link is Up - 100/Full

DHCP/BOOTP: Ignoring delayed packet

DHCP/BOOTP: Ignoring delayed packet

., OK

IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.2.110

IP-Config: Complete:

     device=eth0, addr=192.168.2.110, mask=255.255.255.0, gw=192.168.2.1,

     host=192.168.2.110, domain=, nis-domain=(none),

     bootserver=0.0.0.0, rootserver=192.168.2.107, rootpath=

Looking up port of RPC 100003/3 on 192.168.2.107

Looking up port of RPC 100005/3 on 192.168.2.107

VFS: Mounted root (nfs filesystem) on device 0:14.

Freeing init memory: 176K

Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

Backtrace:

[<c00384a8>] (dump_backtrace+0x0/0x114) from [<c047b5cc>] (dump_stack+0x18/0x1c)

r7:00000013 r6:c00548c4 r5:c002c35c r4:c0612358

[<c047b5b4>] (dump_stack+0x0/0x1c) from [<c047b648>] (panic+0x78/0xf4)

[<c047b5d0>] (panic+0x0/0xf4) from [<c00345fc>] (init_post+0xb4/0xdc)

r3:00000000 r2:c7dd5800 r1:c7dd5900 r0:c0544582

[<c0034548>] (init_post+0x0/0xdc) from [<c00084fc>] (kernel_init+0x12c/0x170)

r5:c002c35c r4:c0611480

[<c00083d0>] (kernel_init+0x0/0x170) from [<c00548c4>] (do_exit+0x0/0x6dc)

r5:c00083d0 r4:00000000

Labels (2)
0 Kudos
Reply
1 Solution
3,219 Views
gonfer
Contributor V

Hi Pt A R,

it looks you are trying to access your RFS in a wrong location. Please, check your U-boot "nfsroot" definition:

nfsroot=/home/dtsuser/ltib/ltib/rootfs/boot/

I think it should be something like:

nfsroot=/home/dtsuser/ltib/ltib/rootfs


HTH,

Gonzalo.

View solution in original post

0 Kudos
Reply
6 Replies
3,220 Views
gonfer
Contributor V

Hi Pt A R,

it looks you are trying to access your RFS in a wrong location. Please, check your U-boot "nfsroot" definition:

nfsroot=/home/dtsuser/ltib/ltib/rootfs/boot/

I think it should be something like:

nfsroot=/home/dtsuser/ltib/ltib/rootfs


HTH,

Gonzalo.

0 Kudos
Reply
3,219 Views
pt
Senior Contributor I

Hi gonfer

Thanks.But now I am facing another issue.

.............................................................

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>

All bugs added by David S. Miller <davem@redhat.com>

lib80211: common routines for IEEE802.11 drivers

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 02:24:50 UTC (8690)

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)

eth1: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)

Sending DHCP requests .

PHY: 0:00 - Link is Up - 100/Full

.., OK

IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.2.114

IP-Config: Complete:

     device=eth0, addr=192.168.2.114, mask=255.255.255.0, gw=192.168.2.1,

     host=192.168.2.114, domain=, nis-domain=(none),

     bootserver=0.0.0.0, rootserver=192.168.2.107, rootpath=

Looking up port of RPC 100003/3 on 192.168.2.107

Looking up port of RPC 100005/3 on 192.168.2.107

VFS: Mounted root (nfs filesystem) on device 0:14.

Freeing init memory: 176K

starting pid 1168, tty '': '/etc/rc.d/rcS'

Mounting /proc and /sys

Starting the hotplug events dispatcher udevd

Synthesizing initial hotplug events

Setting the hostname to freescale

Mounting filesystems

Booted NFS, not relocating: /tmp /var

mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

Running sysctl

Setting up networking on loopback device:

Setting up networking on eth0:

nfs: server 192.168.2.107 not responding, still trying

nfs-not-responding.png

Regards

Pt

0 Kudos
Reply
3,219 Views
eliedebrauwer
Contributor II

Hello Pt,

Well, since you get the message 'Setting up networking on eth0' right before you loose track of your NFS connection it's likely that you reconfiguring your ethernet caused the NFS server to become unreachable. You could try making sure the ethernet configuration does not happen by editing your network settings on your nfs rootfs.

hth

3,219 Views
gonfer
Contributor V

I agree with Elie.

You could also try to disable "Start Networking" under Ltib. I don't remember exactly where you can find this option but you will find it easily.

Regards,

Gonzalo.

3,219 Views
pt
Senior Contributor I

Hi eliedebrauwer, gonfer

I have disabled that option. Now it starts working.

logged in.

Thanks to all.

Regards

Pt

0 Kudos
Reply
3,219 Views
igorpadykov
NXP Employee
NXP Employee

Hi Pt A R

seems it did not find proper nfsroot or it is different version from kernel.

BTW is it working wth demo

L2.6.35_1.1.0_DEMO_IMAGE   ?

Best regards

igor

0 Kudos
Reply