Rooting around in the Longse / Cantonk S2L33M/IMX322 vari-focal camera.

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Thank you! I'm going to try.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Thank you, alastairstevenson!
I was able to do this and set up the Internet on the camera.
But I can't download mtd4, 5 and 6. At some point there is a failure.
Maybe there is not enough space in the memory of the device? If this is the case, will you have to configure the NFS server?
What say you?
The log is attached.
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
I was able to do this and set up the Internet on the camera.
But I can't download mtd4, 5 and 6. At some point there is a failure.
From the log it looks like /etc/init.d/rcS is not enough by itself to fully initialise the running environment.
Startup tasks tend to be distributed in different ways in different implementations of embedded systems.

Suggestion:
To check if all is normal, use the commands
mount
and
df -h
There should be no errors, and a list of mounts should show, and the space used on them.
If there are errors, the full startup has not yet been done.

Another place to look in in the file /etc/inittab
Check out the contents using
cat /etc/inittab
Look for lines such as below, which would be part of startup processing.
null::sysinit:/bin/mount -t tmpfs tmpfs /tmp
There may also be a line that runs /etc/init.d/rcS

If there are lines like that in inittab you will need to execute them manually.
This is easy to do if you use the PuTTY 'copy all to clipboard' item from the top left menu.
You can paste the result into Notepad or similar
Then gather together the lines to want to execute, copy them to the clipboard, and paste into PuTTY.
This saves typing them, and removes typing errors.

Once you get to a proper running system, you should be able to bring in the files you need without running out of space.

Again - I'd suggest that you do not attempt to write the bootloader and the system partitions mtdblock0, 1,2 and 3
These are working OK and if corrupted will permanently brick the camera.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Thank you!
I will try...
About system partitions I understood.
The rest is not very good yet...
PS, how hard is it to learn Linux.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
I cannot run the commands manually in the inittab file.
Where is my mistake?
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
Where is my mistake?
Oops - my mistake, sorry.
I forgot to mention that you need to trim the lines in inittab before using them manually at the command line.
So quite a bit of the startup is in inittab and not all in rcS
That explains why mount and so on do not work.
This is the relevant part of inittab:
Code:
# Startup the system
#null::sysinit:/bin/mount -o remount,rw,sync /
null::sysinit:/bin/mount -t proc proc /proc
null::sysinit:/bin/mount -t tmpfs tmpfs /tmp
null::sysinit:/bin/sh /etc/ambrwfs
null::sysinit:/bin/mount -a
null::sysinit:/bin/echo '\000\000\000\000' > /proc/sys/kernel/hotplug
null::sysinit:/bin/hostname -F /etc/hostname
null::sysinit:/sbin/ifconfig lo 127.0.0.1 up
null::sysinit:/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

# now run any rc scripts
::sysinit:/etc/init.d/rcS
null::once:/usr/local/bin/upgrade-d
Suggest using this subset to get the environment initiallised:
/bin/mount -o remount,rw,sync /
/bin/mount -t proc proc /proc
/bin/mount -t tmpfs tmpfs /tmp
/bin/sh /etc/ambrwfs
/bin/mount -a
/etc/init.d/rcS
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Hello, alastairstevenson!
I tried this and also tried the netcat and did something bad for the camera... Now I can only get Amboot and can't get to the root console.
What can you tell me in this case? Do I still have options or not?
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
I'm not sure what you did with nc. What did it attempt to transfer in?

The original idea was to see if you could boot to a shell and find if tftp was available.
It was, and could therefore be used to bring in a saved partition image from another camera, to be applied to this camera.
Something like
cat file_that_was_loaded_in > /dev/mtdblock4

It looks like mtdblock4 and mtdblock6 have been written over such that they are no longer valid UBIFS images.

On the attempt to repair via the bootloader - the NAND reclaim looks promising.
If the NAND subsystem in the bootloader does allow writing of specific partitions from images that have been loaded in using tftp, there may me a chance of re-writing with valid data.

