Cubox doesn't boot after upgrade

This forum is for topics dealing with problems with software specifically in the ARMv7h repo.

Cubox doesn't boot after upgrade

Postby aflow » Sun Jun 08, 2014 3:35 pm

Hello,
My cubox is no longer able to boot after I perform a system upgrade today (pacman -Syu). The system is intalled in a SSD hard disk connected using eSata.

If I look at the startup information I can see that the kernel starts to load but suddenly it fails with the following message:
$this->bbcode_second_pass_code('', '[ 8.767987] systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
')

This is is the complete debug of the boot process:
$this->bbcode_second_pass_code('', 'U-Boot 2009.08 (Apr 08 2013 - 17:25:54) Marvell version: 5.4.4 NQ SR1

BootROM:
Version on chip: 2.33
Status: OK
Retries #: 0
Board: CuBox
SoC: 88AP510 (A1)
CPU: Marvell Sheeva (Rev 5)
CPU @ 800Mhz, L2 @ 400Mhz
DDR3 @ 400Mhz, TClock @ 166Mhz
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
DRAM: 1 GB
CS 0: base 0x00000000 size 512 MB
CS 1: base 0x20000000 size 512 MB
Addresses 60M - 0M are saved for the U-Boot usage.
SF: Detected W25Q32 with page size 4 kB, total 4 MB

Streaming disabled
L2 Cache Prefetch disabled
L2 Cache ECC disabled
Modifying CPU/CORE/DDR power rails to 1.0(+2.5%) / 1.0(-5%) / 1.5(-5%)
USB 0: Host Mode
USB 1: Host Mode
Setting VPU power OFF.
Setting GPU power ON.
MMC: MV_SDHCI: 0, MV_SDHCI: 1
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
===> Executing ext4load usb 0:1 0x02000000 /boot.scr
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
scanning bus for storage devices... 0 Storage Device(s) found
** Bad partition 1 **
===> Executing ext4load usb 1:1 0x02000000 /boot.scr
** Bad partition 1 **
===> Executing fatload usb 0:1 0x02000000 /boot.scr
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
===> Executing fatload usb 1:1 0x02000000 /boot.scr
** Can't read from device 1 **

** Unable to use usb 1:1 for fatload **
===> Executing ext4load usb 0:1 0x02000000 /boot/boot.scr
** Bad partition 1 **
===> Executing ext4load usb 1:1 0x02000000 /boot/boot.scr
** Bad partition 1 **
===> Executing fatload usb 0:1 0x02000000 /boot/boot.scr
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
===> Executing fatload usb 1:1 0x02000000 /boot/boot.scr
** Can't read from device 1 **

** Unable to use usb 1:1 for fatload **
===> Executing ext4load usb 0:2 0x02000000 /boot.scr
** Bad partition 2 **
===> Executing ext4load usb 1:2 0x02000000 /boot.scr
** Bad partition 2 **
===> Executing fatload usb 0:2 0x02000000 /boot.scr
** Can't read from device 0 **

** Unable to use usb 0:2 for fatload **
===> Executing fatload usb 1:2 0x02000000 /boot.scr
** Can't read from device 1 **

** Unable to use usb 1:2 for fatload **
===> Executing ext4load usb 0:2 0x02000000 /boot/boot.scr
** Bad partition 2 **
===> Executing ext4load usb 1:2 0x02000000 /boot/boot.scr
** Bad partition 2 **
===> Executing fatload usb 0:2 0x02000000 /boot/boot.scr
** Can't read from device 0 **

** Unable to use usb 0:2 for fatload **
===> Executing fatload usb 1:2 0x02000000 /boot/boot.scr
** Can't read from device 1 **

** Unable to use usb 1:2 for fatload **
===> Executing ext4load mmc 0:1 0x02000000 /boot.scr
Card did not respond to voltage select!
Device: MV_SDHCI
Manufacturer ID: 0
OEM: 0
Name: Tran Speed: 0
Rd Block Len: 0
MMC version 0.0
High Capacity: No
Capacity: 0
Bus Width: 1-bit
** Bad partition 1 **
===> Executing fatload mmc 0:1 0x02000000 /boot.scr
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
===> Executing ext4load mmc 0:1 0x02000000 /boot/boot.scr
** Bad partition 1 **
===> Executing fatload mmc 0:1 0x02000000 /boot/boot.scr
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
===> Executing ext4load mmc 0:2 0x02000000 /boot.scr
** Bad partition 2 **
===> Executing fatload mmc 0:2 0x02000000 /boot.scr
** Can't read from device 0 **

** Unable to use mmc 0:2 for fatload **
===> Executing ext4load mmc 0:2 0x02000000 /boot/boot.scr
** Bad partition 2 **
===> Executing fatload mmc 0:2 0x02000000 /boot/boot.scr
** Can't read from device 0 **

** Unable to use mmc 0:2 for fatload **
===> Executing ext4load ide 0:1 0x02000000 /boot.scr

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: SanDisk SDSSDP128G Firm: 2.0.0 Ser#: 131447400318
Type: Hard Disk
Supports 48-bit addressing
Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)

Loading file "/boot.scr" from ide device 0:1 hda1
** File not found /boot.scr
===> Executing fatload ide 0:1 0x02000000 /boot.scr
reading /boot.scr

** Unable to read "/boot.scr" from ide 0:1 **
===> Executing ext4load ide 0:1 0x02000000 /boot/boot.scr
Loading file "/boot/boot.scr" from ide device 0:1 hda1
1340 bytes read
## Executing script at 02000000
======== Starting boot ========
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
scanning bus for storage devices... 0 Storage Device(s) found
Loading file "/boot/uInitrd" from ide device 0:1 hda1
** File not found /boot/uInitrd
** Bad partition 1 **
** Bad partition 1 **
Loading file "/boot/uImage" from ide device 0:1 hda1
4039272 bytes read
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-3.5.7-11-ARCH+
Created: 2013-04-29 23:41:30 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4039208 Bytes = 3.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] CPU: ARMv7 Processor [560f5815] revision 5 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine: SolidRun CuBox
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 256032
[ 6.472944] Register vmeta clk
[ 6.499932]
[ 6.499932] [galcore] GC Version: GC Ver0.8.0.3184-1
[ 6.499962] galcore options:
[ 6.499976] irqLine = 48
[ 6.499991] registerMemBase = 0xF1840000
[ 6.500008] contiguousSize = 8388607
[ 6.500024] contiguousBase = 0x3F000000
[ 6.500041] bankSize = 0x02000000
[ 6.500057] fastClear = -1
[ 6.500071] compression = -1
[ 6.500086] signal = 48
[ 6.500101] baseAddress = 0x00000000
[ 6.500128]
[ 6.500128] [galcore] registerBase =0xf1840000, registerMemSize = 0x0003ffff, contiguousBase= 0x3f000000, contiguousSize = 0x007fffff
[ 6.500209] [galcore] streamCount = 1
[ 6.500228] [galcore] registerMax = 64
[ 6.500244] [galcore] threadCount = 256
[ 6.500261] [galcore] shaderCoreCount = 1
[ 6.500278] [galcore] vertexCacheSize = 8
[ 6.500296] [galcore] vertexOutputBufferSize = 512
[ 6.500600]
[ 6.500600] [galcore] real contiguouSize = 0x007fffff
[ 6.500646]
[ 6.500646] [galcore] chipModel=0x600,chipRevision=0x19,chipFeatures=0x87ecd,chipMinorFeatures=0x7
[ 6.501604] highmem bounce pool size: 64 pages
[ 6.508283] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 6.878485] [1] internal addr[0xffd00000],addr[0x10480000] size[524288]
[ 6.885309] [2] internal addr[0xffdc0000],addr[0x10410000] size[65536]
[ 6.891845] [3] internal addr[0xffdd9000],addr[0x103ed000] size[4096]
[ 7.033769] mmc0: Card removed during transfer!
[ 7.038297] mmc0: Resetting controller.
[ 7.105069] cubox_extclk_setup : add alias 'extclk/dovefb.0' to clkout0 w 0
[ 8.195483] set_clock_divider : setup reference clk to 74250074
[ 8.214576] set_clock_divider : setup reference clk to 74250074
[ 8.521991] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
[ 8.534033] EXT4-fs (sda1): couldn't mount as ext2 due to feature incompatibilities
[ 8.767987] systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
')

Any suggestions to solve this issue?.

Thanks.
aflow
 
Posts: 1
Joined: Sun Jun 08, 2014 3:27 pm

Re: Cubox doesn't boot after upgrade

Postby pepedog » Sun Jun 08, 2014 4:01 pm

Can you roll back to an older systemd package until this is worked out
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Cubox doesn't boot after upgrade

Postby WarheadsSE » Sun Jun 08, 2014 7:35 pm

Yup!
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm


Return to ARMv7h

Who is online

Users browsing this forum: No registered users and 15 guests