Hello,
I have a B3 which will not boot.
Tried reinstall with working usb stick (working perfectly on other B3)
I created a serial console and it hangs on boot see serial output below. green light keeps on.
**** serial output****
U-Boot 2010.06 (Jun 10 2011 - 09:06:51)
BUBBA|3
SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1116 Initializing on egiga0 @08 done
88E1116 Initializing on egiga1 @18 done
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
reading /install/install.itb
...........................................................................................................................................................................................................................................................................................................................................................
3560964 bytes read
## Booting kernel from FIT Image at 00800000 ...
Using 'config@1' configuration
Trying 'kernel@1' kernel subimage
Description: bubba-2.6.34
Type: Kernel Image
Compression: uncompressed
Data Start: 0x008000c4
Data Size: 1800528 Bytes = 1.7 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: md5
Hash value: 82879e5750f477cde5b1939c9a12b02f
Hash algo: sha1
Hash value: 2f7e9ef4397e4b8ff9d4117edbb3f50b6834c678
Verifying Hash Integrity ... md5+ sha1+ OK
## Loading init Ramdisk from FIT Image at 00800000 ...
Using 'config@1' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: Excito installer
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x009b7b40
Data Size: 1759121 Bytes = 1.7 MiB
Architecture: ARM
Hash algo: sha1
Hash value: 83f5ea97fa3caa47ec701d79da9e4f12a6a38931
Verifying Hash Integrity ... sha1+ OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
What can be the problem?
Can I test more with a connected serial cable?
Puma
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Boot problem B3
Boot problem B3
Linux is like a wigwam - no windows, no gates, apache inside!
Re: Boot problem B3
That's a bit odd.
Two things I would suggest:
1) could you press a key (via your serial connection) when it prompts you "Hit any key to stop autoboot" after power-on, then at U-Boot's B3 prompt type printenv and press enter, and post the output here?
2) you might also want to see if you can boot from my Gentoo B3 Live USB; not suggesting you use Gentoo at all, but the live USB image uses a more modern version of the kernel (3.17.1) with the L2 cache patch etc., so you might get some different diagnostic output via the serial console if you try it.
best
sakaki
Edit: I say 'odd', because that hang is reminiscent of the sort of thing that happens with the L2-cache problem on 3.x kernels, and which led to the solutions of either a) reflash U-Boot to a more modern version, in which the bug is fixed or b) use a patched kernel (as the live USB does, for example). However, the kernel you are trying to boot is 2.6.34... where I didn't think this whole L2 thing was an issue anyhow; also, the kernel passes its checksum tests...
Two things I would suggest:
1) could you press a key (via your serial connection) when it prompts you "Hit any key to stop autoboot" after power-on, then at U-Boot's B3 prompt type printenv and press enter, and post the output here?
2) you might also want to see if you can boot from my Gentoo B3 Live USB; not suggesting you use Gentoo at all, but the live USB image uses a more modern version of the kernel (3.17.1) with the L2 cache patch etc., so you might get some different diagnostic output via the serial console if you try it.
best
sakaki
Edit: I say 'odd', because that hang is reminiscent of the sort of thing that happens with the L2-cache problem on 3.x kernels, and which led to the solutions of either a) reflash U-Boot to a more modern version, in which the bug is fixed or b) use a patched kernel (as the live USB does, for example). However, the kernel you are trying to boot is 2.6.34... where I didn't think this whole L2 thing was an issue anyhow; also, the kernel passes its checksum tests...
Re: Boot problem B3
My output with printenv:
B3> printenv
bootdelay=1
baudrate=115200
preboot=
loadaddr=0x800000
console=ttyS0
bootfile=uImage
flashfile=u-boot.kwb
installfile=install.itb
setdiskargs=setenv bootargs root=$diskdev console=$console,$baudrate serial=${serial#} key=$key button=$button
setbootargs=setenv bootargs root=$rootdev rw console=$console,$baudrate $othbootargs
usbbootroot=/dev/sda1
usbbootdev=usb 0:1
usbboot=usb start; setenv diskdev $usbbootroot; run setdiskargs; ext2load $usbbootdev $loadaddr /boot/$bootfile; bootm
usbflashdev=usb 0:1
usbflash=fatload $usbflashdev $loadaddr /install/$flashfile && sf probe 0:0 && sf erase 0 80000; sf write $loadaddr 0 $filesize
satadev=sata 0:1
sataroot=/dev/sda1
sataboot=setenv diskdev $sataroot; run setdiskargs; ext2load $satadev $loadaddr /boot/$bootfile; bootm
usbinstallroot=/dev/ram0
usbinstalldev=usb 0:1
usbinstall=usb start; setenv diskdev $usbinstallroot; run setdiskargs; fatload $usbinstalldev $loadaddr /install/$installfile; bootm
bootalt1=run sataboot || reset
bootalt2=run usbinstall || run usbflash || run sataboot || reset
ethact=egiga0
ethaddr=00:22:02:00:26:5c
eth1addr=00:22:02:00:26:5d
serial#=5720
key=ti+esov8rZOuKmm+4Y/CFbTt0t0=
stdin=serial
stdout=serial
stderr=serial
button=0
bootcmd=run sataboot || reset
Environment size: 1242/65532 bytes
B3>
I try to boot with Gentoo B3 Live USB later this evening.
Puma
B3> printenv
bootdelay=1
baudrate=115200
preboot=
loadaddr=0x800000
console=ttyS0
bootfile=uImage
flashfile=u-boot.kwb
installfile=install.itb
setdiskargs=setenv bootargs root=$diskdev console=$console,$baudrate serial=${serial#} key=$key button=$button
setbootargs=setenv bootargs root=$rootdev rw console=$console,$baudrate $othbootargs
usbbootroot=/dev/sda1
usbbootdev=usb 0:1
usbboot=usb start; setenv diskdev $usbbootroot; run setdiskargs; ext2load $usbbootdev $loadaddr /boot/$bootfile; bootm
usbflashdev=usb 0:1
usbflash=fatload $usbflashdev $loadaddr /install/$flashfile && sf probe 0:0 && sf erase 0 80000; sf write $loadaddr 0 $filesize
satadev=sata 0:1
sataroot=/dev/sda1
sataboot=setenv diskdev $sataroot; run setdiskargs; ext2load $satadev $loadaddr /boot/$bootfile; bootm
usbinstallroot=/dev/ram0
usbinstalldev=usb 0:1
usbinstall=usb start; setenv diskdev $usbinstallroot; run setdiskargs; fatload $usbinstalldev $loadaddr /install/$installfile; bootm
bootalt1=run sataboot || reset
bootalt2=run usbinstall || run usbflash || run sataboot || reset
ethact=egiga0
ethaddr=00:22:02:00:26:5c
eth1addr=00:22:02:00:26:5d
serial#=5720
key=ti+esov8rZOuKmm+4Y/CFbTt0t0=
stdin=serial
stdout=serial
stderr=serial
button=0
bootcmd=run sataboot || reset
Environment size: 1242/65532 bytes
B3>
I try to boot with Gentoo B3 Live USB later this evening.
Puma
Linux is like a wigwam - no windows, no gates, apache inside!
Re: Boot problem B3
Your U-boot version is the same as that on one of my B3s... and your posted U-Boot printenv also looks sane (i have just diff-ed it against the one from that box); so that's not it...
Let me know how the live USB test goes.
best
sakaki
Let me know how the live USB test goes.
best
sakaki
Re: Boot problem B3
Dear Sakaki,
It took some time to find and create a usb stick.
After several attempts i got:
Puma
It took some time to find and create a usb stick.
Code: Select all
U-Boot 2010.06 (Jun 10 2011 - 09:06:51)
BUBBA|3
SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1116 Initializing on egiga0 @08 done
88E1116 Initializing on egiga1 @18 done
Hit any key to stop autoboot: 1 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
reading /install/install.itb
........
...........................................................................................................................................................................................
..................................................................................................................................................................
3660520 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Gentoo ARM: Linux 3.17.1-gentoo-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3660456 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.17.1-gentoo-r1-b3 (root@koneko) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #7 Tue Oct 21 16:07:11 BST 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: Excito B3
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: root=/dev/sda2 rootfstype=ext4 rootdelay=5 console=ttyS0,115200n8 earlyprintk
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 512044K/524288K available (5117K kernel code, 238K rwdata, 1464K rodata, 158K init, 645K bss, 12244K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06759b4 (6583 kB)
[ 0.000000] .init : 0xc0676000 - 0xc069d888 ( 159 kB)
[ 0.000000] .data : 0xc069e000 - 0xc06d9b40 ( 239 kB)
[ 0.000000] .bss : 0xc06d9b40 - 0xc077b220 ( 646 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000015] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[ 0.000217] Console: colour dummy device 80x30
[ 0.000238] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 0.090088] pid_max: default: 32768 minimum: 301
[ 0.090200] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090216] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090677] CPU: Testing write buffer coherency: ok
[ 0.091000] Setting up static identity map for 0x4dae30 - 0x4dae88
[ 0.091250] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.092287] devtmpfs: initialized
[ 0.093529] pinctrl core: initialized pinctrl subsystem
[ 0.093921] regulator-dummy: no parameters
[ 0.097038] NET: Registered protocol family 16
[ 0.097495] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.098385] cpuidle: using governor ladder
[ 0.098408] cpuidle: using governor menu
[ 0.098793] Feroceon L2: Enabling L2
[ 0.098834] Feroceon L2: Cache support initialised.
[ 0.099186] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.099274] [Firmware Info]: /ocp@f1000000/ethernet-controller@76000/ethernet1-port@0: local-mac-address is not set
[ 0.112866] vgaarb: loaded
[ 0.113142] SCSI subsystem initialized
[ 0.113618] usbcore: registered new interface driver usbfs
[ 0.113698] usbcore: registered new interface driver hub
[ 0.113904] usbcore: registered new device driver usb
[ 0.115204] Switched to clocksource orion_clocksource
[ 0.115447] FS-Cache: Loaded
[ 0.125820] NET: Registered protocol family 2
[ 0.126536] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.126590] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.126640] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.126692] TCP: reno registered
[ 0.126710] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.126730] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.126894] NET: Registered protocol family 1
[ 0.127347] RPC: Registered named UNIX socket transport module.
[ 0.127356] RPC: Registered udp transport module.
[ 0.127361] RPC: Registered tcp transport module.
[ 0.127367] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.128530] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.141206] FS-Cache: Netfs 'nfs' registered for caching
[ 0.142151] NFS: Registering the id_resolver key type
[ 0.142189] Key type id_resolver registered
[ 0.142196] Key type id_legacy registered
[ 0.142219] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.142242] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.143382] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.144290] msgmni has been set to 1000
[ 0.145943] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.145963] io scheduler noop registered
[ 0.146165] io scheduler cfq registered (default)
[ 0.147231] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.147759] irq: Cannot allocate irq_descs @ IRQ35, assuming pre-allocated
[ 0.148080] irq: Cannot allocate irq_descs @ IRQ67, assuming pre-allocated
[ 0.148654] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[ 0.148670] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.148680] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.148691] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.148954] PCI: bus0: Fast back to back transfers disabled
[ 0.148968] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.149105] PCI: bus1: Fast back to back transfers enabled
[ 0.149145] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.153688] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.154932] console [ttyS0] disabled
[ 0.154988] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 28, base_baud = 10416666) is a 16550A
[ 0.675967] console [ttyS0] enabled
[ 0.679959] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.725334] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.765314] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.770852] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.815312] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.855312] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.868150] brd: module loaded
[ 0.874784] loop: module loaded
[ 0.878053] Unable to handle kernel paging request at virtual address 00720084
[ 0.885261] pgd = c0004000
[ 0.887955] [00720084] *pgd=00000000
[ 0.891519] Internal error: Oops: 5 [#1] ARM
[ 0.895765] Modules linked in:
[ 0.898811] CPU: 0 PID: 1 Comm: swapper Not tainted 3.17.1-gentoo-r1-b3 #7
[ 0.905651] task: df43a000 ti: df44c000 task.ti: df44c000
[ 0.911021] PC is at slab_unmergeable+0x10/0x4c
[ 0.915528] LR is at __kmem_cache_alias+0xa8/0x170
[ 0.920298] pc : [<c009eb40>] lr : [<c00a14f4>] psr: 60000013
[ 0.920298] sp : df44de78 ip : 00000000 fp : 00000000
[ 0.931717] r10: fffffff8 r9 : 00000020 r8 : 00000020
[ 0.936910] r7 : c05ea0f0 r6 : 00000020 r5 : c06ae6ec r4 : 00720080
[ 0.943398] r3 : 00000000 r2 : 00000100 r1 : 00000000 r0 : 00720080
[ 0.949888] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
[ 0.957153] Control: 0005397f Table: 00004000 DAC: 00000017
[ 0.962864] Process swapper (pid: 1, stack limit = 0xdf44c1c0)
[ 0.968661] Stack: (0xdf44de78 to 0xdf44e000)
[ 0.972992] de60: df618000 df7de0c8
[ 0.981134] de80: df7de0c8 00000000 00000000 c05ea0f0 00000000 00000020 c06ae6e0 00000000
[ 0.989273] dea0: 00000000 c0083a7c 00000000 df44c000 00000000 c02477d0 df404b00 c0772400
[ 0.997412] dec0: 00000000 00000010 c06d9b40 c068a64c 00000000 df44c000 00000000 c068a6dc
[ 1.005551] dee0: 00000000 00000000 c06a84b8 c06a84b8 df70f560 c0008818 c06afc60 c05bd4e0
[ 1.013690] df00: c075bd7c df426240 c04dfd00 00000011 00000000 00000000 00000000 c00ed904
[ 1.021829] df20: dfffcea2 c04fddd4 000000bd c002af14 c06abfa4 00000000 c05eaec8 c0648dd8
[ 1.029967] df40: 00000006 00000006 00000000 c069d704 00000006 c0695be4 c06d9b40 c067651c
[ 1.038106] df60: 000000bd c0695bf0 00000000 c0676c58 00000006 00000006 c067651c fffffff6
[ 1.046245] df80: 57effbfc fffefdfc 00000000 c04d1618 00000000 00000000 00000000 00000000
[ 1.054384] dfa0: 00000000 c04d1620 00000000 c0009530 00000000 00000000 00000000 00000000
[ 1.062522] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1.070662] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 7cff7fe7 ffe769fe
[ 1.078808] [<c009eb40>] (slab_unmergeable) from [<c00a14f4>] (__kmem_cache_alias+0xa8/0x170)
[ 1.087299] [<c00a14f4>] (__kmem_cache_alias) from [<c0083a7c>] (kmem_cache_create+0x4c/0x1b8)
[ 1.095875] [<c0083a7c>] (kmem_cache_create) from [<c068a6dc>] (init_sd+0x90/0x164)
[ 1.103496] [<c068a6dc>] (init_sd) from [<c0008818>] (do_one_initcall+0x80/0x1cc)
[ 1.110944] [<c0008818>] (do_one_initcall) from [<c0676c58>] (kernel_init_freeable+0xec/0x1b4)
[ 1.119518] [<c0676c58>] (kernel_init_freeable) from [<c04d1620>] (kernel_init+0x8/0xe4)
[ 1.127575] [<c04d1620>] (kernel_init) from [<c0009530>] (ret_from_fork+0x14/0x24)
[ 1.135108] Code: e59f3040 e5933000 e3530000 1a000008 (e5902004)
[ 1.141213] ---[ end trace d4623c35d7d17f84 ]---
[ 1.145833] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 1.145833]
[ 1.154924] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 1.154924]
[ 82.795222] random: nonblocking pool is initialized
After several attempts i got:
Code: Select all
U-Boot 2010.06 (Jun 10 2011 - 09:06:51)
BUBBA|3
SoC: Kirkwood 88F6281_A0
DRAM: 512 MiB
In: serial
Out: serial
Err: serial
Net: egiga0, egiga1
88E1116 Initializing on egiga0 @08 done
88E1116 Initializing on egiga1 @18 done
Hit any key to stop autoboot: 1 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
reading /install/install.itb
........
...........................................................................................................................................................................................
..................................................................................................................................................................
3660520 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Gentoo ARM: Linux 3.17.1-gentoo-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3660456 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.17.1-gentoo-r1-b3 (root@koneko) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #7 Tue Oct 21 16:07:11 BST 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: Excito B3
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: root=/dev/sda2 rootfstype=ext4 rootdelay=5 console=ttyS0,115200n8 earlyprintk
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 512044K/524288K available (5117K kernel code, 238K rwdata, 1464K rodata, 158K init, 645K bss, 12244K reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06759b4 (6583 kB)
[ 0.000000] .init : 0xc0676000 - 0xc069d888 ( 159 kB)
[ 0.000000] .data : 0xc069e000 - 0xc06d9b40 ( 239 kB)
[ 0.000000] .bss : 0xc06d9b40 - 0xc077b220 ( 646 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000015] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[ 0.000217] Console: colour dummy device 80x30
[ 0.000238] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 0.090088] pid_max: default: 32768 minimum: 301
[ 0.090200] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090216] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090677] CPU: Testing write buffer coherency: ok
[ 0.091000] Setting up static identity map for 0x4dae30 - 0x4dae88
[ 0.091250] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.092287] devtmpfs: initialized
[ 0.093529] pinctrl core: initialized pinctrl subsystem
[ 0.093921] regulator-dummy: no parameters
[ 0.097038] NET: Registered protocol family 16
[ 0.097495] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.098385] cpuidle: using governor ladder
[ 0.098408] cpuidle: using governor menu
[ 0.098793] Feroceon L2: Enabling L2
[ 0.098834] Feroceon L2: Cache support initialised.
[ 0.099186] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[ 0.099274] [Firmware Info]: /ocp@f1000000/ethernet-controller@76000/ethernet1-port@0: local-mac-address is not set
[ 0.112866] vgaarb: loaded
[ 0.113142] SCSI subsystem initialized
[ 0.113618] usbcore: registered new interface driver usbfs
[ 0.113698] usbcore: registered new interface driver hub
[ 0.113904] usbcore: registered new device driver usb
[ 0.115204] Switched to clocksource orion_clocksource
[ 0.115447] FS-Cache: Loaded
[ 0.125820] NET: Registered protocol family 2
[ 0.126536] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.126590] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.126640] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.126692] TCP: reno registered
[ 0.126710] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.126730] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.126894] NET: Registered protocol family 1
[ 0.127347] RPC: Registered named UNIX socket transport module.
[ 0.127356] RPC: Registered udp transport module.
[ 0.127361] RPC: Registered tcp transport module.
[ 0.127367] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.128530] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.141206] FS-Cache: Netfs 'nfs' registered for caching
[ 0.142151] NFS: Registering the id_resolver key type
[ 0.142189] Key type id_resolver registered
[ 0.142196] Key type id_legacy registered
[ 0.142219] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.142242] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.143382] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.144290] msgmni has been set to 1000
[ 0.145943] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.145963] io scheduler noop registered
[ 0.146165] io scheduler cfq registered (default)
[ 0.147231] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.147759] irq: Cannot allocate irq_descs @ IRQ35, assuming pre-allocated
[ 0.148080] irq: Cannot allocate irq_descs @ IRQ67, assuming pre-allocated
[ 0.148654] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[ 0.148670] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.148680] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.148691] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.148954] PCI: bus0: Fast back to back transfers disabled
[ 0.148968] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.149105] PCI: bus1: Fast back to back transfers enabled
[ 0.149145] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.153688] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.154932] console [ttyS0] disabled
[ 0.154988] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 28, base_baud = 10416666) is a 16550A
[ 0.675974] console [ttyS0] enabled
[ 0.679966] mv_xor f1060800.xor: Marvell shared XOR driver
[ 0.725332] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.765314] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[ 0.770851] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.815313] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.855313] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.868146] brd: module loaded
[ 0.874875] loop: module loaded
[ 0.878918] sata_mv f1080000.sata: slots 32 ports 2
[ 0.887701] scsi host0: sata_mv
[ 0.891619] scsi host1: sata_mv
[ 0.895021] ata1: SATA max UDMA/133 irq 34
[ 0.899129] ata2: SATA max UDMA/133 irq 34
[ 0.904490] libphy: orion_mdio_bus: probed
[ 0.914899] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 1.994275] ata1: SATA link down (SStatus 0 SControl F300)
[ 2.000368] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:22:02:00:26:5c
[ 3.084289] ata2: SATA link down (SStatus 0 SControl F300)
[ 3.090313] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:22:02:00:26:5d
[ 3.099214] sky2: driver version 1.30
[ 3.103036] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.109557] ehci-pci: EHCI PCI platform driver
[ 3.114045] ehci-orion: EHCI orion driver
[ 3.118192] orion-ehci f1050000.ehci: EHCI Host Controller
[ 3.123669] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 3.131467] orion-ehci f1050000.ehci: irq 31, io mem 0xf1050000
[ 3.155237] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 3.161997] hub 1-0:1.0: USB hub found
[ 3.165779] hub 1-0:1.0: 1 port detected
[ 3.170436] usbcore: registered new interface driver usb-storage
[ 3.176823] rtc-mv f1010300.rtc: invalid RTC date, resetting to January 1st, 2013
[ 3.184578] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 3.191642] i2c /dev entries driver
[ 3.195429] md: raid0 personality registered for level 0
[ 3.200723] md: raid1 personality registered for level 1
[ 3.207603] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 3.217588] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.223115] usbcore: registered new interface driver usbhid
[ 3.228687] usbhid: USB HID core driver
[ 3.232724] oprofile: no performance counters
[ 3.237182] oprofile: using timer interrupt.
[ 3.241626] TCP: cubic registered
[ 3.244923] Initializing XFRM netlink socket
[ 3.249212] NET: Registered protocol family 17
[ 3.253658] NET: Registered protocol family 15
[ 3.258283] Key type dns_resolver registered
[ 3.263192] registered taskstats version 1
[ 3.268084] rtc-mv f1010300.rtc: setting system clock to 2013-01-01 08:32:08 UTC (1357029128)
[ 3.277932] Waiting 5 sec before mounting root device...
[ 3.485328] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 3.638708] hub 1-1:1.0: USB hub found
[ 3.642887] hub 1-1:1.0: 4 ports detected
[ 3.925634] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[ 4.047861] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 4.054862] scsi host2: usb-storage 1-1.1:1.0
[ 5.056897] scsi 2:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS
[ 5.067447] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 5.074130] sd 2:0:0:0: [sda] 8060928 512-byte logical blocks: (4.12 GB/3.84 GiB)
[ 5.082113] sd 2:0:0:0: [sda] Write Protect is off
[ 5.087364] sd 2:0:0:0: [sda] No Caching mode page found
[ 5.092664] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 5.104156] sda: sda1 sda2
[ 5.109367] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 8.285298] md: Waiting for all devices to be available before autodetect
[ 8.292065] md: If you don't use raid, use raid=noautodetect
[ 8.299305] md: Autodetecting RAID arrays.
[ 8.303395] md: Scanned 0 and added 0 devices.
[ 8.307874] md: autorun ...
[ 8.310665] md: ... autorun DONE.
[ 8.609165] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 8.616890] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[ 8.624124] Freeing unused kernel memory: 156K (c0676000 - c069d000)
INIT: version 2.88 booting
OpenRC 0.12.4 is starting up Gentoo Linux (armv5tel)
* Mounting /proc ...
[ ok ]
* Mounting /run ...
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Mounting /dev ...
[ ok ]
* Mounting /dev/mqueue ...
[ ok ]
* Mounting /dev/pts ...
[ ok ]
* Mounting /dev/shm ...
[ ok ]
* Creating list of required static device nodes for the current kernel ...
[ ok ]
* Mounting /sys ...
[ ok ]
* Mounting debug filesystem ...
[ ok ]
* setting up tmpfiles.d entries for /dev ...
[ ok ]
* Starting udev ...
[ ok ]
* Generating a rule to create a /dev/root symlink ...
[ ok ]
* Populating /dev with existing devices through uevents ...
[ ok ]
* Waiting for uevents to be processed ...
[ ok ]
* Setting system clock using the hardware clock [UTC] ...
[ ok ]
* Autoloaded 0 module(s)
* Checking local filesystems ...
/dev/sda2: Superblock last mount time (Tue Oct 21 23:14:05 2014,
now = Tue Jan 1 08:32:19 2013) is in the future.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
* Fileystem errors left uncorrected, aborting
[ !! ]
* rc: Aborting!
* fsck: caught SIGTERM, aborting
INIT: Entering runlevel: 3
* Starting bootled ...
[ ok ]
* Checking local filesystems ...
/dev/sda2: Superblock last mount time (Tue Oct 21 23:14:05 2014,
now = Tue Jan 1 08:32:19 2013) is in the future.
/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
* Fileystem errors left uncorrected, aborting
[ !! ]
* rc: Aborting!
* fsck: caught SIGTERM, aborting
This is (none).unknown_domain (Linux armv5tel 3.17.1-gentoo-r1-b3) 08:32:21
(none) login:
Puma
Linux is like a wigwam - no windows, no gates, apache inside!
Re: Boot problem B3
Hi Puma -
unfortunately, based on that first trace (the one that ends in the kernel oops), and given that the standard Excito image won't start on your B3 at all, I think you may have some fault in your hardware, possibly bad RAM...
you could try running mtest from the U-Boot prompt, to test your RAM...
unfortunately, based on that first trace (the one that ends in the kernel oops), and given that the standard Excito image won't start on your B3 at all, I think you may have some fault in your hardware, possibly bad RAM...
you could try running mtest from the U-Boot prompt, to test your RAM...
Re: Boot problem B3
Be careful with that conclusion. We've seen many weird errors in the past years that were attributed to hardware failure, and nearly all of those turned out to be something else
Re: Boot problem B3
Tried mtest for 2 hours no error.
Puma
Puma
Linux is like a wigwam - no windows, no gates, apache inside!
Re: Boot problem B3
I'd give it some time. This is not the fastest machine around. Memory errors can be hard to detect. I've once had memtest running for several hours on an old P66 machine until it hit a range of memory where one bit was faulty.
Re: Boot problem B3
What we have seen is installations that become corrupt for unknown reasons. Sometimes with parts of the filesystem missing (giving a partially working system), sometimes not booting at all. Throwing the USB stick in the bin and downloading a new install image has helped us a few times, but we never truly understood the root cause.
/Johannes (Excito co-founder a long time ago, but now I'm just Johannes)
Re: Boot problem B3
Hi Puma,
if mtest is still coming up with no errors after running for a considerable time, here are a few other things I would suggest:
Option 1: Getting the Live USB Running (Fixing the RTC)
Your second trace of running the live USB shows that you got most of the way to a running system (on which you should be able to run some other userland tests) - the only issue was caused by your real-time-clock (RTC) being considerably off, thinking it is Jan 2013, and so rejecting the root partition superblock last mount time as too far in the future).
However, I think it should still be far enough through init to allow you to log in and fix the RTC via the command line. So, could you try booting from the live USB again (until you get to the login: prompt), and then see if you can log in as user root, password gentoob3, via the serial terminal? If this works, then try setting your RTC to something sane (note, your prompt will probably be different, as the Gentoo init hasn't completed properly):
wait for a minute or so, then try rebooting from the Live USB. Do you get a clean startup into Gentoo now? (Note - you may need to re-write the USB key from the genb3disklessimg.xz file at this point, if things on the root partition have got really got messed up with all the clock changes, but with luck, the above should work.)
If you can get a clean startup, and then log in (root/gentoob3) again, you'll be able to run some further tests from a normal Linux environment, download additional software etc.
Option 2 - Try the Hard Drive from your other B3
You mentioned in your first post that you have successfully installed the standard Excito system on another B3. Since you are comfortable working with hardware (as you've presumably removed the PCB from your B3's case to solder the serial connection to it!) you could try cleanly powering down your 'good' B3, then putting its HDD in the problematic one, than powerering it up (without the rear button pressed), and observing the boot process via the serial terminal. NB - I would at least try to fix the RTC via the above procedure first though, before trying this, and ideally, take a backup of any critical data you have stored on your 'good' B3's HDD, before transplanting it temporarily in this manner.
Option 3 - Try the Excito Installer Again, with another USB Key
As Johannes suggests, you could try writing the Excito USB installer image to another USB key, and trying again. I have to admit that, based on the output you provided, it does appear that the kernel/ramdisk loaded OK from the stick (since both passed their checksum test upon extraction from the install.itb FIT image), so I would have expected to see some output on the serial terminal after the 'Starting kernel...' point even if the payload on the stick were corrupt in some way, but it is worth giving this a shot as well.
Other
Can I just check that you haven't made any other hardware mods to your B3 (the one you are having problems booting) other than soldering the serial cable to it?
best
sakaki
if mtest is still coming up with no errors after running for a considerable time, here are a few other things I would suggest:
Option 1: Getting the Live USB Running (Fixing the RTC)
Your second trace of running the live USB shows that you got most of the way to a running system (on which you should be able to run some other userland tests) - the only issue was caused by your real-time-clock (RTC) being considerably off, thinking it is Jan 2013, and so rejecting the root partition superblock last mount time as too far in the future).
However, I think it should still be far enough through init to allow you to log in and fix the RTC via the command line. So, could you try booting from the live USB again (until you get to the login: prompt), and then see if you can log in as user root, password gentoob3, via the serial terminal? If this works, then try setting your RTC to something sane (note, your prompt will probably be different, as the Gentoo init hasn't completed properly):
Code: Select all
b3 ~ # /bin/date 020510422015
(adjust as appropriate, the format is MMDDhhmmYYYY (Month, Day, hour, minute, year)).
b3 ~ # /sbin/hwclock --systohc
(to write the system clock to the RTC)
b3 ~ # /sbin/hwclock --show
(to check for sanity)
b4 ~ # /sbin/shutdown -P now
If you can get a clean startup, and then log in (root/gentoob3) again, you'll be able to run some further tests from a normal Linux environment, download additional software etc.
Option 2 - Try the Hard Drive from your other B3
You mentioned in your first post that you have successfully installed the standard Excito system on another B3. Since you are comfortable working with hardware (as you've presumably removed the PCB from your B3's case to solder the serial connection to it!) you could try cleanly powering down your 'good' B3, then putting its HDD in the problematic one, than powerering it up (without the rear button pressed), and observing the boot process via the serial terminal. NB - I would at least try to fix the RTC via the above procedure first though, before trying this, and ideally, take a backup of any critical data you have stored on your 'good' B3's HDD, before transplanting it temporarily in this manner.
Option 3 - Try the Excito Installer Again, with another USB Key
As Johannes suggests, you could try writing the Excito USB installer image to another USB key, and trying again. I have to admit that, based on the output you provided, it does appear that the kernel/ramdisk loaded OK from the stick (since both passed their checksum test upon extraction from the install.itb FIT image), so I would have expected to see some output on the serial terminal after the 'Starting kernel...' point even if the payload on the stick were corrupt in some way, but it is worth giving this a shot as well.
Other
Can I just check that you haven't made any other hardware mods to your B3 (the one you are having problems booting) other than soldering the serial cable to it?
best
sakaki
Re: Boot problem B3
With that time being off by that much, you might also want to replace the battery on the mainboard.
Re: Boot problem B3
Hello,
This weekend I have done the following:
1. replaced battery and yes there was some slight corrosion underneath the battery so I thought I found the problem
2. Booted with the Gentoo live usb stick and could log in and fix the RTC as written by Sakaki
This worked I could set the time and date. but after a short reboot with gentoo usb live it failed again during boot process.
3. Tried a new HD with a preinstall of clean B3 (installed on other good working B3)
B3 did boot once from this HD and could not be shutdown with button on the rear so probarbly crashed system i think (blue light was on)
If I take power off and serial cable off and leave it a while it will complete the boot process.
When I power up after a very short time it fails always.
I think I try a long memory test this week.
You guys are probarbly right that this is a hardware failure....
Thank you for all of your answers and help.
Puma
This weekend I have done the following:
1. replaced battery and yes there was some slight corrosion underneath the battery so I thought I found the problem
2. Booted with the Gentoo live usb stick and could log in and fix the RTC as written by Sakaki
This worked I could set the time and date. but after a short reboot with gentoo usb live it failed again during boot process.
3. Tried a new HD with a preinstall of clean B3 (installed on other good working B3)
B3 did boot once from this HD and could not be shutdown with button on the rear so probarbly crashed system i think (blue light was on)
If I take power off and serial cable off and leave it a while it will complete the boot process.
When I power up after a very short time it fails always.
I think I try a long memory test this week.
You guys are probarbly right that this is a hardware failure....
Thank you for all of your answers and help.
Puma
Linux is like a wigwam - no windows, no gates, apache inside!