This command -
tftp program mtd6 0x08000000

requires an additional parameter (a 0 at the end) to tell the bootloader that the data is not a program to be executed
tftp program mtd6 0x08000000 0

But I'm not sure what the NAND command would be to write the data to a specified partition.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Tftp server is available and I tried to use it to transfer files. But I failed to pass mtd4. It's large. So I tried to do it through a netcat. But when you try to copy got it.
I tried to run the tftp program mtd6 0x08000000 0, but unfortunately nothing has changed. What else to try?
 

Attachments

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
I tried to run the tftp program mtd6 0x08000000 0
That worked OK, and loaded the file into memory as it should.

The next step would be to write that data to the correct area of flash memory.
But it's not obvious if the available NAND commands can do that, or if it's the 'nand prog' command that does that, how to use the command-line parameters. It would seem logical that if there is an erase command there should also be a write/program command.

The normal steps would be a 'nand erase' to the specified offset and size to initialise the flash, then a 'nand write' from the memory that has been loaded to the same offset.
But there doesn't seem to be a nand write command.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
I can try nand prog with my hands, but I don't understand how this command works... It is not clear what the [BITFLIP] parameter is...
And I don't know what pages I need...
I am ready for any experiments, but unfortunately I do not understand much yet...
Ready to test any of your idea if you are not too busy.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
But as I can understand from the logs, into which slot do I load, for example mtd4?
Here mtd6 I load at 0x08000000. Where is this information?
Is it?
Code:
Creating 7 MTD partitions on " amba_nand":
[ 9.703578] 0x000000000000-0x000000020000 : "bst"
[ 9.709119] 0x000000020000-0x000000160000: "bld"
[ 9.714518] 0x000000160000-0x0000002a0000: "ptb"
[ 9.719926] 0x0000002a0000-0x000000aa0000: "pri"
[ 9.725297] 0x000000aa0000-0x000003ea0000: "lnx"
[ 9.730752] 0x000003ea0000-0x0000058a0000: "add"
[ 9.736163] 0x0000058a0000-0x000007ca0000: "adc"
I have not met in the logs references to 08000000.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Is there any way this can help?
Code:
The following commands are supported:
r32     w32     boot    erase
help    reboot  setenv  show
memtest fs      fdt     nand
usbdl   gpio    tftp    ping
sd
Use 'help' to get help on a specific command
amboot> usbdl help
Invalid hex address
Help for 'usbdl':
The command execute actions over USB
usbdl (Perform actions controlled by Host)
usbdl ADDRESS exec (Download image to target address and execute it)
usbdl fwprog (Download firware and program it into flash)
usbdl ext (Turn on USB external clock)
usbdl kernel (Download kernel files and execute it)
usbdl upload (Upload data to Host by host's request)
usbdl test [download | pll] (Test download or dll power-on/off)
amboot>
'' is not a recognized command! Type 'help' for help...
amboot> w32 help
Type 'help w32' for help
Help for 'w32':
w32 [address] [value]
Write a 32-bit data into an address
amboot> r32 help
invalid address!
Help for 'r32':
r32 [address]
Read a 32-bit data from an address
amboot> fdt help
Help for 'fdt':
fdt utility commands
fdt header                                - show fdt header
fdt cmdline [cmdline]                     - set cmdline
fdt getnode [path]                        - get node path
fdt getprop [path]                        - get node path and property
fdt setprop [path] [prop] [TYPE] [value]  - set property value
e.g.:
     fdt setprop [path] [prop] bool 0|1
     fdt setprop [path] [prop] hex  0x12345678
     fdt setprop [path] [prop] byte 02 11 22 0xab
     fdt setprop [path] [prop] str  string
amboot>
amboot> fs
Help for 'fs':
         fs ls
         fs info
         fs cd [dir]
         fs read [file] [addr] [exec]
         fs write [file] [addr] [size]
amboot>
I can connect the camera to my computer via USB and Ambausb can initialize the device. But unfortunately, I don't know how to use this program.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
Here mtd6 I load at 0x08000000.
That's a memory (RAM) address.
The 'lnx' partition is mtdblock4
Those addresses in the partition table are flash offsets, not memory addresses.
To use them requires an app or command that can read and write to the flash chip.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
Hello, alastairstevenson!
Thank you for helping me.
I was able with the help of your tips to recover a single "brick".
And now I'm facing another problem on another camera. I tried to flash a new firmware, but something went wrong.
The method that approached the previous camera does not work here.
The log is attached.
 

Attachments

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
And now I'm facing another problem on another camera. I tried to flash a new firmware, but something went wrong.
The method that approached the previous camera does not work here.
All, was able to solve this problem.
The problem was that when you switch to the new firmware, you first need to flash the bridge firmware, and then through The regular ipcsearch utility.exe to flash new firmware.
My version of IPCsearch.exe could not do it, but the older version could.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,952
Reaction score
6,787
Location
Scotland
I was able with the help of your tips to recover a single "brick".
Well done!
What was the final method to put the firmware back together again? Via a bootloader command?

The problem was that when you switch to the new firmware, you first need to flash the bridge firmware
Yes, I think the 'bridge' intermediate firmware includes a kernel update.
 

maks1978

Young grasshopper
Joined
Nov 15, 2018
Messages
35
Reaction score
1
Location
Moscow
The method worked the one you described:
1. boot console=ttyS0 ubi.mtd=lnx root=ubi0:rootfs rw rootfstype=ubifs init=/bin/sh
2. /etc/init.d/rcS
3. ifconfig eth0 <camera_IP_address> up
4. ping -c X <your_PC_IP_address> (where X = number of required packets (otherwise the ping cannot be interrupted))
5. cat /etc/inittab
6. /bin/mount -t proc proc /proc
/bin/mount -t tmpfs tmpfs /tmp
/bin/sh /etc/ambrwfs
/bin/mount -a
/bin/mount -o remount,rw,sync /
/etc/init.d/rcS

After that, the camera was able to boot properly and I was able to find and flash it through a web browser.

But it worked only with the camera, which can be accessed in the root console.... I have 2 cameras in which there is no download and which have a root console not available.
And there are 2 more cameras where I experimented with NAND" killed " Amboot...
Now no aktivnosti UART camera not give.
amboot>
amboot> boot console=ttyS0 ubi.mtd=lnx root=ubi0:rootfs rw rootfstype=ubifs init=/bin/sh
bst: 0x1946EC63 1.3 (2015/6/19) 0x00000000 0x00000001 (2048)
bld: 0xD383D753 1.3 (2015/6/19) 0x00000000 0x00000000 (193104)
pri: 0x73C1A954 0.1 (2015/6/19) 0x00208000 0x00000000 (4908792)
lnx: 0xEF9F71BB 0.1 (2015/6/19) 0x00000000 0x00000001 (42598400)
add: 0xE5FE18AF 0.1 (2015/6/19) 0x00000000 0x00000001 (11927552)
adc: 0xE31BE621 0.1 (2015/6/19) 0x00000000 0x00000001 (3670016)

loading pri to 0x00208000
rmd image absent... skipping
Jumping to 0x00208000 ...
cmdline: console=ttyS0 ubi.mtd=lnx root=ubi0:rootfs rw rootfstype=ubifs init=/bin/sh
cpux_jump: 0x00000000
initrd2_start: 0x00000000 initrd2_size: 0x00000000
kernelp: 0x00200000 kernels: 0x06E00000
idspp: 0x07000000 idsps: 0x09000000
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.10.73 (zucker@ubuntu) (gcc version 4.9.1 20140625 (prerelease) (crosstool-NG - Ambarella Linaro Multilib GCC [CortexA9 & ARMv6k] 2014.06) ) #2 PREEMPT Mon Jun 15 21:05:42 CST 2015
[ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Ambarella S2L (Flattened Device Tree), model: Ambarella S2LM Kiwi Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Ambarella: AHB = 0xe0000000[0xe0000000],0x01000000 0
[ 0.000000] Ambarella: APB = 0xe8000000[0xe8000000],0x01000000 0
[ 0.000000] Ambarella: PPM = 0x00000000[0xdfe00000],0x00200000 9
[ 0.000000] Ambarella: AXI = 0xf0000000[0xf0000000],0x00030000 0
[ 0.000000] Ambarella: DRAMC = 0xdffe0000[0xef000000],0x00020000 0
[ 0.000000] Ambarella: DBGBUS = 0xec000000[0xec000000],0x00200000 0
[ 0.000000] Ambarella: DBGFMEM = 0xee000000[0xee000000],0x01000000 0
[ 0.000000] Ambarella: IAVMEM = 0x07000000[ ],0x09000000
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 27940
[ 0.000000] Kernel command line: console=ttyS0 ubi.mtd=lnx root=ubi0:rootfs rw rootfstype=ubifs init=/bin/sh
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 110MB = 110MB total
[ 0.000000] Memory: 106600k/106600k available, 6040k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0x87000000 - 0xff000000 (1920 MB)
[ 0.000000] lowmem : 0x80000000 - 0x86e00000 ( 110 MB)
[ 0.000000] modules : 0x7f000000 - 0x80000000 ( 16 MB)
[ 0.000000] .text : 0x80008000 - 0x8045eadc (4443 kB)
[ 0.000000] .init : 0x8045f000 - 0x80481f0c ( 140 kB)
[ 0.000000] .data : 0x80482000 - 0x804b66f8 ( 210 kB)
[ 0.000000] .bss : 0x804b66f8 - 0x804d658c ( 128 kB)
[ 0.000000] NR_IRQS:240
[ 0.000000] sched_clock: 32 bits at 36MHz, resolution 27ns, wraps every 119304ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [ttyS0] enabled
[ 0.232587] Calibrating delay loop... 597.60 BogoMIPS (lpj=2988032)
[ 0.292606] pid_max: default: 32768 minimum: 301
[ 0.297297] Mount-cache hash table entries: 512
[ 0.304193] CPU: Testing write buffer coherency: ok
[ 0.309342] Setting up static identity map for 0x80342998 - 0x803429f8
[ 0.318134] devtmpfs: initialized
[ 0.322673] pinctrl core: initialized pinctrl subsystem
[ 0.328116] NET: Registered protocol family 16
[ 0.333332] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.340712] L310 cache controller enabled
[ 0.344712] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32020000, Cache size: 131072 B
[ 0.354285] ambarella-pinctrl e8009000.pinctrl: Ambarella pinctrl driver registered
[ 0.362294] ambarella-gpio gpio.0: Ambarella GPIO driver registered
[ 0.372230] bio: create slab <bio-0> at 0
[ 0.377279] ambarella-dma e0005000.dma: Ambarella DMA Engine
[ 0.384391] ambarella-i2c e8003000.i2c: Ambarella I2C adapter[0] probed!
[ 9.389989] ambarella-i2c e8007000.i2c: No ACK from address 0xe8, 2:0!
[ 9.396504] pca953x 2-0074: failed reading register
[ 9.401392] pca953x: probe of 2-0074 failed with error -16
[ 9.406868] ambarella-i2c e8007000.i2c: Ambarella I2C adapter[2] probed!
[ 9.414253] Switching to clocksource ambarella-cs-timer
[ 9.426008] ambarella-sd e0002000.sdmmc0: Slot0 use bounce buffer[0x86720000<->0x06920000]
[ 9.434300] ambarella-sd e0002000.sdmmc0: Slot0 req_size=0x00020000, segs=32, seg_size=0x00020000
[ 9.443170] ambarella-sd e0002000.sdmmc0: Slot0 use ADMA
[ 9.519585] ambarella-sd e0002000.sdmmc0: 1 slots @ 50000000Hz
[ 9.525587] NET: Registered protocol family 2
[ 9.533905] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[ 9.541005] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 9.547378] TCP: Hash tables configured (established 1024 bind 1024)
[ 9.553810] TCP: reno registered
[ 9.557062] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 9.562931] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 9.569358] NET: Registered protocol family 1
[ 9.574028] RPC: Registered named UNIX socket transport module.
[ 9.580018] RPC: Registered udp transport module.
[ 9.584727] RPC: Registered tcp transport module.
[ 9.589408] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 9.596216] ambarella-adc e801d000.adc: Ambarella ADC driver init
[ 9.604912] msgmni has been set to 208
[ 9.610015] NET: Registered protocol family 38
[ 9.614529] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 9.622053] io scheduler noop registered
[ 9.625960] io scheduler deadline registered
[ 9.630259] io scheduler cfq registered (default)
[ 9.635948] e8005000.uart: ttyS0 at MMIO 0xe8005000 (irq = 9) is a ambuart
[ 9.643703] brd: module loaded
[ 9.649282] loop: module loaded
[ 9.655021] ambarella-nand e0001000.nand: in ecc-[1]bit mode
[ 9.660751] ambarella_nand: Use On Flash BBT
[ 9.665081] NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD/Spansion NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64
[ 9.677739] Bad block table found at page 65472, version 0x29
[ 9.683700] Bad block table found at page 65408, version 0x29
[ 9.689717] 7 ofpart partitions found on MTD device amba_nand
[ 9.696472] Creating 7 MTD partitions on "amba_nand":
[ 9.703563] 0x000000000000-0x000000020000 : "bst"
[ 9.709102] 0x000000020000-0x000000160000 : "bld"
[ 9.714498] 0x000000160000-0x0000002a0000 : "ptb"
[ 9.719910] 0x0000002a0000-0x000000aa0000 : "pri"
[ 9.725281] 0x000000aa0000-0x000003ea0000 : "lnx"
[ 9.730733] 0x000003ea0000-0x0000058a0000 : "add"
[ 9.736144] 0x0000058a0000-0x000007ca0000 : "adc"
[ 9.742805] ambarella-spi e0020000.spi: cs1 >= max 1
[ 9.747763] spi_master spi0: spi_device register error /ahb@e0000000/spi@e0020000/spidev@1
[ 9.756274] ambarella-spi e0020000.spi: Ambarella spi controller 0 created.
[ 9.819523] libphy: Ambarella MII Bus: probed
[ 9.824366] ambarella-eth e000e000.ethernet: Ethernet PHY[0]: 0x001cc816!
[ 9.831641] ambarella-eth e000e000.ethernet: MAC Address[00:00:1b:01:3e:7e].
[ 9.838931] mousedev: PS/2 mouse device common for all mice
[ 9.844883] ambarella-rtc e8015000.rtc: rtc core: registered rtc-ambarella as rtc0
[ 9.852658] i2c /dev entries driver
[ 9.859864] ambarella-wdt e800c000.wdt: Ambarella Watchdog Timer Probed.
[ 9.866913] TCP: cubic registered
[ 9.870284] Initializing XFRM netlink socket
[ 9.874585] NET: Registered protocol family 17
[ 9.879110] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 9.886820] ThumbEE CPU extension supported.
[ 9.892290] UBI: attaching mtd4 to ubi0
[ 10.041855] UBI: scanning is finished
[ 10.051204] UBI: attached mtd4 (name "lnx", size 52 MiB) to ubi0
[ 10.057196] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 10.064011] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 10.070707] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 10.077558] UBI: good PEBs: 416, bad PEBs: 0, corrupted PEBs: 0
[ 10.083469] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 10.090592] UBI: max/mean erase counter: 13/1, WL threshold: 4096, image sequence number: 998301244
[ 10.099619] UBI: available PEBs: 0, total reserved PEBs: 416, PEBs reserved for bad PEB handling: 20
[ 10.108730] UBI: background thread "ubi_bgt0d" started, PID 47
[ 10.114593] ambarella-rtc e8015000.rtc: setting system clock to 2106-02-07 06:28:15 UTC (4294967295)
[ 10.124890] UBIFS: background thread "ubifs_bgt0_0" started, PID 48
[ 10.153203] UBIFS: recovery needed
[ 10.898071] UBIFS assert failed in ubifs_change_lp at 559 (pid 1)
[ 10.904202] CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.73 #2
[ 10.910074] [<800133ac>] (unwind_backtrace+0x0/0x12c) from [<80011a14>] (show_stack+0x10/0x14)
[ 10.918683] [<80011a14>] (show_stack+0x10/0x14) from [<801838a4>] (ubifs_change_lp+0x714/0x760)
[ 10.927386] [<801838a4>] (ubifs_change_lp+0x714/0x760) from [<80171b90>] (ubifs_replay_journal+0xadc/0x10d4)
[ 10.937211] [<80171b90>] (ubifs_replay_journal+0xadc/0x10d4) from [<80162a44>] (mount_ubifs+0xb68/0x1800)
[ 10.946770] [<80162a44>] (mount_ubifs+0xb68/0x1800) from [<8016431c>] (ubifs_mount+0x3b0/0x6e4)
[ 10.955467] [<8016431c>] (ubifs_mount+0x3b0/0x6e4) from [<800a4a80>] (mount_fs+0x14/0xcc)
[ 10.963647] [<800a4a80>] (mount_fs+0x14/0xcc) from [<800bd40c>] (vfs_kern_mount+0x4c/0xcc)
[ 10.971911] [<800bd40c>] (vfs_kern_mount+0x4c/0xcc) from [<800bf6c0>] (do_mount+0x1bc/0x90c)
[ 10.980347] [<800bf6c0>] (do_mount+0x1bc/0x90c) from [<800bfe94>] (SyS_mount+0x84/0xb8)
[ 10.988339] [<800bfe94>] (SyS_mount+0x84/0xb8) from [<8045ff00>] (mount_block_root+0x140/0x278)
[ 10.997041] [<8045ff00>] (mount_block_root+0x140/0x278) from [<80460304>] (prepare_namespace+0xa8/0x1d4)
[ 11.006516] [<80460304>] (prepare_namespace+0xa8/0x1d4) from [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0)
[ 11.016345] [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0) from [<8033d67c>] (kernel_init+0xc/0x154)
[ 11.025567] [<8033d67c>] (kernel_init+0xc/0x154) from [<8000ed58>] (ret_from_fork+0x14/0x3c)
[ 11.035383] UBIFS error (pid 1): ubifs_read_node: bad node type (12 but expected 0)
[ 11.043055] UBIFS error (pid 1): ubifs_read_node: bad node at LEB 324:88064, LEB mapping status 1
[ 11.051915] Not a node, first 24 bytes:
[ 11.055564] 00000000: 0b a1 b1 50 01 01 c1 18 b2 93 27 cc 0c 01 c2 18 fa 93 27 ce 0c c3 18 ec ...P......'.......'.....
[ 11.068585] CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.73 #2
[ 11.074442] [<800133ac>] (unwind_backtrace+0x0/0x12c) from [<80011a14>] (show_stack+0x10/0x14)
[ 11.083061] [<80011a14>] (show_stack+0x10/0x14) from [<80168968>] (ubifs_read_node+0x29c/0x304)
[ 11.091761] [<80168968>] (ubifs_read_node+0x29c/0x304) from [<8018b17c>] (ubifs_tnc_read_node+0x58/0x1fc)
[ 11.101321] [<8018b17c>] (ubifs_tnc_read_node+0x58/0x1fc) from [<8016c7c8>] (ubifs_tnc_locate+0x1e0/0x1e8)
[ 11.111100] [<8016c7c8>] (ubifs_tnc_locate+0x1e0/0x1e8) from [<8018639c>] (ubifs_recover_size+0x15c/0x4c4)
[ 11.120764] [<8018639c>] (ubifs_recover_size+0x15c/0x4c4) from [<801635e8>] (mount_ubifs+0x170c/0x1800)
[ 11.130152] [<801635e8>] (mount_ubifs+0x170c/0x1800) from [<8016431c>] (ubifs_mount+0x3b0/0x6e4)
[ 11.138922] [<8016431c>] (ubifs_mount+0x3b0/0x6e4) from [<800a4a80>] (mount_fs+0x14/0xcc)
[ 11.147102] [<800a4a80>] (mount_fs+0x14/0xcc) from [<800bd40c>] (vfs_kern_mount+0x4c/0xcc)
[ 11.155367] [<800bd40c>] (vfs_kern_mount+0x4c/0xcc) from [<800bf6c0>] (do_mount+0x1bc/0x90c)
[ 11.163802] [<800bf6c0>] (do_mount+0x1bc/0x90c) from [<800bfe94>] (SyS_mount+0x84/0xb8)
[ 11.171809] [<800bfe94>] (SyS_mount+0x84/0xb8) from [<8045ff00>] (mount_block_root+0x140/0x278)
[ 11.180503] [<8045ff00>] (mount_block_root+0x140/0x278) from [<80460304>] (prepare_namespace+0xa8/0x1d4)
[ 11.189976] [<80460304>] (prepare_namespace+0xa8/0x1d4) from [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0)
[ 11.199803] [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0) from [<8033d67c>] (kernel_init+0xc/0x154)
[ 11.209009] [<8033d67c>] (kernel_init+0xc/0x154) from [<8000ed58>] (ret_from_fork+0x14/0x3c)
[ 11.218109] UBIFS: background thread "ubifs_bgt0_0" stops
[ 11.223790] List of all partitions:
[ 11.227284] 1f00 128 mtdblock0 (driver?)
[ 11.232424] 1f01 1280 mtdblock1 (driver?)
[ 11.237455] 1f02 1280 mtdblock2 (driver?)
[ 11.242522] 1f03 8192 mtdblock3 (driver?)
[ 11.247552] 1f04 53248 mtdblock4 (driver?)
[ 11.252601] 1f05 26624 mtdblock5 (driver?)
[ 11.257629] 1f06 36864 mtdblock6 (driver?)
[ 11.262665] No filesystem could mount root, tried: ubifs
[ 11.268044] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 11.276285] CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.73 #2
[ 11.282130] [<800133ac>] (unwind_backtrace+0x0/0x12c) from [<80011a14>] (show_stack+0x10/0x14)
[ 11.290728] [<80011a14>] (show_stack+0x10/0x14) from [<8033e628>] (panic+0xa4/0x1e0)
[ 11.298460] [<8033e628>] (panic+0xa4/0x1e0) from [<80460010>] (mount_block_root+0x250/0x278)
[ 11.306878] [<80460010>] (mount_block_root+0x250/0x278) from [<80460304>] (prepare_namespace+0xa8/0x1d4)
[ 11.316336] [<80460304>] (prepare_namespace+0xa8/0x1d4) from [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0)
[ 11.326147] [<8045fc1c>] (kernel_init_freeable+0x1b0/0x1c0) from [<8033d67c>] (kernel_init+0xc/0x154)
[ 11.335348] [<8033d67c>] (kernel_init+0xc/0x154) from [<8000ed58>] (ret_from_fork+0x14/0x3c)
 
Top