Possible dead board?

Hardware related problems and workarounds

Possible dead board?

Postby macarphoto » Mon Oct 24, 2016 4:04 am

Hello, I am new to the parallella. I actually bought it almost a year ago through a seller on Amazon, but finally plugged it in a couple of weeks ago. Needless to say, it doesn't seem to boot and I was wondering if anyone could help me. I am sure the the return period is long past, so hopefully you can help me fix it, or it will become a doorstop. I did recently buy a Raspberry Pi, which I got completely running Wifi test code in a couple of hours. I was hoping it would be the same for this one.

Anyway, I have the P1601 Parallella-16 Desktop Computer. I have followed the quick start guide here: https://www.parallella.org/quick-start/

I have tried the following builds with a 32-GByte micro SD card, which I formatted each time using SD Formatter, then imaging the disk using Win32 DiskImager (just as recommended in the quick start guide):

1. ubuntu-15.04-esdk-2016.3.1-headless-z7010 - The ethernet LEDs are blinking, the two green LEDs on the Parallella board are on constantly. However, the MAC address does not show up when I scan with Advanced IP Scanner. I also connect to an HDMI monitor, but nothing is displayed on the screen (which I gather is what is expected).
2. ubuntu-14.04-hdmi-z7010-20140611 - I used a converted to attach the board to my HDMI monitor. When I try this build, the ethernet LEDs are blinking, the two green LEDs on the Parallella board are on constantly. The MAC address still does not show up when I scan with Advanced IP Scanner. However, there are messages printed on the screen, so I attached a screenshot of these boot messages. I would rather use the headless version, but I thought that the boot messages may be a clue to help figure out the problem.
3. ubuntu-15.04-esdk-2016.3.1-headless-z7020 - Tried this on the off chance it might work, even though I checked the FPGA silkscreen and it is indeed a 7010. In any case, same result as the 7010 headless build: All LEDs lit as expected, MAC address does not show up in Advanced IP Scanner, and nothing on the HDMI monitor.

I first suspected a weak power supply. The power supply that came with the kit (which is indeed rated at 2.0A) was a bit weak - only 4.83V. And this is before running anything on the board! So I found another power supply rated at 2.5A, plugged it in, and I measured 5.13V. Then I tried all three builds as above, formatting the 32GByte card in between attempts. and the exact same thing happened.

It's not the ethernet cable - I've tried two different cables, and tested them using other devices.

I'm pretty sure it's not the SD card. I used it in a digital camera before attempting to use it here. I've tried a 4GByte card with the 7010 headless and hdmi builds, with the same results as above.

Any help will be appreciated!
Attachments
20161023_174517_small.jpg
Screenshot of boot messages with ubuntu-14.04-hdmi-z7010-20140611
20161023_174517_small.jpg (693.79 KiB) Viewed 33689 times
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Re: Possible dead board?

Postby sebraa » Mon Oct 24, 2016 8:13 am

This does not look like a dead board to me, because the kernel runs and complains about file system errors. SD cards are generally unreliable storage, and the Parallella uses your SD card in a different way than your camera does. I assume that the headless images fail in the same way as the HDMI image, but only a serial debug cable can tell for sure.

I assume that your 32 GB SD card is at fault or that you make a mistake in writing the images. The 4 GB SD card can't work since at least some older images were larger and trying to write would leave a corrupted file system - which the error message shows. You do not need to format your SD card between writes, because "formatting" there just creates a partition table and a FAT file system, which the image will overwrite immediately. It doesn't hurt, though.

I can imagine that you take out the SD card directly after the imager has said that its done, while the SD card itself is still in the process of writing its caches. Depending on how the SD card controller is built (there are huge differences!), this may corrupt the data and explain your error messages. Try a different SD card, a different SD card reader, or leave the SD card in while you reboot your computer after writing the image. You may have had bad luck with both cards, though.

