tpm8
-
Posts
28 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by tpm8
-
-
On 5/22/2018 at 11:19 AM, Igor said:
Yes. Fixed.
Still - or again - I'm getting this error.
Err:13 http://beta.armbian.com stretch Release 404 Not Found Reading package lists... Done E: The repository 'http://beta.armbian.com stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. -
This is a10-meminfo output with mainline u-boot @384 MHz and DCDC3=1.3V.
lima-memtester immediately freezes.
<1>Unable to handle kernel NULL pointer dereference at virtual address 00000124 <1>pgd = ee034000 <1>[00000124] *pgd=6ebb7831, *pte=00000000, *ppte=00000000 <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM [ 252.758001] Internal error: Oops: 17 [#1] PREEMPT SMP ARM <d>Modules linked in:[ 252.765391] Modules linked in: mali mali ump ump bnep bnep cpufreq_userspace cpufreq_userspace sunxi_ir sunxi_ir hidp hidp rfcomm rfcomm hci_uart hci_uart bluetooth bluetooth [last unloaded: scsi_wait_scan] [last unloaded: scsi_wait_scan]
root@cubietruck:~/a10-dram-tools# ./a10-meminfo dram_clk = 384 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05050505 active_windowing = 0
-
This is a10-meminfo output with mainline u-boot @432 MHz and default DCDC3 (1.25v). This is the mainline u-boot default defconfig for cubietruck.
Passed lima-memtester running about 12h (3 complete loops) without problems.
root@cubietruck:~/a10-dram-tools# ./a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x06060606 active_windowing = 0
-
This is a10-meminfo output with mainline u-boot @432 MHz and DCDC3=1.3V
Passed lima-memtester running about 8h (2 complete loops) without problems.
root@cubietruck:~/a10-dram-tools# ./a10-meminfo dram_clk = 432 mbus_clk = 300 dram_type = 3 dram_rank_num = 1 dram_chip_density = 8192 dram_io_width = 16 dram_bus_width = 32 dram_cas = 9 dram_zq = 0x7b (0x5294a00) dram_odt_en = 0 dram_tpr0 = 0x42d899b7 dram_tpr1 = 0xa090 dram_tpr2 = 0x22a00 dram_tpr3 = 0x0 dram_emr1 = 0x4 dram_emr2 = 0x10 dram_emr3 = 0x0 dqs_gating_delay = 0x05060606 active_windowing = 0
-
Quick test results from me with DCDC3=1.30V ( CONFIG_AXP_DCDC3_VOLT=1300 ).
Again seems stable with 432 MHz. (lima-memtester still running).
Two immediate freeze/crashes of lima-memtester with 384 Mhz:
root@cubietruck:~# ./lima-memtester 1536M This is a simple textured cube demo from the lima driver and a memtester. Both combined in a single program. The mali400 hardware is only used to stress RAM in the background. But this happens to significantly increase chances of exposing memory stability related problems. Kernel driver is version 14 Detected 1 Mali-400 GP Cores. Detected 2 Mali-400 PP Cores. FB: 1920x1080@32bpp at 0x44001000 (0x00FD2000) Using dual buffered direct rendering to FB. memtester version 4.3.0 (32-bit) Copyright (C) 2001-2012 Charles Cazabon. Licensed under the GNU General Public License version 2 (only). pagesize is 4096 pagesizemask is 0xfffff000 want 1536MB (1610612736 bytes) got 1536MB (1610612736 bytes), trying mlock ...locked. Loop 1: Stuck Address : setting 0 Mali: permit MALI_IOC_MEM_MAP_EXT ioctl for framebuffer (paddr=0x44000000, size=16777216) <6>mali: use config clk_div 1 <6>mali: clk_div 1 Mali: mali clock set completed, clock is 312000000 Hz <6>mali: use config clk_div 1 <6>mali: clk_div 1 Mali: mali clock set completed, clock is 312000000 Hz Mali: Mali device driver loaded <1>Unable to handle kernel paging request at virtual address ff725170 <1>Unable to handle kernel paging request at virtual address bb42bac4 $$$$ <1>Unable to handle kernel NULL pointer dereference at virtual address 00000000 [ 55.933111] Unable to handle kernel NULL pointer dereference at virtual address 00000000 <1>Unable to handle kernel paging request at virtual address ff00ed1c [ 55.954559] Unable to handle kernel paging request at virtual address ff00ed1c <1>Unable to handle kernel paging request at virtual address ff25c738 <1>pgd = ee624000 <1>[ff25c738] *pgd=00000000 <0>Internal error: Oops: 5 [#1] PREEMPT SMP ARM <d>Modules linked in: mali ump bnep cpufreq_userspace sunxi_ir hidp rfcomm hci_uart bluetooth [last unloaded: scsi_wait_scan] CPU: 0 Not tainted (3.4.113-sun7i #40) PC is at do_bad_area+0x34/0x8c LR is at do_translation_fault+0x6c/0x9c pc : [<c0019880>] lr : [<c0019954>] psr: 200f0193 sp : ee4de0b8 ip : ee4de000 fp : c0b4ff24 r10: 00000000 r9 : 00000001 r8 : ee4de188 r7 : ff25c738 r6 : 00000005 r5 : ff25c738 r4 : ee4de188 r3 : ff25c540 r2 : ee4de188 r1 : 00000005 r0 : ee4de188 Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Control: 10c5387d Table: 6e62406a DAC: 00000015 PC: 0xc0019800: 9800 eb02d986 e3500000 1affffc3 eaffff67 e3a01048 e28d0020 eb0f6f98 e28d1020 9820 eaffffc3 e3a01048 e28d0020 eb0f6f93 e28d1020 eaffffde e1a03005 e1a02006 9840 e1a01009 e1a00007 eb1c0315 e92d40f0 e24dd00c e1a04002 e1a05000 e1a0300d 9860 e3c3cd7f e5923040 e3ccc03f e1a06001 e313000f e59c300c 0a000006 e1a00002 9880 e59371f8 ebfffebb e3500000 0a00000c e28dd00c e8bd80f0 e58d2004 e3a0c001 98a0 e1a02001 e340c003 e1a01000 e58dc000 e1a00003 e3a0300b ebfffeba e28dd00c 98c0 e8bd80f0 e1a03004 e1a02006 e1a01005 e1a00007 eb1c02f2 e92d4010 ebffffda 98e0 e3a00000 e8bd8010 e35004bf 3a000023 e92d4070 e1a0c002 e5922040 e1a03000 LR: 0xc00198d4: 98d4 eb1c02f2 e92d4010 ebffffda e3a00000 e8bd8010 e35004bf 3a000023 e92d4070 98f4 e1a0c002 e5922040 e1a03000 e1a0e001 e312000f 0a00000d e3081ffc e34c10a3 9914 e1a04aa0 e7e02a50 e5916028 e1a01184 e0865001 ee120f10 e7952102 e3c00dff 9934 e3c0003f e3520000 e2400480 1a000005 e1a00003 e1a0200c e1a0100e ebffffbd 9954 e3a00000 e8bd8070 e7963184 e0801001 e7803184 e5953004 e5813004 ee071f3a 9974 f57ff04f e3a00000 e8bd8070 eafffedc e1a00600 ea02fa99 e92d4ff8 e1a04000 9994 e302092c e34c008d eb1c03d0 e1a00004 eb026003 e2144002 18bd8ff8 e302c1ec 99b4 e34cc0a9 e59ca004 e35a0000 da00004f e30f2b4c e34c20a2 e30d3414 e34c30b3 SP: 0xee4de038: e038 ee4dfe74 ee4dfdd0 ff723bd8 ff000000 ff000000 ff000000 ff000000 ff000000 e058 c0019880 200f0193 ffffffff ee4de0a4 ee4de188 c000e798 ee4de188 00000005 e078 ee4de188 ff25c540 ee4de188 ff25c738 00000005 ff25c738 ee4de188 00000001 e098 00000000 c0b4ff24 ee4de000 ee4de0b8 c0019954 c0019880 200f0193 ffffffff e0b8 00000000 00000000 ff000000 ff0007f9 ff007fc8 ff004000 ff25c738 ff019954 e0d8 ffa3177c ff000005 c00198e8 c00083bc 00000000 00000000 00000000 00000000 e0f8 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e118 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 IP: 0xee4ddf80: df80 0016f880 b64de070 00000001 c0000000 eeb4ff24 c071a508 0016f880 000198d8 dfa0 00000000 c000ec20 00000000 000007f9 c0007fc8 c0004000 ff25c738 c0019954 dfc0 c0a3177c 00000005 c00198e8 c00083bc 7fffffff 00000000 00000000 b670de3c dfe0 00000000 b670db40 00039ac4 00039ad4 800f0010 b670db4c 00000000 00000000 e000 ff000000 ff010001 ff000000 ff25c540 ffa34608 ff000000 ff000015 ff00f940 e020 ee25c540 ee25d500 ee16f880 ee4de000 c0a18940 c0a2c658 ee4dfe74 ee4dfdd0 e040 00723bd8 00000000 00000000 00000000 00000000 00000000 00019880 000f0193 e060 ffffffff ee4de0a4 ee4de188 c000e798 ee4de188 00000005 ee4de188 ff25c540 FP: 0xc0b4fea4: fea4 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 fec4 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 fee4 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ff04 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ff24 00000000 00000000 00000000 c07c5f64 ef004000 c07c5ed4 c09299c4 ef005600 ff44 00000000 00000000 0000003e 00000006 c07c5f64 c0929a44 eea30c00 00000001 ff64 00000000 0000003e 00000007 00000000 00000000 00000000 00000000 00000000 ff84 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 R0: 0xee4de108: e108 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e128 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e148 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e168 00000000 00000000 c0019880 200f0193 ffffffff ee4de1bc ee4de2a0 c000e798 e188 ee4de2a0 00000005 ee4de2a0 ff25c540 ee4de2a0 ff25c738 00000005 ff25c738 e1a8 ee4de2a0 00000001 00000000 c0b4ff24 ee4de000 ee4de1d0 c0019954 c0019880 e1c8 200f0193 ffffffff 00000000 00000000 00000000 000007f9 c0007fc8 c0004000 e1e8 ff25c738 c0019954 c0a3177c 00000005 c00198e8 c00083bc 00000000 00000000 R2: 0xee4de108: e108 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e128 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e148 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e168 00000000 00000000 c0019880 200f0193 ffffffff ee4de1bc ee4de2a0 c000e798 e188 ee4de2a0 00000005 ee4de2a0 ff25c540 ee4de2a0 ff25c738 00000005 ff25c738 e1a8 ee4de2a0 00000001 00000000 c0b4ff24 ee4de000 ee4de1d0 c0019954 c0019880 e1c8 200f0193 ffffffff 00000000 00000000 00000000 000007f9 c0007fc8 c0004000 e1e8 ff25c738 c0019954 c0a3177c 00000005 c00198e8 c00083bc 00000000 00000000 R3: 0xff25c4c0: c4c0 ******** ******** ******** ******** ******** ******** ******** ******** c4e0 ******** ******** ******** ******** ******** ******** ******** ******** c500 ******** ******** ******** ******** ******** ******** ******** ******** c520 ******** ******** ******** ******** ******** ******** ******** ******** c540 ******** ******** ******** ******** ******** ******** ******** ******** c560 ******** ******** ******** ******** ******** ******** ******** ******** c580 ******** ******** ******** ******** ******** ******** ******** ******** c5a0 ******** ******** ******** ******** ******** ******** ******** ******** R4: 0xee4de108: e108 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e128 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e148 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e168 00000000 00000000 c0019880 200f0193 ffffffff ee4de1bc ee4de2a0 c000e798 e188 ee4de2a0 00000005 ee4de2a0 ff25c540 ee4de2a0 ff25c738 00000005 ff25c738 e1a8 ee4de2a0 00000001 00000000 c0b4ff24 ee4de000 ee4de1d0 c0019954 c0019880 e1c8 200f0193 ffffffff 00000000 00000000 00000000 000007f9 c0007fc8 c0004000 e1e8 ff25c738 c0019954 c0a3177c 00000005 c00198e8 c00083bc 00000000 00000000 R5: 0xff25c6b8: c6b8 ******** ******** ******** ******** ******** ******** ******** ******** c6d8 ******** ******** ******** ******** ******** ******** ******** ******** c6f8 ******** ******** ******** ******** ******** ******** ******** ******** c718 ******** ******** ******** ******** ******** ******** ******** ******** c738 ******** ******** ******** ******** ******** ******** ******** ******** c758 ******** ******** ******** ******** ******** ******** ******** ******** c778 ******** ******** ******** ******** ******** ******** ******** ******** c798 ******** ******** ******** ******** ******** ******** ******** ******** R7: 0xff25c6b8: c6b8 ******** ******** ******** ******** ******** ******** ******** ******** c6d8 ******** ******** ******** ******** ******** ******** ******** ******** c6f8 ******** ******** ******** ******** ******** ******** ******** ******** c718 ******** ******** ******** ******** ******** ******** ******** ******** c738 ******** ******** ******** ******** ******** ******** ******** ******** c758 ******** ******** ******** ******** ******** ******** ******** ******** c778 ******** ******** ******** ******** ******** ******** ******** ******** c798 ******** ******** ******** ******** ******** ******** ******** ******** R8: 0xee4de108: e108 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e128 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e148 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 e168 00000000 00000000 c0019880 200f0193 ffffffff ee4de1bc ee4de2a0 c000e798 e188 ee4de2a0 00000005 ee4de2a0 ff25c540 ee4de2a0 ff25c738 00000005 ff25c738 e1a8 ee4de2a0 00000001 00000000 c0b4ff24 ee4de000 ee4de1d0 c0019954 c0019880 e1c8 200f0193 ffffffff 00000000 00000000 00000000 000007f9 c0007fc8 c0004000 e1e8 ff25c738 c0019954 c0a3177c 00000005 c00198e8 c00083bc 00000000 00000000 <1>Unable to handle kernel paging request at virtual address 004de074 <1>pgd = ee624000 <1>[004de074] *pgd=00000000
-
@tpm8: could you please compile an 384 u-boot with that option ... then I can retest that too
Here we go - zip contains both 384MHz and 432MHz u-boot at DCDC3=1.30V ( CONFIG_AXP_DCDC3_VOLT=1300 ).
-
Thanks - you are right. I saw the crash during unload of the wireless kernel module but wouldn't guess that it was related.
Commenting the line ap6210 in /etc/modules fixed it.
PS: And even better - disabling WLAN also fixed that 10-20 seconds delay during ssh login
-
Installed armbian 5.25 jessie legacy from scratch. No changes to network configuration.
Cubietruck:
- eth0 (wired ethernet) - DHCP - works fine
- WLAN0 - driver is loaded during boot - but not used at all
Default /etc/networking/interfaces config:
allow-hotplug eth0 iface eth0 inet dhcp auto lo iface lo inet loopback
Reboot hangs forever during shutdown while executing the following stop (!!) skript:
[ *** ] A stop job is running for LSB: Raise network interfa...13s / no limit)
Tried both possible solutions to define a timeout of 15 secs from http://unix.stackexchange.com/questions/186162/how-to-change-timeout-in-systemctl
But this does not work - it keeps saying "no limit".
Question is - why does i raise network interfaces during sytem stop anyway?
TIA
Tobias
Lines grabbed from shutdown:
... [ OK ] Stopped Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Stopped Getty on tty1. [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Stopped WPA supplicant. [ OK ] Stopped Bluetooth service. [ OK ] Stopped User Manager for UID 0. [ OK ] Stopped LSB: disk temperature monitoring daemon. [ OK ] Stopped LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Stopped LSB: Starts LIRC daemon.. [ OK ] Stopped LSB: Start NTP daemon. [ OK ] Stopped LSB: Armbian gathering hardware information. [ OK ] Stopped LSB: Advanced IEEE 802.11 management daemon. [ OK ] Stopped LSB: Start/stop sysstat's sadc. [ OK ] Started Store Sound Card State. [ OK ] Started Unattended Upgrades. Stopping LSB: set CPUFreq kernel parameters... [ OK ] Stopped target Network is Online. Stopping Login Service... [ OK ] Removed slice user-0.slice. Stopping LSB: Patch firmware for brcm40183 Bluetooth adapter... [ OK ] Removed slice system-serial\x2dgetty.slice. [ OK ] Removed slice system-getty.slice. Stopping /etc/rc.local Compatibility... [ OK ] Stopped /etc/rc.local Compatibility. Stopping Permit User Sessions... [ OK ] Stopped Login Service. [ OK ] Stopped LSB: set CPUFreq kernel parameters. [ OK ] Stopped LSB: Patch firmware for brcm40183 Bluetooth adapter. [ OK ] Stopped Permit User Sessions. [ OK ] Stopped target Network. Stopping LSB: Load kernel modules needed to enable cpufreq scaling... [ OK ] Stopped LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Stopped target Basic System. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Stopped target Paths. [ OK ] Stopped target Timers. [ OK ] Stopped target Sockets. [ OK ] Closed Syslog Socket. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Stopped target System Initialization. Stopping Load/Save RF Kill Switch Status of rfkill4... Stopping Load/Save RF Kill Switch Status of rfkill1... Stopping Load/Save RF Kill Switch Status of rfkill2... Stopping Load/Save RF Kill Switch Status of rfkill0... Stopping Restore / save the current clock... Stopping Update UTMP about System Boot/Shutdown... Stopping Apply Kernel Variables... [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped target Encrypted Volumes. Stopping Load Kernel Modules... [ OK ] Stopped Load Kernel Modules. Stopping LSB: Raise network interfaces.... [ OK ] Stopped target Swap. Deactivating swap /var/swap... [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Remote File Systems (Pre). [ OK ] Stopped Load/Save RF Kill Switch Status of rfkill4. [ OK ] Stopped Load/Save RF Kill Switch Status of rfkill1. [ OK ] Stopped Load/Save RF Kill Switch Status of rfkill2. [ OK ] Stopped Load/Save RF Kill Switch Status of rfkill0. [ OK ] Stopped Restore / save the current clock. [ OK ] Stopped Update UTMP about System Boot/Shutdown. [ OK ] Deactivated swap /var/swap. Stopping Create Volatile Files and Directories... [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Removed slice system-systemd\x2drfkill.slice. [* ] A stop job is running for LSB: Raise network interfa...32s / no limit) -
Status: Prepared new sdcard with armbian 5.25 Legacy 3.4.113, only did apt-getupdate/upgrade afterwards
u-boot 5.25 (original unchanged) time to freeze:
Try 1: approx. 10 secs
Try 2: approx. 30 secs
Try 3: approx. 10mins
Try 4: approx. 10mins
Try 5: approx. 9 mins
@tpm8: can you provide a binary u-boot which is the same base as 5.25 but with the unchanged clock-speed? So that we can make sure that this is really the only difference? Or should I use your November u-boot?
I've compiled from mainline u-boot yesterday (13/02/2017) with unmodified cubietruck defconfig (CONFIG_DRAM_CLK=432 ) and another version with reduced clock speed (CONFIG_DRAM_CLK=384) that is used in armbian.
I guess it's the same version that is used in armbian 5.25 (but can't be sure).
Please find attached a zip with both binaries.
-
Since we are testing the DRAM settings in U-Boot, the choice of kernel does not really matter. For the sake of convenience, the Orange Pi PC testing had been done via a special FEL boot package: https://github.com/ssvb/lima-memtester/releases/tag/20151207-orange-pi-pc-fel-test
I can easily prepare something like this for the Cubietruck too.
That would be great. I would happily test DRAM clock settings more efficently.
-
...
I found http://linux-sunxi.org/Hardware_Reliability_Tests... will try it ...
Update: Sorry, I need support ... I use Mainline kernel from Armbian 16.04 (Xenial) default image:
...
Failed to 'modprobe mali'. Aborted
root@cubietruck5:~# modprobe mali modprobe: FATAL: Module mali not found in directory /lib/modules/4.9.7-sunxi
Any idea? Do I need to change more ? Or is it a problem with mainline kernel ?
From here: http://linux-sunxi.org/A10_DRAM_Controller_Calibration
It is required to have the sunxi-3.4 kernel (specifically for for the mali kernel module). The mainline kernel is not supported yet because it is lacking in the graphics department.
-
Folks,
I did some more testing with armbian 5.25 (jessie legacy) on my "problematic" cubie truck:
- again unstable with armbian u-boot 5.25 Package ( crash after few seconds running lima memtester)
- stable with own compiled current mainline u-boot with default cubietruck defconfig (DRAM clock speed: 432 MHz) - completed 35 runs of lima memtester over night without problems
- but also unstable with current mainline u-boot at DRAM clock speed 384 MHz ( crash after few seconds running lima memtester)
So I'm quite sure now, that one of my two cubietrucks is a rare (??) exemplar that is UNSTABLE at 384 MHz - whatever u-boot version.
The only difference in the defconfig is slightly lower DRAM frequency in Armbian compared to mainline:
Thanks - this confirms my finding.
Keep in mind that different units may have slightly different tolerances and overclocking potential even if it's the same board model. For example, have a look at https://linux-sunxi.org/Orange_Pi_PC#DRAM_clock_speed_limit
Some Orange Pi PC boards pass the lima-memtester test with DRAM clocked at 720 MHz, while the others fail it at 672 MHz. The same is very likely true for the Cubietruck.
Again, this Orange Pi Example fits with my observation that a LOWER clock speed also can cause stability problems.
OK, lower DRAM clock frequency can explain why stability problems disappeared. Why was it lowered in armbian in the first place? Was it there to address reliability problems? If yes, then why hasn't it been reported to mainline yet?
...Edit: Various reports in this discussion thread are very confusing and contradict each other. For example, tpm8 mentioned that the mainline U-Boot was stable with the 432MHz DRAM clock speed, while armbian was not. Please get your act together.
Good question.
But I think there is not that much contradiction:
- At least for mine cubietruck the lower DRAM clock speed is apparently bad.
- most probably armbian 5.17 and 5.20 u-boot versions were build _before_ lowering DRAM clock speed in armbian cubietruck defconfig - so they are stable for me (and appollon77 ??)
-
@tpm8: What kernel you use? I unse vanilla (so "next" here, means kernel 4.9.7). I read that the "setenv bootm_boot_mode sec" is needed for sunxi-3.4 kernel ... so is your file compatible with my system at all?
You are right - I use the legacy 3.4.x kernel. So skip editing boot.cmd with mainline / vanilla kernel - I changed my post above. My system hang during kernel boot without the bootm_boot_mode line.
Compiling u-boot is completely independent from the kernel that is booted afterwards. So the compiled u-boot should work for you too.
Anyway - fiddling with u-boot can make your system stop booting at all. This is why I mentioned to have an SD card backup before doing so...
-
Cool, will try tonight. After booting successfully is there a way to see that the new u-boot was used to boot without looking at the console during boot (because the cubietruck where I can see if it worked with the InfluxDB on it is located in my cellar and no monitor there :-) )
Afraid a monitor in the cellar won't be good enough - there is no easy way to see u-boot boot messages. These are visible on a serial console only ( see http://linux-sunxi.org/Cubieboard/TTL ). dmesg logging only starts after loading the Linux kernel.
-
@apollon77 - mine cross-compliled u-boot was stable (at least it passed several runs of CPU stress tester and LIMA memtester).
Backup your SD-Card before installing u-boot!
Legacy 3.4 kernel only - You have to add the following line to /boot/boot.cmd:
setenv bootm_boot_mode sec
Legacy 3.4 kernel only - Build new boot script:
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
Download u-boot from here
(as I can't attach a binary to this thread)Copy u-boot binary:
scp -p u-boot-sunxi-with-spl.bin cubietruck:/root/u-boot-sunxi-with-spl_20161122.bin
Write u-boot to boot sector:
root@cubietruck:~# dd if=u-boot-sunxi-with-spl_20161122.bin of=/dev/mmcblk0 bs=1024 seek=8
Sync & reboot:
root@cubietruck:~# sync root@cubietruck:~# reboot
Serial console should show the following during boot:
U-Boot SPL 2016.11-00108-gca39bd8 (Nov 22 2016 - 12:52:25) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2016.11-00108-gca39bd8 (Nov 22 2016 - 12:52:25 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubietruck I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 ...
-
No. Unfortunately not. I've searched for it at git hub, but without success.
Anyone a hint, where to find the armbian cubietruck u-boot defconfig file?
-
Finally got the second Cubietruck and did some more testing. Here are the results.
"Works stable" means a minimum complete run of lima-memtester and cpufreq-ljt-stress-test (cpuburn-arm).
Cubie1 (old, existent):
- SKhynix H5TQ4G63AFR-PBC DRAM chips.
- Works rock solid with armbian u-boot 5.17 and u-boot 5.20 ( U-Boot SPL 2016.09-armbian )
- very unstable (boot errors, LIMA memtester crashes the kernel instantly, see here) with armbian u-boot 5.23 and beta 5.24 ( U-Boot 2016.11 )
- stable with own crosscompiled mainline u-boot SPL 2016.11-00108-gca39bd8 using unmodified default Cubietruck_defconfig file (CONFIG_DRAM_CLK=432)
Cubie2 (new arrival):
- has also SKhynix H5TQ4G63AFR-PBC DRAM chips
- works stable with all u-boot versions, eg. armbian 5.20, 5.23 and beta 5.24.161212 / U-Boot SPL 2016.11-armbian
This means, that the problem/behaviour
- isn't related to SKhynix DRAM chips (same chips on both cubie trucks)
-
isn't related to DRAM clock speed( problematic cubie1 runs stable with mainline u-boot at DRAM_CLK 432MHz but crashes with armbian u-boot 5.23 at lower 384 MHz)Edit 14/02/2017: is most probably related to DRAM clock speed of 384 MHz. I think I own a rare Cubietruck that is stable with 432MHz _but_ unstable at 384MHz.
- is probably related to armbian u-boot customizing for Cubietruck.
Edit 14/02/2017: only in so far that armbian lowered DRAM clock speed for Cubietruck to 384 MHz for cubie u-boot defconfig.
Where can I find armbian cubietruck u-boot defconfig file in order to compare it to the mainline default config?
-
You can't get this information in a software way. Just check the markings on the four DRAM chips on the board. For example, the original https://linux-sunxi.org/Cubietruck used GT8UB512M8EN-BG chips and you can find them on the pictures.
It is necessary to recompile U-Boot for this after changing the DRAM clock speed settings in the 'configs/Cubietruck_defconfig' file. You can find some instructions here: https://linux-sunxi.org/Mainline_U-Boot#Compile_U-Boot
Ok. Mine has SKhynix SKhynix H5TQ4G63AFR-PBC DRAM chips. The board says CUBIETRUCK V1.0-06.06 printed on it.
Link to photo of the board: http://workupload.com/file/hGEwhZh
I also managed to compile latest u-boot. As soon as the other unit arrives I'm going make further tests.
-
Crash on the Xenial server (so vanilla = next) with 5.24 after 9h in normal operation (there is mainly an influxdb+redis slave running).
Went back to 5.20 there.
On Debian Wheezy (legacy=default) still ok ... will see there.
Powering can not be the reason.
Almost glad that I'm not the only one...
-
Please check what DRAM chips do you have on your board, and ideally you should run lima-memtester with different DRAM clock speeds to find if lower value works for you.
Could you please give me some advise
- how to identify DRAM chips (dmesg? armbianmonitor?)
- how to modify DRAM clock speeds? (do I have to compile an individual kernel for that? boot.cmd parameter?
-
If lima-memtester simply crashes, then it sounds more like power supply issue than DRAM instability or some other hardware issue.
I don't think it's power or hardware related, because same configuration works fine with 5.20 u-boot. lima-memtester runs without problems for hours...
Maybe I used the wrong words. Calling lima-memtester does not crash itself but immediately freezes / crashes the kernel. The cube is shown on the screen.
Anyway I've ordered another cubietruck to completely rule out individual hardware problems.
-
Reboot and make sure you got a proper u-boot. I made few tests and I could reproduce an error easily while on latest u-boot I could run limatester stable over the night.
I've prepared a new SD card from scratch with 5.20 image + all updates + 5.24 beta u-boot for the test. Several reboots with this clean image but still unstable on my cubietruck. Probably a different hardware revision?
On my "production" SD card with u-boot 5.20 (otherwise same packages and same jessie legacy kernel) everything is rock solid. There i can Lima Tester for hours without problems.
In order to completely rule out hardware problems I've ordered another (used) cubietruck. As soon as it is delivered I'm able to do more testing.
-
Unfortunately - still no success with u-boot 5.24.161116
Unpacking linux-u-boot-cubietruck-default (5.24.161116) over (5.23) ... Setting up linux-u-boot-cubietruck-default (5.24.161116) ... Updating u-boot on device /dev/mmcblk0
I've seen this time two different errors as soon as some load was put on the cubietruck. Sometimes it won't even boot to the prompt.
Unable to handle kernel paging request at virtual address xxxxxx or Console: Internal Error: Oops - undefined instruction: 0 [#1] PREEMPT SMP ARM
Again, starting LIMA Memtester crashed the cubie immediately.
If it is of any use - I've uploaded detailed boot log:
root@cubietruck:~# armbianmonitor -u /var/log/armhwinfo.log has been uploaded to http://sprunge.us/NDDH
Hope this helps. TIA
Tobias
-
Can't find any cubietruck uboot packages on beta any more??
E.g. http://beta.armbian.com/pool/main/l/linux-u-boot-cubietruck-default/doesn't exist...
BSP scripts RFC
in Armbian build framework
Posted
Using armbian 5.51 debian stretch I found the following errors in the system log from the reboot after a system crash. At least Apache failed to start.
root@hc1:/var/log# journalctl | grep "/var/log" Jul 09 12:13:16 hc1 apachectl[970]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for main error log Jul 09 12:13:16 hc1 apachectl[970]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost defined at /etc/apache2/sites-enabled/nextcloud.conf:7 Jul 09 12:13:16 hc1 apachectl[970]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost defined at /etc/apache2/sites-enabled/default-ssl.conf:2 Jul 09 12:13:16 hc1 apachectl[970]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/apache2/' for error log of vhost defined at /etc/apache2/sites-enabled/000-default.conf:1 Jul 09 12:13:21 hc1 nmbd[1414]: mkdir failed on directory /var/log/samba/cores: No such file or directory Jul 09 12:13:21 hc1 nmbd[1414]: Failed to create /var/log/samba/cores for user 0 with mode 0700 Jul 09 12:13:21 hc1 nmbd[1414]: Unable to open new log file '/var/log/samba/log.': No such file or directory Jul 09 12:13:21 hc1 nmbd[1414]: Unable to open new log file '/var/log/samba/log.nmbd': No such file or directory Jul 09 12:13:22 hc1 smbd[1439]: Unable to open new log file '/var/log/samba/log.smbd': No such file or directory Jul 09 12:13:22 hc1 smbd[1439]: Unable to open new log file '/var/log/samba/log.smbd': No such file or directory Jul 09 12:13:22 hc1 smbd[1439]: Unable to open new log file '/var/log/samba/log.smbd': No such file or directoryCould you please add samba and apache2 log directory to the function RecreateLogs in /usr/lib/armbian/armbian-ramlog:
RecreateLogs (){ # in case of crash those services doesn't start if there are no dirs & logs [ ! -d /var/log/proftpd ] && mkdir -p /var/log/proftpd [ ! -d /var/log/nginx ] && mkdir -p /var/log/nginx [ ! -d /var/log/apache2 ] && mkdir -p /var/log/apache2 [ ! -d /var/log/samba ] && mkdir -p /var/log/samba [ ! -f /var/log/proftpd/controls.log ] && touch /var/log/proftpd/controls.log [ ! -f /var/log/nginx/access.log ] && touch /var/log/nginx/access.log [ ! -f /var/log/nginx/error.log ] && touch /var/log/nginx/error.log }Probably it would be a good idea to schedule a ramlog syncToDisk once per day using an systemd timer?
Thanks & keep up the good work.
Tobias