Home/Support/Support Forum/Kernel boot problem when moving from the dev board
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Kernel boot problem when moving from the dev board

0 votes
We are changing our 9M 2443 from WinCE to Linux. I have went through the kernel settings removing drivers for stuff we do not use (TFT, hssd, USB). the kernel stiif boots fine on the dev board but on our host it hangs... here are the boot messages, maybe someone else has run into this situation...

## Booting image at 30200000 ...
Image Name: Linux-2.6.35.14
Created: 2015-02-18 17:39:13 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1585912 Bytes = 1.5 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
fixing Load address and Entry Point: 30200040 30200040 ...
XIP Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.14 (marc@ubuntu) (gcc version 4.4.6 (crosstool-NG 1.12.1) ) #1 Wed Feb 18 12:39:10 EST 2015
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: ConnectCore 9M 2443 on a JSCC9M2443 Devboard
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
CPU S3C2443 (id 0x32443001)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 534.000 MHz, cpu 534.000 MHz, mem 133.500 MHz, pclk 66.750 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
CPU: MPLL on 534.000 MHz, cpu 534.000 MHz, mem 133.500 MHz, pclk 66.750 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: ip=192.168.1.4:192.168.1.241:192.168.1.1:255.255.255.0:cc9m2443js:eth0:off console=ttySAC0,38400 root=/dev/mtdblock4

rootfstype=jffs2 rw mtdparts=onboard_boot:0xc0000(U-Boot),0x80000@0xc0000(NVRAM),0x100000@0x140000(Splash),0x300000@0x240000

(Kernel),0x7ac0000@0x540000(RootFS) video=displayfb:VGA
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: 64MB = 64MB total
Memory: 61696k/61696k available, 3840k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc4800000 - 0xe0000000 ( 440 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0026000 ( 120 kB)
.text : 0xc0026000 - 0xc02f2000 (2864 kB)
.data : 0xc02f2000 - 0xc030bce0 ( 104 kB)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:99
irq: clearing subpending status 00000002
Console: colour dummy device 80x30
console [ttySAC0] enabled
Calibrating delay loop... 266.24 BogoMIPS (lpj=665600)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Starting Linux on ARM ConnectCore 9M 2443
S3C Power Management, Copyright 2004 Simtec Electronics
S3C2443: Initialising architecture
S3C2443: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c480c000, irq 88
DMA channel 1 at c480c100, irq 89
DMA channel 2 at c480c200, irq 90
DMA channel 3 at c480c300, irq 91
DMA channel 4 at c480c400, irq 92
DMA channel 5 at c480c500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
s3c-i2c s3c2410-i2c: slave address 0x00
s3c-i2c s3c2410-i2c: bus frequency set to 379 KHz
s3c-i2c s3c2410-i2c: i2c-1: S3C I2C adapter
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
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 120
io scheduler noop registered (default)
Console: switching to colour frame buffer device 80x30
s3c2443fb-tft: frame buffer fb0: s3c2443fb-tft, display config VGA
s3c2443-adc: ADC available on MAJOR 253
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2410 PORT A
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2410 PORT B
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2410 PORT C
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2410 PORT D
brd: module loaded
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c24xx-nand s3c2410-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2410-nand: System booted from NAND
s3c24xx-nand s3c2410-nand: NAND hardware ECC
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
5 cmdlinepart partitions found on MTD device onboard_boot
s3c2410_nand_update_chip: chip c3edfd90: 11
Scanning device for bad blocks
Bad eraseblock 333 at 0x0000029a0000
Creating 5 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x000000000000-0x0000000c0000 : "U-Boot"
0x0000000c0000-0x000000140000 : "NVRAM"
0x000000140000-0x000000240000 : "Splash"
0x000000240000-0x000000540000 : "Kernel"
0x000000540000-0x000008000000 : "RootFS"
s3c24xx-nand s3c2410-nand: clock idle support enabled
spi-s3c2443: Probing device with the ID 0
spi-s3c2443: Input clock frequency: 66750000 Hz
mapped channel 3 to 0
mapped channel 4 to 1
smsc911x: Driver version 2008-10-21.
smsc911x-mdio: probed
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
net eth0: MAC Address: 00:40:9d:72:7d:c6
mice: PS/2 mouse device common for all mice
rtc-ds1307 1-0068: SET TIME!
rtc-ds1307 1-0068: rtc core: registered ds1337 as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
TCP cubic registered
NET: Registered protocol family 17
rtc-ds1307 1-0068: setting system clock to 2000-01-01 00:17:58 UTC (946685878)
net eth0: SMSC911x/921x identified at 0xc5200000, IRQ: 53
IP-Config: Complete:
device=eth0, addr=192.168.1.4, mask=255.255.255.0, gw=192.168.1.1,
host=cc9m2443js, domain=, nis-domain=(none),
bootserver=192.168.1.241, rootserver=192.168.1.241, rootpath=
VFS: Mounted root (jffs2 filesystem) on device 31:4.
devtmpfs: mounted
Freeing init memory: 120K
request_module: runaway loop modprobe net-pf-10

here it is stopped

Thanks
asked Feb 18, 2015 in Linux by marcL New to the Community (2 points)

Please log in or register to answer this question.

2 Answers

0 votes
What development board are you referring to?
answered Feb 18, 2015 by mvut Veteran of the Digi Community (12,001 points)
It work fine on the DIGI development board (ConnectCore 9M 2443 Digi JumpStart Kit)
When moving to ours it hangs. From googling it semms the message is IPV6 related and recursive call to loading the module (Even though not enabled in the kernel). I have made a kernel with modules disabled and will try it tomorrow, I don't believe we have much need for that feature anyway.
0 votes
A new end with modules disabled... Still looking

IP-Config: Complete:
device=eth0, addr=192.168.1.4, mask=255.255.255.0, gw=192.168.1.1,
host=cc9m2443js, domain=, nis-domain=(none),
bootserver=192.168.1.241, rootserver=192.168.1.241, rootpath=
VFS: Mounted root (jffs2 filesystem) on device 31:4.
devtmpfs: mounted
Freeing init memory: 124K
Kernel panic - not syncing: Attempted to kill init!
Backtrace:
[<c002b2c0>] (dump_backtrace+0x0/0x114) from [<c0233370>] (dump_stack+0x18/0x1c)
r7:00000001 r6:c3c15bc0 r5:00000000 r4:c02be7d8
[<c0233358>] (dump_stack+0x0/0x1c) from [<c02333d4>] (panic+0x60/0xdc)
[<c0233374>] (panic+0x0/0xdc) from [<c003d17c>] (do_exit+0x70/0x5bc)
r3:c02ae018 r2:c3c19f48 r1:00000001 r0:c027c7e9
[<c003d10c>] (do_exit+0x0/0x5bc) from [<c003d7c8>] (sys_exit+0x18/0x1c)
[<c003d7b0>] (sys_exit+0x0/0x1c) from [<c0027e60>] (ret_fast_syscall+0x0/0x2c)
answered Feb 19, 2015 by marcL New to the Community (2 points)
...