My advice: Try to write the SD card from within a Linux system, and if that fails, use another different SD card with 8 GB (maybe 16, I can't remember).
sebraa
 
Posts: 495
Joined: Mon Jul 21, 2014 7:54 pm

Re: Possible dead board?

Postby macarphoto » Tue Oct 25, 2016 5:10 am

Thanks for the reply and advice! I've been working from home this evening, but I will try out your suggestions in the next couple of days and post my results. I actually don't have any 8 or 16GByte cards - only 32 and 64 (and the one 4GByte card I found lying around). But I will try different ones.
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Re: Possible dead board?

Postby aolofsson » Tue Oct 25, 2016 11:08 am

Sorry to hear that. This does look like an SD card issue, but can't be sure. In any case, I recommend picking up a serial cable for anyone doing headless development work. We have never seen a dead board exhibit this behaviour.

https://www.adafruit.com/products/954?g ... hgodKvEBtg

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Possible dead board?

Postby macarphoto » Wed Oct 26, 2016 6:17 am

Again, thanks to both of you for your replies.

I was able to try out another 32GByte card (the previous card was a class 10 Transcend, this new one a class 10 Samsung if that matters any). Same result with the headless build.

I never remove an SD card from my PC's built-in reader without ejecting it first, but sebraa's suggestion was worth a try. So I re-imaged the SD card with the headless build, restarted the computer. After restart, I ejected the card, installed it into the Parallella. Same result as before.

It seems like the only things left to try are a 8 or 16GB card (per sebraa's suggestions), and picking up a serial cable and getting more clues from the boot messages there (per aolofsson's suggestions), correct?

I'll try to find a smaller card somewhere, and order the cable to continue the debugging this weekend.

Thanks again,

macarphoto
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Re: Possible dead board?

Postby macarphoto » Sat Oct 29, 2016 6:24 pm

I bought a new SanDisk 16GByte card, and same result. I have used SD cards on many boards like this in the past (Matchstiq and Xilinx boards for work, and RBPi for home) and never had an SD card failure. If the symptoms with this Parallella card point to a bad SD card, then it may be a mechanical issue with the SD card socket itself. I was looking into debugging it with the JTAG port, but apparently I need to create an adapter for the PEC_POWER connector since porcupines are nowhere to be found. I think at this point, since I do enough hardware debugging at work and was hoping that this board would just start running, I will call this board a loss. Next time I will be sure to put a board through its paces as soon as I get it so I can return it if it doesn't work.

Thanks again for your help!
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Re: Possible dead board?

Postby aolofsson » Mon Oct 31, 2016 5:39 pm

The board is clearly starting to boot and doing a LOT of stuff to get to that point (uses dram, processor, flash, sd card). Seems more like a SW problem than a HW problem, but anything is possible...
A log from a serial cable will help debugging. Takes away the guess work in 9/10 cases.

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Possible dead board?

Postby macarphoto » Mon Oct 31, 2016 7:31 pm

Hello Andreas, how would you recommend attaching the serial cable to the board? The porcupine would be best but I can't find it anywhere. The only other thing I can think of is to buy the mating connector to the PEC_POWER connector and do some soldering. However, I don't have the soldering equipment to solder to a fine-pitch connector like the PEC_POWER connector.

Thanks,

Chris
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Re: Possible dead board?

Postby sebraa » Mon Oct 31, 2016 8:19 pm

The UART pins are available next to the Ethernet connector in the corner (see the small "Rx", "Tx" printed on the board). Use a 3.3 volt UART cable.
sebraa
 
Posts: 495
Joined: Mon Jul 21, 2014 7:54 pm

Re: Possible dead board?

Postby macarphoto » Thu Nov 03, 2016 3:27 am

Ok, I bought the serial cable, plugged it in and it seemed get a kernel panic (see below for the entire set of messages printed to the screen). In reading the other current "Kernel Panic" thread, it seems that I may be writing images to the card incorrectly(?). Do you agree? I am using a windows 10 machine; I have to get ahold of a linux machine, if this is what it takes to write the images correctly. So here is the process I use to image the cards (I've tried 4GB, 16GB, 32GB cards with the same result):

1. Using SD Formatter, I format the card. I've tried both "Full (Erase)" and "Full (Overwrite)", and "Format Size Adjustment" On. At one point in time, I tried it with "Format Size Adjustment" Off, but I don't recall if I was also doing "Full (Erase)" or "Full (Overwrite)"
2. Using Win32 Disk Imager, I write the image to the card.

Thanks!

Chris

**********************************
U-Boot 2012.10-00003-g792c31c (Jan 03 2014 - 12:24:08)

I2C: ready
DRAM: 992 MiB
WARNING: Caches not enabled
MMC: SDHCI: 0
SF: Detected N25Q128 with page size 64 KiB, total 16 MiB
In: serial
Out: serial
Err: serial
Net: zynq_gem
Hit any key to stop autoboot: 0
Configuring PL and Booting Linux...
Device: SDHCI
Manufacturer ID: 3
OEM: 5344
Name: SL16G
Tran Speed: 50000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 14.8 GiB
Bus Width: 4-bit
reading parallella.bit.bin

2083744 bytes read
reading uImage

6511160 bytes read
reading devicetree.dtb

13112 bytes read
## Booting kernel from Legacy Image at 03000000 ...
Image Name: Linux-4.4.0+
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6511096 Bytes = 6.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02a00000
Booting using the fdt blob at 0x02a00000
Loading Kernel Image ... OK
OK
Loading Device Tree to 1fff9000, end 1ffff337 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.0+ (esim@adapteva-dev) (gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2) ) #1 SMP Thu May 12 15:35:42 CEST 2016
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Adapteva Parallella Board with headless bitstream
[ 0.000000] cma: Reserved 64 MiB at 0x3a000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 12 pages/cpu @ef811000 s19136 r8192 d21824 u49152
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 252416
[ 0.000000] Kernel command line: console=ttyPS0,115200 earlyprintk root=/dev/mmcblk0p2 rootfstype=ext4 rw rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 924692K/1015808K available (8370K kernel code, 981K rwdata, 3812K rodata, 1052K init, 338K bss, 25580K reserved, 65536K cma-reserved, 163840K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0208000 - 0xc0dee850 (12187 kB)
[ 0.000000] .init : 0xc0def000 - 0xc0ef6000 (1052 kB)
[ 0.000000] .data : 0xc0ef6000 - 0xc0feb640 ( 982 kB)
[ 0.000000] .bss : 0xc0fee000 - 0xc1042ad0 ( 339 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to f0804000
[ 0.000000] zynq_clock_init: clkc starts at f0804100
[ 0.000000] Zynq clock init
[ 0.000000] global-timer: tied to cpu frequency, not supported with scaling
[ 0.000000] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.000018] sched_clock: 16 bits at 54kHz, resolution 18432ns, wraps every 603975816ns
[ 0.000055] timer #0 at f0808000, irq=17
[ 0.000497] Console: colour dummy device 80x30
[ 0.000516] Calibrating delay loop... 1327.10 BogoMIPS (lpj=3317760)
[ 0.025178] pid_max: default: 32768 minimum: 301
[ 0.025288] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.025307] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.025897] CPU: Testing write buffer coherency: ok
[ 0.026118] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.026173] Setting up static identity map for 0x209000 - 0x209098
[ 0.055167] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.055259] Brought up 2 CPUs
[ 0.055278] SMP: Total of 2 processors activated (2659.94 BogoMIPS).
[ 0.055278] CPU: All CPU(s) started in SVC mode.
[ 0.056218] devtmpfs: initialized
[ 0.059683] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.060236] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[ 0.064401] pinctrl core: initialized pinctrl subsystem
[ 0.066060] NET: Registered protocol family 16
[ 0.068788] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.085193] cpuidle: using governor ladder
[ 0.100197] cpuidle: using governor menu
[ 0.101819] zynq-gpio e000a000.gpio: could not find pctldev for node /amba/slcr@f8000000/pinctrl@700/gpio0-default, deferring probe
[ 0.107680] No ATAGs?
[ 0.107717] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.107717] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.108897] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.110740] Serial: AMBA PL011 UART driver
[ 0.140729] vgaarb: loaded
[ 0.141632] SCSI subsystem initialized
[ 0.142148] usbcore: registered new interface driver usbfs
[ 0.142222] usbcore: registered new interface driver hub
[ 0.142296] usbcore: registered new device driver usb
[ 0.142517] phy0 supply vcc not found, using dummy regulator
[ 0.142628] phy1 supply vcc not found, using dummy regulator
[ 0.143623] pps_core: LinuxPPS API ver. 1 registered
[ 0.143623] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.143660] PTP clock support registered
[ 0.143826] EDAC MC: Ver: 3.0.0
[ 0.146093] clocksource: Switched to clocksource ttc_clocksource
[ 0.156802] NET: Registered protocol family 2
[ 0.157355] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.157447] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.157594] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.157668] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.157705] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.157945] NET: Registered protocol family 1
[ 0.158350] RPC: Registered named UNIX socket transport module.
[ 0.158369] RPC: Registered udp transport module.
[ 0.158369] RPC: Registered tcp transport module.
[ 0.158387] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.159161] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.160544] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.172266] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.173114] NFS: Registering the id_resolver key type
[ 0.173170] Key type id_resolver registered
[ 0.173188] Key type id_legacy registered
[ 0.173262] ntfs: driver 2.1.32 [Flags: R/O].
[ 0.174626] bounce: pool size: 64 pages
[ 0.174847] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.174865] io scheduler noop registered
[ 0.174884] io scheduler deadline registered
[ 0.174921] io scheduler cfq registered (default)
[ 0.184948] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.184966] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.249350] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.251562] SuperH (H)SCI(F) driver initialized
[ 0.252207] msm_serial: driver initialized
[ 0.252594] STMicroelectronics ASC driver initialized
[ 0.253165] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 25, base_baud = 3125000) is a xuartps
[ 0.924594] console [ttyPS0] enabled
[ 0.929257] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to f085c000
[ 0.936261] [drm] Initialized drm 1.1.0 20060810
[ 0.949182] loop: module loaded
[ 0.953034] zram: Added device: zram0
[ 0.960757] m25p80 spi32766.0: unrecognized JEDEC id bytes: 10, 33, 0
[ 0.970268] libphy: Fixed MDIO Bus: probed
[ 0.975005] CAN device driver interface
[ 0.980388] libphy: MACB_mii_bus: probed
[ 0.984867] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 26 (04:4f:8b:00:4d:02)
[ 0.994636] macb e000b000.ethernet eth0: attached PHY driver [Marvell 88E1318S] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[ 1.006654] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[ 1.013547] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.021362] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 1.028754] usbcore: registered new interface driver pegasus
[ 1.034412] usbcore: registered new interface driver asix
[ 1.039776] usbcore: registered new interface driver ax88179_178a
[ 1.045859] usbcore: registered new interface driver cdc_ether
[ 1.051683] usbcore: registered new interface driver smsc75xx
[ 1.057416] usbcore: registered new interface driver smsc95xx
[ 1.063148] usbcore: registered new interface driver net1080
[ 1.068788] usbcore: registered new interface driver cdc_subset
[ 1.074687] usbcore: registered new interface driver zaurus
[ 1.080290] usbcore: registered new interface driver cdc_ncm
[ 1.087184] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.093653] ehci-pci: EHCI PCI platform driver
[ 1.098114] ehci-platform: EHCI generic platform driver
[ 1.103422] ehci-omap: OMAP-EHCI Host Controller driver
[ 1.108694] ehci-orion: EHCI orion driver
[ 1.112731] SPEAr-ehci: EHCI SPEAr driver
[ 1.116786] ehci-st: EHCI STMicroelectronics driver
[ 1.121689] ehci-exynos: EHCI EXYNOS driver
[ 1.125910] ehci-atmel: EHCI Atmel driver
[ 1.129946] tegra-ehci: Tegra EHCI driver
[ 1.134020] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.140139] ohci-pci: OHCI PCI platform driver
[ 1.144600] ohci-platform: OHCI generic platform driver
[ 1.149890] ohci-omap3: OHCI OMAP3 driver
[ 1.153926] SPEAr-ohci: OHCI SPEAr driver
[ 1.157982] ohci-st: OHCI STMicroelectronics driver
[ 1.162885] ohci-atmel: OHCI Atmel driver
[ 1.167216] usbcore: registered new interface driver usb-storage
[ 1.173630] e0002000.usb supply vbus not found, using dummy regulator
[ 1.180543] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 1.185390] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 1.201113] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 1.207288] hub 1-0:1.0: USB hub found
[ 1.210992] hub 1-0:1.0: 1 port detected
[ 1.216301] ci_hdrc ci_hdrc.1: doesn't support gadget
[ 1.221296] ci_hdrc ci_hdrc.1: no supported roles
[ 1.227286] mousedev: PS/2 mouse device common for all mice
[ 1.236152] i2c /dev entries driver
[ 1.243636] cdns-i2c e0004000.i2c: 100 kHz mmio e0004000 irq 23
[ 1.256004] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 666666 KHz
[ 1.263284] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 666667 KHz
[ 1.272445] Xilinx Zynq CpuIdle Driver started
[ 1.277367] sdhci: Secure Digital Host Controller Interface driver
[ 1.283468] sdhci: Copyright(c) Pierre Ossman
[ 1.289016] Synopsys Designware Multimedia Card Interface Driver
[ 1.295799] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.303485] sdhci-arasan e0101000.sdhci: No vmmc regulator found
[ 1.309439] sdhci-arasan e0101000.sdhci: No vqmmc regulator found
[ 1.341197] mmc0: SDHCI controller on e0101000.sdhci [e0101000.sdhci] using ADMA
[ 1.350708] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.357123] usbcore: registered new interface driver usbhid
[ 1.362671] usbhid: USB HID core driver
[ 1.389324] NET: Registered protocol family 10
[ 1.395425] sit: IPv6 over IPv4 tunneling driver
[ 1.401304] NET: Registered protocol family 17
[ 1.405691] can: controller area network core (rev 20120528 abi 9)
[ 1.411921] NET: Registered protocol family 29
[ 1.416327] can: raw protocol (rev 20120528)
[ 1.420548] can: broadcast manager protocol (rev 20120528 t)
[ 1.426225] can: netlink gateway (rev 20130117) max_hops=1
[ 1.432160] Key type dns_resolver registered
[ 1.436657] ThumbEE CPU extension supported.
[ 1.440878] Registering SWP/SWPB emulation handler
[ 1.451661] hctosys: unable to open rtc device (rtc0)
[ 1.460730] VDD_DSP: disabling
[ 1.464988] Waiting for root device /dev/mmcblk0p2...
[ 1.472674] mmc0: new high speed SDHC card at address aaaa
[ 1.478627] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[ 1.487788] mmcblk0: p1 p2
[ 1.583893] JBD2: no valid journal superblock found
[ 1.588760] EXT4-fs (mmcblk0p2): error loading journal
[ 1.605643] JBD2: no valid journal superblock found
[ 1.610528] EXT4-fs (mmcblk0p2): error loading journal
[ 1.615836] List of all partitions:
[ 1.619283] b300 15558144 mmcblk0 driver: mmcblk
[ 1.624536] b301 102400 mmcblk0p1 8debc16a-01
[ 1.629826] b302 3582976 mmcblk0p2 8debc16a-02
[ 1.635116] No filesystem could mount root, tried: ext4
[ 1.640425] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[ 1.648830] CPU1: stopping
[ 1.651540] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.0+ #1
[ 1.657419] Hardware name: Xilinx Zynq Platform
[ 1.661991] [<c02192a4>] (unwind_backtrace) from [<c02148bc>] (show_stack+0x10/0x14)
[ 1.669677] [<c02148bc>] (show_stack) from [<c0488d9c>] (dump_stack+0x7c/0x8c)
[ 1.676884] [<c0488d9c>] (dump_stack) from [<c0217a30>] (handle_IPI+0x188/0x1a8)
[ 1.684257] [<c0217a30>] (handle_IPI) from [<c020a75c>] (gic_handle_irq+0x90/0x94)
[ 1.691814] [<c020a75c>] (gic_handle_irq) from [<c0215414>] (__irq_svc+0x54/0x70)
[ 1.699260] Exception stack(0xee88bf58 to 0xee88bfa0)
[ 1.704311] bf40: 00000000 00000000
[ 1.712458] bf60: 2e92c000 00000000 ef820590 00000000 62370957 00000000 620d2140 00000000
[ 1.720623] bf80: c0fa7384 c0ef84f0 00000011 ee88bfa8 c084905c c084912c 60000013 ffffffff
[ 1.728789] [<c0215414>] (__irq_svc) from [<c084912c>] (cpuidle_enter_state+0x254/0x2c8)
[ 1.736862] [<c084912c>] (cpuidle_enter_state) from [<c0280b40>] (cpu_startup_entry+0x190/0x250)
[ 1.745617] [<c0280b40>] (cpu_startup_entry) from [<0020ab6c>] (0x20ab6c)
[ 1.752400] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
macarphoto
 
Posts: 7
Joined: Mon Oct 24, 2016 3:34 am

Next

Return to Troubleshooting

Who is online

Users browsing this forum: No registered users and 22 guests

cron