# Kernel panic - not syncing ...
**URL:** https://forums.digi.com/t/kernel-panic-not-syncing/6139
**Category:** Linux
**Created:** [March 31, 2010, 12:23pm UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139 "2010-03-31T12:23:49Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@fritz](https://forums.digi.com/u/fritz)
#### Post date: [March 31, 2010, 12:23pm UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139/1 "2010-03-31T12:23:49Z")
Hi everybody!
I am working with my special Digi 9210 on a Dev Board, trying this an that, and suddenly, I am not able to boot anymore. Here is a copy of the output:
```auto
U-Boot 1.1.6 (Feb 8 2010 - 16:44:56 - GCC 4.3.2) dub-revf4
for Digi Connect ME 9210 on Development Board
DRAM: 16 MB
Flash: 8 MB
CPU: NS9210 @ 74.95680 MHz, SYS 299.82720 MHz, AHB 74.95680 MHz, Rev 0
Strap: 0x077d
Autoscript from TFTP... [not available]
Hit any key to stop autoboot: 0
TFTP from server 192.168.1.101; our IP address is 192.168.1.50
Filename 'uImage-cme9210js'.
Load address: 0x200000
Loading: #################################################################
###########
done
Bytes transferred = 1084128 (108ae0 hex)
linux will be booted now
## Booting image at 00200000 ...
Image Name: Linux-2.6.28.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1084064 Bytes = 1 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
fixing Load address and Entry Point: 00200040 00200040 ...
XIP Kernel Image ... OK
Starting kernel ...
Uncompressing Linux........................................................................ done, booting the kernel.
Linux version 2.6.28.10 (fgh@del52) (gcc version 4.3.2 (GCC) ) #1 Wed Mar 31 13:32:48 CEST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Digi Connect ME 9210 on Devboard
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line: ip=192.168.1.50:192.168.1.101:192.168.1.1:255.255.255.0:cme9210js:eth0:off console=ttyNS0,38400 root=nfs nfsroot=192.168.1.101:/exports/nfsroot-cme9210js mtdparts=physmap-flash.0:0x30000(U-Boot),0x20000@0x30000(NVRAM),0x140000@0x50000(Kernel),0x180000@0x190000(RootFS),0x4f0000@0x310000(UserFS)
PID hash table entries: 64 (order: 6, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 16MB = 16MB total
Memory: 13952KB available (2032K code, 133K data, 76K init)
Calibrating delay loop... 37.06 BogoMIPS (lpj=185344)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
ns921x CPU frequency change support initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET:rotocol family 1
squashfs: version 3.4 (2008/08/26) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 27
io scheduler noop registered (default)
ns921x-serial.0: ttyNS0 at MMIO 0x90010000 (irq = 7) is a NS921X
console [ttyNS0] enabled
ns921x-serial.2: ttyNS2 at MMIO 0x90020000 (irq = 9) is a NS921X
Digi NS921x UART driver
ns9xxx-eth-mii: probed
ns9xxx-eth ns9xxx-eth: eth0 at MMIO c185c000
Digi NS9XXX Ethernet driver
physmap platform flash device: 10000000 at 50000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
5 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 5 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "U-Boot"
0x00030000-0x00050000 : "NVRAM"
0x00050000-0x00190000 : "Kernel"
0x00190000-0x00310000 : "RootFS"
0x00310000-0x00800000 : "UserFS"
ns9xxx-wdt ns9xxx-wdt: NS9xxx watchdog timer at 0xc185a174
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IP-Config: Complete:
device=eth0, addr=192.168.1.50, mask=255.255.255.0, gw=192.168.1.1,
host=cme9210js, domain=, nis-domain=(none),
bootserver=192.168.1.101, rootserver=192.168.1.101, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.101
Looking up port of RPC 100005/1 on 192.168.1.101
VFS: Mounted root (nfs filesystem).
Freeing init memory: 76K
USAGE: /sbin/init
Kernel panic - not syncing: Attempted to kill init!
```
What did i do wrong?
Thx, Fritz.
ps: there is a older rootfs-image in the flash, which is booting perfectly.
---
### Author:  [@LeonidM](https://forums.digi.com/u/LeonidM)
#### Post date: [March 31, 2010, 1:09pm UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139/2 "2010-03-31T13:09:43Z")
it somehow does not like your
Kernel command line: ip=192.168.1.50:192.168.1.101:192.168.1.1:255.255.255.0:cme9210js:eth0:off console=ttyNS0,38400 root=nfs nfsroot=192.168.1.101:/exports/nfsroot-cme9210js mtdparts=physmap-flash.0:0x30000(U-Boot),0x20000@0x30000(NVRAM),0x140000@0x50000(Kernel),0x180000@0x190000
New kernel in FLASH will boot with old rootfs in FLASH? did you try to put new rootfs in FLASH? or is it an NFS problem?
---
### Author:  [@fritz](https://forums.digi.com/u/fritz)
#### Post date: [April 1, 2010, 7:59am UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139/3 "2010-04-01T07:59:08Z")
why? it is the same as in the working flash-file:
```auto
U-Boot 1.1.6 (Feb 8 2010 - 16:44:56 - GCC 4.3.2) dub-revf4
for Digi Connect ME 9210 on Development Board
DRAM: 16 MB
Flash: 8 MB
CPU: NS9210 @ 74.95680 MHz, SYS 299.82720 MHz, AHB 74.95680 MHz, Rev 0
Strap: 0x077d
Autoscript from TFTP... [not available]
Hit any key to stop autoboot: 0
CME9210 # dboot linux flash
Reading: complete
linux will be booted now
## Booting image at 00200000 ...
Image Name: Linux-2.6.28.10
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1088828 Bytes = 1 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
fixing Load address and Entry Point: 00200040 00200040 ...
XIP Kernel Image ... OK
Starting kernel ...
Uncompressing Linux........................................................................ done, booting the kernel.
Linux version 2.6.28.10 (fgh@del52) (gcc version 4.3.2 (GCC) ) #9 Mon Mar 1 16:15:25 CET 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Digi Connect ME 9210 on Devboard
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line: ip=192.168.1.50:192.168.1.101:192.168.1.1:255.255.255.0:cme9210js:eth0:off console=ttyNS0,38400 root=/dev/mtdblock3 rootfstype=squashfs rw mtdparts=physmap-flash.0:0x30000(U-Boot),0x20000@0x30000(NVRAM),0x140000@0x50000(Kernel),0x180000@0x190000(RootFS),0x4f0000@0x310000(UserFS)
PID hash table entries: 64 (order: 6, 256 bytes)
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 16MB = 16MB total
Memory: 13944KB available (2040K code, 134K data, 76K init)
Calibrating delay loop... 37.06 BogoMIPS (lpj=185344)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
ns921x CPU frequency change support initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.4 (2008/08/26) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 27
io scheduler noop registered (default)
ns921x-serial.0: ttyNS0 at MMIO 0x90010000 (irq = 7) is a NS921X
console [ttyNS0] enabled
ns921x-serial.2: ttyNS2 at MMIO 0x90020000 (irq = 9) is a NS921X
Digi NS921x UART driver
ns9xxx-eth-mii: probed
ns9xxx-eth ns9xxx-eth: eth0 at MMIO c185c000
Digi NS9XXX Ethernet driver
physmap platform flash device: 10000000 at 50000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
5 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 5 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "U-Boot"
0x00030000-0x00050000 : "NVRAM0x00050000-0x00190000 : "Kernel"
0x00190000-0x00310000 : "RootFS"
0x00310000-0x00800000 : "UserFS"
ns9xxx-wdt ns9xxx-wdt: NS9xxx watchdog timer at 0xc185a174
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IP-Config: Complete:
device=eth0, addr=192.168.1.50, mask=255.255.255.0, gw=192.168.1.1,
host=cme9210js, domain=, nis-domain=(none),
bootserver=192.168.1.101, rootserver=192.168.1.101, rootpath=
VFS: Mounted root (squashfs filesystem) readonly.
Freeing init memory: 76K
Mounting kernel file systems: /sys /dev/pts.
Mounting tmp file systems (tmpfs): /tmp.
net eth0: link up (100/full)
Creating nodes via configuration file... done
Mounting fstab configured file systems... done
Starting syslog daemon: OK
Starting network.
Starting vsftpd server: OK
BusyBox v1.15.2 (2009-12-03 15:11:08 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ #
```
maybe i have a problem with nfs. how can i check that?
---
### Author:  [@fritz](https://forums.digi.com/u/fritz)
#### Post date: [April 1, 2010, 8:13am UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139/4 "2010-04-01T08:13:18Z")
Ah, OK, it`s not the nfs.
I used an on old backup file which is working.
So the problem is my actual configuration.
But where do I start looking?
---
### Author:  [@fritz](https://forums.digi.com/u/fritz)
#### Post date: [April 1, 2010, 8:25am UTC](https://forums.digi.com/t/kernel-panic-not-syncing/6139/5 "2010-04-01T08:25:50Z")
I am stunned.
today it is working.
nothing changed.
1.