tpm8

  • Content Count

    28
  • Joined

  • Last visited

Everything posted by tpm8

  1. 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 o
  2. 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.
  3. 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 bl
  4. 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 = 0
  5. 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 = 0x1
  6. 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 Ma
  7. Here we go - zip contains both 384MHz and 432MHz u-boot at DCDC3=1.30V ( CONFIG_AXP_DCDC3_VOLT=1300 ). cubietruck_uboot_binary_DCDC3_13v_20170219.zip
  8. 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
  9. 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
  10. 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. cubietruck_uboot_binary_20170213.zip
  11. That would be great. I would happily test DRAM clock settings more efficently.
  12. 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.
  13. 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 tha
  14. 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...
  15. 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.
  16. @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) u-boot-sunxi-with-spl.zip Copy u-boot binary: scp -p u-boot-sunxi-with-spl.bin cubietruck:/root/u-boot-sunxi-with-sp
  17. 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?
  18. 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 Cubiet
  19. 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.
  20. 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?
  21. 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.
  22. 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.
  23. 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 u
  24. 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...