Bugzilla – Bug 12735
Kernel oopsie when programming MSP.
Last modified: 2012-02-27 17:18:58 UTC
I had another kernel oops when programming the MSP, with yesterday's kernel build (home made). This was on a board that had an incorrect component installed, and *may* have damaged either the MX25 or MSP pin. However after rebooting, it programmed properly. What do you think? -Caleb mxc_wdt: Unexpected close, not stopping! eth0: status: link down. eth0: status: link up, 10MBit Full Duplex, auto-negotiation complete. eth0: enable RMII gasket MXC Watchdog # 0 shutdown Restarting system. ++NAND: RCSR=54200900 Searching for BBT table in the flash ... . Found version 1 Bbt0 at block 1023 (0x7fe0000) Block 604 is bad Block 910 is bad Total bad blocks: 2 .FEC PHY: RTL8201EL FEC: [ HALF_DUPLEX ] [ disconnected ] [ 10M bps ]: Ethernet mxc_fec: MAC address 00:04:20:08:06:1d No IP info for device! Unrecognized chip: 0xf8!!! hardware reset by POR Clock input is 24 MHz RedBoot(tm) bootstrap and debug environment [ROMRAM] Non-certified release, version FSL 200904 - built 13:28:50, Jun 30 2009 Platform: Logitech Baby (i.MX25 ) PASS 1.0 [x32 DDR] System type 2070 revision 3 Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited RAM: 0x00000000-0x03f00000, [0x00095250-0x03ef1000] available FLASH: 0x00000000 - 0x8000000, 1024 blocks of 0x00020000 bytes each. RedBoot> ip_address -b ... waiting for BOOTP information IP: 172.19.115.46/255.255.254.0, Gateway: 172.19.114.1 Default server: 172.19.113.11 RedBoot> load -v -r -b 0x100000 -h 172.19.115.140 zImage-baby.bin Using default protocol (TFTP) | Raw file loaded 0x00100000-0x0028a2ff, assumed entry at 0x00100000 RedBoot> exec -c "noinitrd console=ttymxc1,115200 jtag=on ubi.mtd=1 root=/dev/mtdblock:cramfs init=/linuxrc" entry=0x80008000, target=0x80008000 Using base address 0x00100000 and length 0x0018a300 Uncompressing Linux......................................................................................................... done, booting . Linux version 2.6.26.8-rt16 (slim@slim-desktop) (gcc version 4.2.3) #18 PREEMPT RT Wed Jul 8 06:54:29 CST 2009 CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177 Machine: Logitech MX25 Baby Board Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Real-Time Preemption Support (C) 2004-2007 Ingo Molnar Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: noinitrd console=ttymxc1,115200 jtag=on ubi.mtd=1 root=/dev/mtdblock:cramfs init=/linuxrc Preemptible RCU implementation. MXC IRQ initialized PID hash table entries: 256 (order: 8, 1024 bytes) MXC GPT timer initialized, rate = 12000000 WARNING: Clock divider has been truncated, clock error 333 [ps] per 83 [ns] Console: colour dummy device 80x30 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: 61532KB available (2980K code, 277K data, 136K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 276 bytes NET: Registered protocol family 16 AIPS1 VA base: 0xfc000000 CPU is i.MX0 Revision 0.3 Clock input source is 24000000 MXC GPIO hardware Using SDMA I.API MXC DMA API initialized MXC I2C driver MXC I2C driver ASoC version 0.20 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: 3, 57344 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered NET: Registered protocol family 1 Bus freq driver module loaded krcupreemptd setsched 0 prio = 98 Registering unionfs 2.5.1 (for 2.6.26.8) msgmni has been set to 120 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) MXC Backlight Device mxc_lcdc_bl.0 Initialized. Console: switching to colour frame buffer device 30x40 mxc_sdc_fb mxc_sdc_fb.0: fb0: DISP0 BG fb device registered successfully. mxc_sdc_fb mxc_sdc_fb.0: fb1: DISP0 FG fb device registered successfully. Serial: MXC Internal UART driver mxcintuart.1: ttymxc1 at MMIO 0x43f94000 (irq = 32) is a Freescale MXC console [ttymxc1] enabled brd: module loaded loop: module loaded FEC ENET Version 0.2 fec: PHY @ 0x1, ID 0x001cc815 -- RTL8201E eth0: ethernet 00:04:20:08:06:1d MXC MTD nand Driver 2.5 NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) UBI: attached mtd1 to ubi0 UBI: MTD device name: "ubi" UBI: MTD device size: 126 MiB UBI: number of good PEBs: 1012 UBI: number of bad PEBs: 2 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 3 UBI: available PEBs: 655 UBI: total number of reserved PEBs: 357 UBI: number of PEBs reserved for bad PEB handling: 10 UBI: max/mean erase counter: 2/1 UBI: background thread "ubi_bgt0d" started, PID 275 mice: PS/2 mouse device common for all mice MXC keypad loaded input: mxckpd as /class/input/input0 eth0: status: link up, 100MBit Full Duplex, auto-negotiation complete. eth0: enable RMII gasket MXC WatchDog Driver 2.0 MXC Watchdog # 0 Timer: initial timeout 60 sec input: Unspecified device as /class/input/input1 input: msp430 as /class/input/input2 firmware: requesting msp430.txt i.MX ADC at 0x50030000 irq 46 mxsdhci: MXC Secure Digital Host Controller Interface driver mxsdhci: MXC SDHCI Controller Driver. mmc0: SDHCI detect irq 0 irq 9 PIO Advanced Linux Sound Architecture Driver Version 1.0.16. AIC3104 Audio Codec 0.1<6>DMA Sound Buffers Allocated:UseIram=1 buf->addr=78000000 buf->area=c4860000 size=65536 DMA Sound Buffers Allocated:UseIram=1 buf->addr=83d80000 buf->area=fde97000 size=65536 asoc: aic3104-dai <-> imx-ssi-1 mapping ok AIC3104 WRITE 0: 00000000 AIC3104 WRITE 1: 00000080 AIC3104 WRITE 43: 00000080 AIC3104 WRITE 44: 00000080 AIC3104 WRITE 47: 00000080 AIC3104 WRITE 64: 00000080 AIC3104 WRITE 54: 00000080 AIC3104 WRITE 71: 00000080 AIC3104 WRITE 82: 00000080 AIC3104 WRITE 92: 00000080 AIC3104 WRITE 86: 00000008 AIC3104 WRITE 93: 00000008 AIC3104 WRITE 25: 00000080 AIC3104 WRITE 38: 00000020 AIC3104 WRITE 40: 00000080 AIC3104 WRITE 51: 0000000d AIC3104 WRITE 65: 00000009 AIC3104 WRITE 14: 00000080 AIC3104 WRITE 13: 00000080 AIC3104 WRITE 15: 00000028 AIC3104 WRITE 16: 00000028 AIC3104 WRITE 17: 000000ff AIC3104 WRITE 18: 000000ff AIC3104 WRITE 19: 00000004 AIC3104 WRITE 22: 00000004 ###### sound/soc/codecs/tlv320aic3104.c:1130 aic3104_dapm_event AIC3104 WRITE 65: 00000008 AIC3104 WRITE 51: 0000000c ALSA device list: #0: baby (aic3104) oprofile: using timer interrupt. TCP cubic registered NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com> VFS: Mounted root (cramfs filesystem) readonly. Freeing init memory: 136K mmc0: new SDIO card at address 0001 UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 0, volume 2, name "ubifs" UBIFS: file system size: 9418752 bytes (9198 KiB, 8 MiB, 73 LEBs) UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 6 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: default compressor: lzo UBIFS: reserved for root: 444870 bytes (434 KiB) Filesystem overlay: unionfs mount: mounting /dev on /mnt/overlay/dev failed: Invalid argument init started: BusyBox v1.13.3 (2009-06-23 10:54:01 PDT) starting pid 357, tty '': '/etc/init.d/rcS' Starting udev Mounting RAM Disk Starting syslogd Unable to handle kernel NULL pointer dereference at virtual address 00000000 pgd = c0004000 [00000000] *pgd=00000000 Internal error: Oops: 17 [#1] PREEMPT Modules linked in: CPU: 0 Not tainted (2.6.26.8-rt16 #18) PC is at msp430_programmer_firmware+0x18/0x350 LR is at request_firmware_work_func+0x58/0x90 pc : [<c01adbfc>] lr : [<c01825f4>] psr: a0000013 sp : c3dd5f78 ip : c3dd5fb8 fp : c3dd5fb4 r10: 00000000 r9 : 00000000 r8 : c3c67600 r7 : 00000000 r6 : c018259c r5 : fffffffe r4 : 00000000 r3 : c01adbe4 r2 : 00000000 r1 : c3c67600 r0 : 00000000 Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 0005317f Table: 8288c000 DAC: 00000017 Process firmware/msp430 (pid: 295, stack limit = 0xc3dd4268) Stack: (0xc3dd5f78 to 0xc3dd6000) 5f60: c3dd5fb4 c3dd5f88 5f80: c0182538 c017d108 00000000 c3e3a7a0 fffffffe c018259c 00000000 00000000 5fa0: 00000000 00000000 c3dd5fd4 c3dd5fb8 c01825f4 c01adbf4 c026544c 00000000 5fc0: c3dd4000 c3e3a7a0 c3dd5ff4 c3dd5fd8 c0057f08 c01825ac 00000000 00000000 5fe0: 00000000 00000000 00000000 c3dd5ff8 c0046280 c0057ebc ffffffff ffffffff Backtrace: [<c01adbe4>] (msp430_programmer_firmware+0x0/0x350) from [<c01825f4>] (request_firmware_work_func+0x58/0x90) [<c018259c>] (request_firmware_work_func+0x0/0x90) from [<c0057f08>] (kthread+0x5c/0x94) r5:c3e3a7a0 r4:c3dd4000 [<c0057eac>] (kthread+0x0/0x94) from [<c0046280>] (do_exit+0x0/0x64c) r6:00000000 r5:00000000 r4:00000000 Code: e24cb004 e24dd014 e1a08001 e1a04000 (e5900000) ---[ end trace dcddd54eb1a1194b ]---
Richard: Is this for MPQ or MP?
David is writing a script to clear the msp430 and reboot the system, logging as it goes. This should let us see if this is really a problem.
This may have been caused if the msp430.txt file was missing from the filesystem. I've fixed that bug today. Caleb, could you have deleted that file while testing?
Richards change 6523
(In reply to comment #3) > This may have been caused if the msp430.txt file was missing from the > filesystem. I've fixed that bug today. Caleb, could you have deleted that file > while testing? It's totally possible. Or more likely, I power cycled while the filesystem was in an unknown state. I think sometimes the file will get left at 0 size. I saw this error a bunch last night when I didn't get the builds right. So.... I'm comfortable with you marking the bug fixed.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.