|
From: | Kevin Wells |
Subject: | RE: [Ltib] Kernel panic after update the latest source for LPC32xx target |
Date: | Wed, 4 Aug 2010 19:21:58 +0200 |
Hi Henry, >Thank you for replying, one further thing to confirm
with you. >"/dev/mtdblock5 used for
JFFS2" >In the boot parameter, I just change the
"root=/dev/mtdblock3" to "root=/dev/mtdblock4" and the
target works. >Is it correct? (My concept is the numeric of MTD blocks
is starts from 0.) Yes, that should be /dev/mtdblock4. Good catch! thanks, Kevin From:
address@hidden [mailto:address@hidden On Behalf Of Li
Yuan-Lung Dear Kevin, Thank you for replying, one further thing to confirm with
you. "/dev/mtdblock5 used for JFFS2" In the boot parameter, I just change the
"root=/dev/mtdblock3" to "root=/dev/mtdblock4" and the
target works. Is it correct? (My concept is the numeric of MTD blocks is
starts from 0.) Henry 2010/8/4 Kevin Wells <address@hidden> Hi Henry, >jffs2_scan_eraseblock():
Magic bitmask 0x1985 not found at 0x00188024: 0x7366 instead >Further
such events for this erase block will not be printed >VFS:
Mounted root (jffs2 filesystem) on device 31:3. >Freeing
init memory: 116K >Failed
to execute /sbin/init. Attempting defaults... >Kernel
panic - not syncing: No init found. Try passing init= option to kernel. It seems your JFFS2 partition is
corrupted. You may need to reprogram the JFFS2 image in NAND FLASH via u-boot. Note that the partitions for some boards
were resized in the latest patches! Dump your kernel boot log and look at
the kernel MTD partition info… NAND device: Manufacturer
ID: 0x20, Chip ID: 0x36 (ST Micro NAND 64MiB 1,8V 8-bit) Scanning device for bad
blocks Bad eraseblock 45 at
0x0000000b4000 Creating 5 MTD partitions on
"lpc32xx_nand": 0x000000000000-0x000000064000
: "phy3250-boot" 0x000000064000-0x0000001f4000
: "phy3250-uboot" 0x0000001f4000-0x000000204000
: "phy3250-ubt-prms" 0x000000204000-0x000000604000
: "phy3250-kernel" 0x000000604000-0x000004000000
: "phy3250-rootfs" << /dev/mtdblock5 used for JFFS2 Is the location you wrote your JFFS2
data the same as the MTD partition offset in your boot log? uboot> nand write.jffs2 0x80100000 0x00604000 <size> NAND write: device 0 offset 0x604000, size <size> <size> bytes written: OK uboot> I hope this helps, Kevin From:
ltib-bounces+kevin.wells=nxp.com@nongnu.org [mailto:ltib-bounces+kevin.wells=nxp.com@nongnu.org] On Behalf Of Li Yuan-Lung Dear
NXP friends, After
using "ltib -m distclean" and re-build the kernel, the booting
becomes kernel panic, the build config is just the same as old one. Is there
any modification need to be change with the menuconfig? Thank you. The
panics messages:
........................................................................................ jffs2_scan_eraseblock():
Magic bitmask 0x1985 not found at 0x00188024: 0x7366 instead Further
such events for this erase block will not be printed VFS:
Mounted root (jffs2 filesystem) on device 31:3. Freeing
init memory: 116K Failed
to execute /sbin/init. Attempting defaults... Kernel
panic - not syncing: No init found. Try passing init= option to kernel.
See Linux Documentation/init.txt for guidance. Backtrace: [<c00299fc>]
(dump_backtrace+0x0/0x108) from [<c0029f58>] (dump_stack+0x18/0x1c) r6:00000000
r5:00000000 r4:c0359834 [<c0029f40>]
(dump_stack+0x0/0x1c) from [<c00440f0>] (panic+0x5c/0xf8) [<c0044094>]
(panic+0x0/0xf8) from [<c00255d8>] (init_post+0xb8/0xe8) r3:c3c05e08
r2:00000003 r1:00000002 r0:c02ed374 [<c0025520>]
(init_post+0x0/0xe8) from [<c0008998>] (kernel_init+0x120/0x160) r4:c0359838 [<c0008878>]
(kernel_init+0x0/0x160) from [<c0047598>] (do_exit+0x0/0x684) r4:00000000 Henry
|
[Prev in Thread] | Current Thread | [Next in Thread] |