kernel panic on MPC8323 custom board
Hi.. all I'm porting the linux 2.6.27 kernel to the custom board with Freescale8270. The base is the pq2fads board. The board is noproblem with linux-2.6.17.1 and linux-2.6.25. When booting this machine, a crash takes place such as : - Using FCC1 ETHERNET device TFTP from server 192.168.0.12; our IP address is 192.168.0.161 Filename 'cuImage.pq2fads'. Load address: 0x10 Loading: # done Bytes transferred = 822097 (c8b51 hex) [codec]$ bootm 10 ## Booting kernel from Legacy Image at 0010 ... Image Name: Linux-2.6.27 Created: 2010-08-05 1:35:22 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:822033 Bytes = 802.8 kB Load Address: 0040 Entry Point: 00400ba0 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Booting using board info... Memory - 0x0 0x1000 (256MB) CPU clock-frequency - 0x1ad27480 (450MHz) CPU timebase-frequency - 0x17d7840 (25MHz) CPU bus-frequency - 0x5f5e100 (100MHz) zImage starting: loaded at 0x0040 (sp: 0x0ff65ac8) Allocating 0x1e4924 bytes for kernel ... gunzipping (0x - 0x0040d000:0x005da9f0)...done 0x1b3224 bytes Linux/PowerPC load: root=/dev/nfs rw nfsroot=192.168.0.12:/project/target/target_nadatel ip=192.168.0.161:192.168.0.12:192.168.0.1::h264codec:eth0:off Finalizing device tree... flat tree at 0x40c038 id mach(): done MMU:enter MMU:hw init MMU:mapin MMU:setio MMU:exit [0.00] Using Freescale PQ2FADS machine description [0.00] Linux version 2.6.27 (v...@alinux) (gcc version 3.3.1 (MontaVista 3.3.1-3.0.10.0300532 2003-12-24)) #55 Thu Aug 5 10:35:18 KST 2010 [0.00] console [udbg0] enabled setup_arch: bootmem pq2fads_setup_arch() pq2fads_setup_arch(), finish arch: exit [0.00] Top of RAM: 0x1000, Total RAM: 0x1000 [0.00] Memory hole size: 0MB [0.00] Zone PFN ranges: [0.00] DMA 0x - 0x0001 [0.00] Normal 0x0001 - 0x0001 [0.00] HighMem 0x0001 - 0x0001 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0: 0x - 0x0001 [0.00] On node 0 totalpages: 65536 [0.00] free_area_init_node: node 0, pgdat c01adb3c, node_mem_map c01e7000 [0.00] DMA zone: 65024 pages, LIFO batch:15 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [0.00] Kernel command line: root=/dev/nfs rw nfsroot=192.168.0.12:/project/target/target_nadatel ip=192.168.0.161:192.168.0.12:192.168.0.1::h264codec:eth0:off [0.00] PID hash table entries: 1024 (order: 10, 4096 bytes) [0.00] time_init: decrementer frequency = 25.00 MHz [0.00] time_init: processor frequency = 450.00 MHz [0.00] clocksource: timebase mult[a00] shift[22] registered [0.038127] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.060153] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.134314] High memory: 0k [0.141880] Memory: 257792k/262144k available (1648k kernel code, 4204k reserved, 76k data, 194k bss, 124k init) [0.172857] Calibrating delay loop... 49.79 BogoMIPS (lpj=24896) [0.207709] Mount-cache hash table entries: 512 [0.234059] Unable to handle kernel paging request for data at address 0x0032 [0.255641] Faulting instruction address: 0xc0183c50 [0.270489] Oops: Kernel access of bad area, sig: 11 [#1] [0.286545] Freescale PQ2FADS [0.295392] Modules linked in: [0.304504] NIP: c0183c50 LR: c0183ef4 CTR: [0.319345] REGS: cf821db0 TRAP: 0300 Not tainted (2.6.27) [0.336514] MSR: 9032 EE,ME,IR,DR CR: 82004024 XER: [0.355515] DAR: 0032, DSISR: 2000 [0.367750] TASK = cf81f8a0[1] 'swapper' THREAD: cf82 [0.383362] GPR00: c0183ef4 cf821e60 cf81f8a0 c015e5e0 cf821ec0 0024 013f [0.408348] GPR08: 3860ffda c01a 0002 8124000c 24004024 0fffe000 11fc6000 [0.44] GPR16: fffb fcfd feff 0fff8c94 0002 0ff65e80 [0.458319] GPR24: c01b cf821ec0 c01b c01b cf821eb8 [0.483863] NIP [c0183c50] find_section32+0x14/0xb8 [0.498409] LR [c0183ef4] vdso_do_find_sections+0x28/0xc8 [0.514537] Call Trace: [0.521839] [cf821e60] [c00f5ce8] kobject_uevent_env+0x2f4/0x318 (unreliable) [0.543176] [cf821e90] [c0183ef4] vdso_do_find_sections+0x28/0xc8 [0.561394] [cf821eb0] [c01841b4] vdso_setup+0x2c/0xb8 [0.576749] [cf821f10] [c0184308] vdso_init+0x64/0x1dc [0.592113] [cf821f30] [c0003904] do_one_initcall+0x54/0x184 [0.609022] [cf821fb0] [c017d848] do_initcalls+0x34/0x58 [0.624897] [cf821fd0] [c017d92c] kernel_init+0x40/0x94 [0.640528] [cf821ff0]
Re: kernel panic on MPC8323 custom board
protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 4, 65536 bytes) TCP bind hash table entries: 1024 (order: 2, 28672 bytes) TCP: Hash tables configured (established 2048 bind 1024) TCP reno registered NTFS driver 2.1.28 [Flags: R/O]. JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. fuse init (API version 7.8) JFS: nTxBlock = 478, nTxLock = 3829 io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered Generic RTC Driver v1.07 WDT driver for MPC83xx initialized. mode:reset timeout=65535 (32 seconds) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xe0004500 (irq = 16) is a 16550A serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 17) is a 16550A RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize loop: loaded (max 8 devices) ucc_tdm: Freescale QE UCC TDM Driver config_tdm Delay for Legerity! tdm_start 16-bit linear pcm mode active with slots 0 2 tdm_start UCC based TDM enabled ucc_tdm_probe UCC based tdm module installed UCC Ethernet Controller MII Bus: probed ucc_geth: QE UCC Gigabit Ethernet Controller ucc_geth: UCC2 at 0xe0103000 (irq = 20) eth0: MTU=1500 (frame size=1518,rx_buffer_size=1536,truesize=1792,sk_buff=160) ucc_geth: UCC3 at 0xe0102200 (irq = 34) eth1: MTU=1500 (frame size=1518,rx_buffer_size=1536,truesize=1792,sk_buff=160) SKB Handler initialized(max=64) ICPlus IP175C: Registered new driver block2mtd: version $Revision: 1.30 $ e01004c0.spi: MPC83xx SPI Controller driver at 0xc50aa4c0 (irq = 21) usbmon: debugfs is not available Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. i2c /dev entries driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 No filesystem could mount root, tried: 6Time: timebase clocksource has been installed. jffs2 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Call Trace: [C03B5E70] [C000819C] (unreliable) [C03B5EB0] [C0026AB0] [C03B5F00] [C02A4B98] [C03B5F50] [C02A4DEC] [C03B5F70] [C0003B04] [C03B5FF0] [C00102BC] 0Rebooting in 180 seconds.. Do I miss to turn on something or kernel version do not support device tree? Has u-boot 1.3.2 mtdparts command? When I try to use it an 'unknown command' occur. Thanks Dario -- View this message in context: http://old.nabble.com/kernel-panic-on-MPC8323-custom-board-tp27059752p27128312.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel panic on MPC8323 custom board
Handler initialized(max=64) ICPlus IP175C: Registered new driver flash: Found 1 x16 devices at 0x0 in 16-bit bank Amd/Fujitsu Extended Query Table at 0x0040 flash: 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. RedBoot partition parsing not available physmap-flash flash: Using OF partition information Creating 4 MTD partitions on flash: 0x-0x0008 : U-Boot 0x0008-0x0010 : dtb 0x0010-0x0030 : Kernel 0x0030-0x0100 : rootfs block2mtd: version $Revision: 1.30 $ e01004c0.spi: MPC83xx SPI Controller driver at 0xc50aa4c0 (irq = 21) usbmon: debugfs is not available Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. i2c /dev entries driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 No filesystem could mount root, tried: 6Time: timebase clocksource has been installed. jffs2 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Call Trace: [C03BBE70] [C000819C] (unreliable) [C03BBEB0] [C0026AB0] [C03BBF00] [C02AAB98] [C03BBF50] [C02AADEC] [C03BBF70] [C0003B04] [C03BBFF0] [C00102BC] 0Rebooting in 180 seconds.. But still unable to mount root...any suggestion? Thanks Dario -- View this message in context: http://old.nabble.com/kernel-panic-on-MPC8323-custom-board-tp27059752p27130293.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel panic on MPC8323 custom board
Scott Wood-2 wrote:
Dario Presti wrote:
Hello,
I'm working on MPC8323_rdb board whit 1 new flash device S29GL512P
instead
of original flash devices.
the bootloader is u-boot 1.1.6 (I know is too old and I'm going to
upgrade
it) and the kernel is 2.6.20.
2.6.20 is also too old. :-)
I did this modification to the bootloader to support new flash:
1)I modified the board/mpc8323rdb/config.mk file to set TEXT_BASE from
0xFE00 TO 0xFC00
2)I modified the file /include/configs/MPC8323RDB.h:
#define CFG_FLASH_BASE 0xFC00 /* FLASH base address
*/
#define CFG_FLASH_SIZE 64 /* FLASH size is 64M */
#define CFG_LBLAWBAR0_PRELIM CFG_FLASH_BASE /* Window base at flash base
*/
#define CFG_LBLAWAR0_PRELIM 0x8019 /* 64MB window size */
#define CFG_OR0_PRELIM 0xfc006ff7 /* 64MB Flash size */
#define CFG_MAX_FLASH_BANKS 1 /* number of banks */
#define CFG_MAX_FLASH_SECT 512 /* sectors per device */
3)I modify and recompiled .dts file
fl...@fc00 {
device_type = jedec-flash;
compatible = direct-mapped;
probe-type = CFI;
reg = 0xfc00 0x100;
bank-width = 0x2;
partitions = 0x0 0x80001 0x8 0x2 0xa 0x18
0x22
0xde;
partition-names = U-Boot, dtb, Kernel, rootfs;
};
but the kernel find the flash at 0xFE00 and the boot stop because
kernel
panic. The log is:
Is the kernel even using that node, or some other means to determine the
flash location? The MPC8323RDB Flash Bank 1 messages make me think
you've got a custom flash map driver.
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Thanks Scott,
I did not find where the custom map flash driver is in the kernel source,
where it is?
How can I say to the kernel to use device tree instead of custom map of
flash?
Regards
Dario
--
View this message in context:
http://old.nabble.com/kernel-panic-on-MPC8323-custom-board-tp27059752p27073289.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel panic on MPC8323 custom board
Dario Presti wrote: Thanks Scott, I did not find where the custom map flash driver is in the kernel source, where it is? Grep your kernel tree for MPC8323RDB Flash. How can I say to the kernel to use device tree instead of custom map of flash? Turn off that mapping driver, and turn on CONFIG_MTD_PHYSMAP_OF. This stuff was very new in 2.6.20, though, so there may be issues. I'd upgrade if you can. -Scott ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel panic on MPC8323 custom board
Dario Presti wrote:
Hello,
I'm working on MPC8323_rdb board whit 1 new flash device S29GL512P instead
of original flash devices.
the bootloader is u-boot 1.1.6 (I know is too old and I'm going to upgrade
it) and the kernel is 2.6.20.
2.6.20 is also too old. :-)
I did this modification to the bootloader to support new flash:
1)I modified the board/mpc8323rdb/config.mk file to set TEXT_BASE from
0xFE00 TO 0xFC00
2)I modified the file /include/configs/MPC8323RDB.h:
#define CFG_FLASH_BASE 0xFC00 /* FLASH base address */
#define CFG_FLASH_SIZE 64 /* FLASH size is 64M */
#define CFG_LBLAWBAR0_PRELIM CFG_FLASH_BASE /* Window base at flash base */
#define CFG_LBLAWAR0_PRELIM 0x8019 /* 64MB window size */
#define CFG_OR0_PRELIM 0xfc006ff7 /* 64MB Flash size */
#define CFG_MAX_FLASH_BANKS 1 /* number of banks */
#define CFG_MAX_FLASH_SECT 512 /* sectors per device */
3)I modify and recompiled .dts file
fl...@fc00 {
device_type = jedec-flash;
compatible = direct-mapped;
probe-type = CFI;
reg = 0xfc00 0x100;
bank-width = 0x2;
partitions = 0x0 0x80001 0x8 0x2 0xa 0x18
0x22
0xde;
partition-names = U-Boot, dtb, Kernel, rootfs;
};
but the kernel find the flash at 0xFE00 and the boot stop because kernel
panic. The log is:
Is the kernel even using that node, or some other means to determine the
flash location? The MPC8323RDB Flash Bank 1 messages make me think
you've got a custom flash map driver.
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
