Jump to content

Espressobin support development efforts


lanefu

Recommended Posts

On 2-1-2018 at 7:13 PM, ebin-dev said:

 

All my best wishes to everybody too.

The file /etc/default/cpufrequtils was overwritten by default values - since you use a system with 1200MHz max frequency you need to change the values back to something like this (that was the reason why I recommended to flash u-boot with 1000MHz):

 

Thanks ebin-dev,

 

My cpufrequtils are:

ENABLE=true
MIN_SPEED=200000
MAX_SPEED=1200000
GOVERNOR=ondemand

 

The scaling doesn't work for me.

 

In the passed I tested with the 1000MHz u-boot but got a lot of kernel-panics.

Now, a few weeks or more later, I'll flash my u-boot again to 1000MHz. See what's happen.

 

 

kr.,

Patrick

Link to comment
Share on other sites

13 hours ago, Patrick said:

The scaling doesn't work for me.

 

I have checked your settings 1200MHz / 200MHz with my system:

 

Quote

# cat /proc/version

Linux version 4.4.107-mvebu64 (root@xeon) (gcc version 6.4.1 20171012 (Linaro GCC 6.4-2017.11) ) #7 SMP PREEMPT Sat Dec 30 14:02:18 CET 2017

 

# cpufreq-info 
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 50.0 us.
  hardware limits: 200 MHz - 1.20 GHz
  available frequency steps: 200 MHz, 300 MHz, 600 MHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 200 MHz and 1.20 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 300 MHz.
  cpufreq stats: 200 MHz:34.62%, 300 MHz:50.72%, 600 MHz:0.48%, 1.20 GHz:14.18%  (43235)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 50.0 us.
  hardware limits: 200 MHz - 1.20 GHz
  available frequency steps: 200 MHz, 300 MHz, 600 MHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 200 MHz and 1.20 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 300 MHz.
  cpufreq stats: 200 MHz:34.62%, 300 MHz:50.72%, 600 MHz:0.48%, 1.20 GHz:14.18%  (43235)

 

Link to comment
Share on other sites

12 hours ago, ebin-dev said:

 

I have checked your settings 1200MHz / 200MHz with my system:

 

 

I flashed the u-boot with "flash-image-1g-1000_800_boot_sd_and_usb.bin" and burned a new image on the sd-card.

 

Now the scaling works for me also.

 

# cat /proc/version
Linux version 4.4.107-mvebu64 (root@xeon) (gcc version 6.4.1 20171012 (Linaro GCC 6.4-2017.11) ) #7 SMP PREEMPT Sat Dec 30 14:02:18 CET 2017

 

# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 50.0 us.
  hardware limits: 200 MHz - 1000 MHz
  available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 250 MHz and 1000 MHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 200 MHz:0.11%, 250 MHz:47.38%, 500 MHz:0.46%, 1000 MHz:52.06%  (10841)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0 1
  maximum transition latency: 50.0 us.
  hardware limits: 200 MHz - 1000 MHz
  available frequency steps: 200 MHz, 250 MHz, 500 MHz, 1000 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 250 MHz and 1000 MHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
  cpufreq stats: 200 MHz:0.11%, 250 MHz:47.38%, 500 MHz:0.46%, 1000 MHz:52.06%  (10841)

Link to comment
Share on other sites

17 hours ago, Patrick said:

Is there a way, a log file or so, to find the cause of the crash? 

 

Did you check the output of your console ? The last thing it should do is to display a kernel panic.

You could also check if the problem remains if you flash u-boot/atf with 800_800 MHz.

Link to comment
Share on other sites

3 hours ago, ebin-dev said:

 

Did you check the output of your console ? The last thing it should do is to display a kernel panic.

You could also check if the problem remains if you flash u-boot/atf with 800_800 MHz.

When I connect to the console when the ESPRESSObin has crashed, I only get an empty window.

For me it's only possible to see the console when my macbook is connected (and the cosole open) on a running ESPRESSObin.

Link to comment
Share on other sites

1 hour ago, Patrick said:

For me it's only possible to see the console when my macbook is connected (and the cosole open) on a running ESPRESSObin.

 

Please post any errors / kernel panics you observe this way (disconnect the Power supply from your MacBook !).

If you observe any kernel panics please flash u-boot/atf with 800_800 MHz and see if the issue remains.

Link to comment
Share on other sites

18 hours ago, ebin-dev said:

 

Please post any errors / kernel panics you observe this way (disconnect the Power supply from your MacBook !).

If you observe any kernel panics please flash u-boot/atf with 800_800 MHz and see if the issue remains.

I'm back to 1200_750 MHz and the crashes are gone.

So the 1000_800 MHz doesn't work for at this moment.

 

kr.,

Patrick

Link to comment
Share on other sites

7 hours ago, Patrick said:

I'm back to 1200_750 MHz and the crashes are gone.

So the 1000_800 MHz doesn't work for at this moment.

 

kr.,

Patrick

I found all the firmware with 800mhz ram speed is dodgy. It must be a marginal board layout issue of the ram won't run stable at its rated speed.

 

We just have to put up with lower memory bandwidth on a board that already wasn't all that fast (single channel 16 bit memory interface).

Isn't it similar to the first ever DDR PC's 15 years ago? They had 64 bit bus width, 200mhz.

Link to comment
Share on other sites

On 5-1-2018 at 6:34 PM, ebin-dev said:

 

Please post any errors / kernel panics you observe this way (disconnect the Power supply from your MacBook !).

If you observe any kernel panics please flash u-boot/atf with 800_800 MHz and see if the issue remains.

Sometimes I've got this kind of errors and the system doesn't respond anymore:

 

Message from syslogd@localhost at Jan 12 17:42:02 ...
 kernel:[39637.813868] Call trace:

Message from syslogd@localhost at Jan 12 17:42:02 ...
 kernel:[39637.822536] Call trace:

 

After a few minutes (approx. 10 or so), the system is running normal again.

 

 

kr.

Patrick

Link to comment
Share on other sites

I received some information from bootlin (formerly Free Electrons) - it was confirmed that support for the Marvell 3720 security engine is available in the crypto tree of 4.16-rc1 and that some known bugs will be fixed until the final release of 4.16. 

Not all algorithms available in the security engine are supported yet - but they are working on it ...

 

Quote

The driver currently supports:

Hashes: sha1, hmac(sha1), sha224, sha256.
Ciphers: ecb(aes), cbc(aes).

This allows to offload some IPsec connexions, depending on the
configuration, as these algs can be combined by the crypto layer.

More algs are coming, but I can't give you a schedule for them.

 

 

Link to comment
Share on other sites

6 hours ago, chrisf said:

I had a quick look over the diff for 4.16-rc1 and it looks like there's progress on support for DVFS too

Should this make the ESPRESSObin a bit more stable (les kernel panics)?

For now this thing is hardly useable for personal use with OMV4 installed (with Docker and Plex).

Link to comment
Share on other sites

USB/SATA installer with boot from SPI also works.
https://github.com/armbian/build/commit/69ccc04e88872b75bf6d70cc1e32cce483f3cf25
It's plan to move the board under stable ... but we need some help. With maintaining. Since our board count is huge, it already took days before all boards are tested (at major release), sometimes we skip certain and then Murphy law strikes :(

 

Roles are not strictly specified and nothing special is planed. We seek someone, who is up2date with development status, has a spare board for testing and is willing to update "known issues" or add specific tips for this board on the (new when ready) download page. Also, do testing when major updates are planned.

Any volunteers? :)

Link to comment
Share on other sites

I shall probably join the testers'  efforts as I've ordered a 2GB board for my project. Anyway, it is not delivered yet and I have no clues as for the board version and the memory frequency.

The install process will need to be discovered as well, as I understand it is not a simple image flash process. Extending your board bringing up instructions could be helpful. 

Link to comment
Share on other sites

and here is my 1st SPi log :

root@orangepiplus:~/bin# kermit kermit-usb0.conf 

Connecting to /dev/ttyUSB0, speed 115200
 Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(release):armada-17.06.2:a37c108
NOTICE:  BL1: Built : 14:31:03, Jul  5 2NOTICE:  BL2: v1.3(release):armada-17.06.2:a37c108
NOTICE:  BL2: Built : 14:31:04, Jul  5 20NOTICE:  BL31: v1.3(release):armada-17.06.2:a37c108
NOTICE:  BL31:

U-Boot 2017.03-armada-17.06.3-ga33ecb8 (Jul 05 2017 - 14:30:47 +0800)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  2 GiB
U-Boot DComphy-0: USB3          5 Gbps    
Comphy-1: PEX0          2.5 Gbps  
Comphy-2: SATA0         6 Gbps    
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs 
PCIE-0: Link down
MMC:   sdhci@d0000: 0
SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
Net:   eth0: neta@30000 [PRIME]
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
mmc_init: -95, time 41
MMC Device 0 not found
no mmc device at slot 0
Card did not respond to voltage select!
mmc_init: -95, time 23
** Bad device mmc 0 **
Card did not respond to voltage select!
mmc_init: -95, time 23
** Bad device mmc 0 **
Bad Linux ARM64 Image magic!
Marvell>> 
 

 

I can now experiment with Armbian  boot flash. Which file should I choose for now ?

Link to comment
Share on other sites

I've flashed the u-boot with 

Marvell>> bubt flash-image-2g-1000_800_boot_sd_and_usb.bin spi usb

 

Then I deployed the image to the USB flash, as I have no spare SD card.

dd if=Armbian_5.38_Espressobin_Debian_stretch_default_4.4.112.img of=/dev/sdb bs=1M oflag=direct 

 

Anyway, I was unable to boot from USB flash, despite that Armbian instructions claim , that "After updating your SPI flash with most recent "sd_and_usb" u-boot, you can boot from USB or SD card the exact same way."

 

----------------------------------------------------
SVC_REV:3
SVC_REV:3
NOTICE:  Booting Trusted Firmware
NOTICE:  BL1: v1.3(release):devel-17.08.1:627667b
NOTICE:  BL1: Built : 14:40:36, Oct  4 2NOTICE:  BL2: v1.3(release):devel-17.08.1:627667b
NOTICE:  BL2: Built : 14:40:36, Oct  4 2017
NNOTICE:  BL31: v1.3(release):devel-17.08.1:627667b
NOTICE:  BL31:

U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200)

Model: Marvell Armada 3720 Community Board ESPRESSOBin
       CPU    @ 1000 [MHz]
       L2     @ 800 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 800 [MHz]
DRAM:  2 GiB
U-Boot DT blob at : 000000007f7182d8
Comphy-0: USB3          5 Gbps    
Comphy-1: PEX0          2.5 Gbps  
Comphy-2: SATA0         6 Gbps    
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs 
PCIE-0: Link down
MMC:   sdhci@d0000: 0
SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

Net:   eth0: neta@30000 [PRIME]
Hit any key to stop autoboot:  0 
*** ERROR: `serverip' not set
*** ERROR: `serverip' not set
Bad Linux ARM64 Image magic!

 

 

Am I wrong somewhere ?

How could I boot from a USB flash?

 

I was able to successfully boot from USB both OpenWRT and Yocto from Espressobin site.

Link to comment
Share on other sites

If any bugs are necessary, I have raised some :

I am running a flash-image-2g-1000_800_boot_sd_and_usb.bin

The U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) shows a weird bad CRC (see the above log):

SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

 

I have finally been able booting with manual U-Boot settings :

 

setenv image_name boot/Image
setenv fdt_name boot/dtb/marvell/armada-3720-community.dtb

setenv rootdev "/dev/sda1"

setenv rootfstype "ext4"
setenv verbosity "1"

 

setenv bootusb 'usb reset; ext4load usb 0:1 $kernel_addr $image_name;ext4load usb 0:1 $initrd_addr $initrd_image;ext4load usb 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr - $fdt_addr'

 

run bootusb

 

[    0.185230] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.195207] futex hash table entries: 512 (order: 4, 65536 bytes)
[    0.202201] xor: measuring software checksum speed
[    0.246557]    8regs     :  1919.000 MB/sec
[    0.290588]    8regs_prefetch:  1711.000 MB/sec
[    0.334620]    32regs    :  2359.000 MB/sec
[    0.378655]    32regs_prefetch:  1983.000 MB/sec
[    0.383325] xor: using function: 32regs (2359.000 MB/sec)
[    0.388899] pinctrl core: initialized pinctrl subsystem
[    0.395208] NET: Registered protocol family 16
[    0.411752] cpuidle: using governor ladder
[    0.427920] cpuidle: using governor menu
[    0.432050] vdso: 2 pages (1 code @ ffffffc000db1000, 1 data @ ffffffc000db0000)
[    0.439616] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.448354] DMA: preallocated 2048 KiB pool for atomic allocations
[    0.454744] Serial: AMBA PL011 UART driver
[    0.460094] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 8, base_baud = 0) is a mvebu-uart
[    0.469000] console [ttyMV0] enabled
[    0.469000] console [ttyMV0] enabled
[    0.476342] bootconsole [uart0] disabled
[    0.476342] bootconsole [uart0] disabled

.......

[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Serial Getty on ttyMV0.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Authorization Manager.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Debian GNU/Linux 9 espressobin ttyMV0

espressobin login:

 

Before I was able logging in for the 1st time, the kernel raised an exception :

[  162.674661] Unable to handle kernel NULL pointer dereference at virtual address 000008f9
[  162.682875] pgd = ffffffc000e88000
[  162.686472] [000008f9] *pgd=0000000078406003, *pud=0000000078406003, *pmd=0000000078407003, *pte=00e80000d1d00707
[  162.697016] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[  162.702687] Modules linked in: bridge stp llc ip_tables x_tables
[  162.708996] CPU: 0 PID: 7 Comm: rcu_preempt Not tainted 4.4.112-mvebu64 #8
[  162.716193] Hardware name: Marvell Armada 3720 Community Board (DT)
[  162.722319] task: ffffffc07847c500 ti: ffffffc0784b8000 task.ti: ffffffc0784b8000
[  162.730069] PC is at update_blocked_averages+0x84/0x4c0
[  162.735911] LR is at update_blocked_averages+0x38/0x4c0
[  162.740961] pc : [<ffffffc0000e2624>] lr : [<ffffffc0000e25d8>] pstate: 200001c5
[  162.748880] sp : ffffffc0784bbbb0
[  162.751945] x29: ffffffc0784bbbb0 x28: ffffffc07efc2f00 
[  162.757709] x27: ffffffc07efc2f68 x26: 0000000000000000 
[  162.763202] x25: 0000000000000000 x24: ffffffc07847c970 
[  162.768695] x23: ffffffc0009e496c x22: 0000000000000000 
[  162.774188] x21: ffffffc000db2000 x20: ffffffc07efc2f00 
[  162.779679] x19: 00000000000001c0 x18: ffffffc000e38890 
[  162.785176] x17: 0000000000000001 x16: 0000000000000007 
[  162.790671] x15: 0000000000000000 x14: 0000000000000000 
[  162.796166] x13: 0000000000000000 x12: 0000000000000000 
[  162.801662] x11: 00000000afb50401 x10: afb504000afb5041 
[  162.807156] x9 : ffffffc000a00000 x8 : ffffffc000a00970 
[  162.812651] x7 : ffffffc07efc37a8 x6 : ffffffc077141e58 
[  162.818144] x5 : 000000000000009f x4 : ffffffc077b79c00 
[  162.823639] x3 : 0000000000000000 x2 : 00000025e029edb0 
[  162.829131] x1 : 0000000000000001 x0 : 0000000000000000 
[  162.834623] 
[  162.836335] Process rcu_preempt (pid: 7, stack limit = 0xffffffc0784b8020)
[  162.843274] Stack: (0xffffffc0784bbbb0 to 0xffffffc0784bc000)
[  162.848948] bba0:                                   ffffffc0784bbbe0 ffffffc0000e9668
[  162.857409] bbc0: 00000000ffff7ac7 ffffffc000d8c000 ffffffc0784bbbe0 ffffffc0000e9660
[  162.865511] bbe0: ffffffc0784bbc80 ffffffc0009e4434 ffffffc07efc2f00 ffffffc000d8c000
[  162.873615] bc00: ffffffc000db2000 ffffffc07847c500 ffffffc0009e496c ffffffc07847c970
[  162.881626] bc20: 0000000000000000 0000000000000000 0000000000000001 0000000000000001
[  162.889909] bc40: ffffffc07efc2f00 ffffffc07efc2f68 ffffffc000a00820 ffffffc07847c500
[  162.897930] bc60: 000000017efc2f00 00000000ffff79ce 00000001009e496c ffffffc07847c500
[  162.906124] bc80: ffffffc0784bbcd0 ffffffc0009e496c ffffffc0784b8000 ffffffc0784bbd50
[  162.914235] bca0: ffffffc000db2000 00000000ffff79ce ffffffc07efbeb80 ffffffc0784bbd80
[  162.922345] bcc0: 0000000000000003 0000000000000000 ffffffc0784bbcf0 ffffffc0009e75a8
[  162.930276] bce0: ffffffc07efbeb80 ffffffc0009e75a4 ffffffc0784bbd80 ffffffc000107728
[  162.938469] bd00: ffffffc000dc8800 ffffffc000dc8b20 ffffffc000db2000 0000000000000001
[  162.946482] bd20: ffffffc000dc8000 ffffffc000106910 ffffffc07efc3d80 ffffffc000dc8800
[  162.954673] bd40: ffffffc0784bbd50 0000000000000140 0000000000000000 ffffffc07efbf228
[  162.962867] bd60: 00000000ffff79ce ffffffc00010ac20 ffffffc07847c500 ffffffff00000000
[  162.970795] bd80: ffffffc0784bbe20 ffffffc0000d3250 ffffffc07842e080 ffffffc000e44058
[  162.979076] bda0: ffffffc000c2af10 ffffffc000dc8800 ffffffc0001071c8 0000000000000000
[  162.987095] bdc0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  162.995109] bde0: ffffffc0784b8000 0000028000000000 00ffffc0784bbe20 ffffffc000000000
[  163.003392] be00: ffffffc07847c500 ffffffc0000ef6e8 ffffffc000dc8b28 ffffffc000dc8b28
[  163.011411] be20: 0000000000000000 ffffffc000085dd0 ffffffc0000d3158 ffffffc07842e080
[  163.019603] be40: 0000000000000000 0000000000000000 0000000000000000 ffffffc0000dc438
[  163.027622] be60: ffffffc0000d3158 0000000000000000 0000000000000000 ffffffc000dc8800
[  163.035726] be80: 0000000000000000 0000000000000000 ffffffc0784bbe90 ffffffc0784bbe90
[  163.043738] bea0: 0000000000000000 ffffffc000000000 ffffffc0784bbeb0 ffffffc0784bbeb0
[  163.051929] bec0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.060032] bee0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.068046] bf00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.076326] bf20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.084257] bf40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.092181] bf60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.100460] bf80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.108654] bfa0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.116757] bfc0: 0000000000000000 0000000000000005 0000000000000000 0000000000000000
[  163.124861] bfe0: 0000000000000000 0000000000000000 5555555555555555 5555555555555555
[  163.133049] Call trace:
[  163.135579] [<ffffffc0000e2624>] update_blocked_averages+0x84/0x4c0
[  163.141621] [<ffffffc0000e9668>] pick_next_task_fair+0x240/0x520
[  163.148104] [<ffffffc0009e4434>] __schedule+0xe4/0x5d8
[  163.153323] [<ffffffc0009e496c>] schedule+0x44/0xb8
[  163.158456] [<ffffffc0009e75a8>] schedule_timeout+0x100/0x1a8
[  163.164489] [<ffffffc000107728>] rcu_gp_kthread+0x560/0x818
[  163.170160] [<ffffffc0000d3250>] kthread+0xf8/0x110
[  163.174933] [<ffffffc000085dd0>] ret_from_fork+0x10/0x40
[  163.180783] Code: b9411c80 35001900 f9406081 f9408880 (f9447c22) 
 

 

How could a USB boot be automated ?

Does this kernel panic come from a 800 Mhz ram setting ?

Link to comment
Share on other sites

15 minutes ago, y52 said:

If any bugs are necessary, I have raised some :

I am running a flash-image-2g-1000_800_boot_sd_and_usb.bin

The U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) shows a weird bad CRC (see the above log):

SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

 

I have finally been able booting with manual U-Boot settings :

 

setenv image_name boot/Image
setenv fdt_name boot/dtb/marvell/armada-3720-community.dtb

setenv rootdev "/dev/sda1"

setenv rootfstype "ext4"
setenv verbosity "1"

 

setenv bootusb 'usb reset; ext4load usb 0:1 $kernel_addr $image_name;ext4load usb 0:1 $initrd_addr $initrd_image;ext4load usb 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr - $fdt_addr'

 

run bootusb

 

[    0.185230] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.195207] futex hash table entries: 512 (order: 4, 65536 bytes)
[    0.202201] xor: measuring software checksum speed
[    0.246557]    8regs     :  1919.000 MB/sec
[    0.290588]    8regs_prefetch:  1711.000 MB/sec
[    0.334620]    32regs    :  2359.000 MB/sec
[    0.378655]    32regs_prefetch:  1983.000 MB/sec
[    0.383325] xor: using function: 32regs (2359.000 MB/sec)
[    0.388899] pinctrl core: initialized pinctrl subsystem
[    0.395208] NET: Registered protocol family 16
[    0.411752] cpuidle: using governor ladder
[    0.427920] cpuidle: using governor menu
[    0.432050] vdso: 2 pages (1 code @ ffffffc000db1000, 1 data @ ffffffc000db0000)
[    0.439616] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.448354] DMA: preallocated 2048 KiB pool for atomic allocations
[    0.454744] Serial: AMBA PL011 UART driver
[    0.460094] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 8, base_baud = 0) is a mvebu-uart
[    0.469000] console [ttyMV0] enabled
[    0.469000] console [ttyMV0] enabled
[    0.476342] bootconsole [uart0] disabled
[    0.476342] bootconsole [uart0] disabled

.......

[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Serial Getty on ttyMV0.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Authorization Manager.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Debian GNU/Linux 9 espressobin ttyMV0

espressobin login:

 

Before I was able logging in for the 1st time, the kernel raised an exception :

[  162.674661] Unable to handle kernel NULL pointer dereference at virtual address 000008f9
[  162.682875] pgd = ffffffc000e88000
[  162.686472] [000008f9] *pgd=0000000078406003, *pud=0000000078406003, *pmd=0000000078407003, *pte=00e80000d1d00707
[  162.697016] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[  162.702687] Modules linked in: bridge stp llc ip_tables x_tables
[  162.708996] CPU: 0 PID: 7 Comm: rcu_preempt Not tainted 4.4.112-mvebu64 #8
[  162.716193] Hardware name: Marvell Armada 3720 Community Board (DT)
[  162.722319] task: ffffffc07847c500 ti: ffffffc0784b8000 task.ti: ffffffc0784b8000
[  162.730069] PC is at update_blocked_averages+0x84/0x4c0
[  162.735911] LR is at update_blocked_averages+0x38/0x4c0
[  162.740961] pc : [<ffffffc0000e2624>] lr : [<ffffffc0000e25d8>] pstate: 200001c5
[  162.748880] sp : ffffffc0784bbbb0
[  162.751945] x29: ffffffc0784bbbb0 x28: ffffffc07efc2f00 
[  162.757709] x27: ffffffc07efc2f68 x26: 0000000000000000 
[  162.763202] x25: 0000000000000000 x24: ffffffc07847c970 
[  162.768695] x23: ffffffc0009e496c x22: 0000000000000000 
[  162.774188] x21: ffffffc000db2000 x20: ffffffc07efc2f00 
[  162.779679] x19: 00000000000001c0 x18: ffffffc000e38890 
[  162.785176] x17: 0000000000000001 x16: 0000000000000007 
[  162.790671] x15: 0000000000000000 x14: 0000000000000000 
[  162.796166] x13: 0000000000000000 x12: 0000000000000000 
[  162.801662] x11: 00000000afb50401 x10: afb504000afb5041 
[  162.807156] x9 : ffffffc000a00000 x8 : ffffffc000a00970 
[  162.812651] x7 : ffffffc07efc37a8 x6 : ffffffc077141e58 
[  162.818144] x5 : 000000000000009f x4 : ffffffc077b79c00 
[  162.823639] x3 : 0000000000000000 x2 : 00000025e029edb0 
[  162.829131] x1 : 0000000000000001 x0 : 0000000000000000 
[  162.834623] 
[  162.836335] Process rcu_preempt (pid: 7, stack limit = 0xffffffc0784b8020)
[  162.843274] Stack: (0xffffffc0784bbbb0 to 0xffffffc0784bc000)
[  162.848948] bba0:                                   ffffffc0784bbbe0 ffffffc0000e9668
[  162.857409] bbc0: 00000000ffff7ac7 ffffffc000d8c000 ffffffc0784bbbe0 ffffffc0000e9660
[  162.865511] bbe0: ffffffc0784bbc80 ffffffc0009e4434 ffffffc07efc2f00 ffffffc000d8c000
[  162.873615] bc00: ffffffc000db2000 ffffffc07847c500 ffffffc0009e496c ffffffc07847c970
[  162.881626] bc20: 0000000000000000 0000000000000000 0000000000000001 0000000000000001
[  162.889909] bc40: ffffffc07efc2f00 ffffffc07efc2f68 ffffffc000a00820 ffffffc07847c500
[  162.897930] bc60: 000000017efc2f00 00000000ffff79ce 00000001009e496c ffffffc07847c500
[  162.906124] bc80: ffffffc0784bbcd0 ffffffc0009e496c ffffffc0784b8000 ffffffc0784bbd50
[  162.914235] bca0: ffffffc000db2000 00000000ffff79ce ffffffc07efbeb80 ffffffc0784bbd80
[  162.922345] bcc0: 0000000000000003 0000000000000000 ffffffc0784bbcf0 ffffffc0009e75a8
[  162.930276] bce0: ffffffc07efbeb80 ffffffc0009e75a4 ffffffc0784bbd80 ffffffc000107728
[  162.938469] bd00: ffffffc000dc8800 ffffffc000dc8b20 ffffffc000db2000 0000000000000001
[  162.946482] bd20: ffffffc000dc8000 ffffffc000106910 ffffffc07efc3d80 ffffffc000dc8800
[  162.954673] bd40: ffffffc0784bbd50 0000000000000140 0000000000000000 ffffffc07efbf228
[  162.962867] bd60: 00000000ffff79ce ffffffc00010ac20 ffffffc07847c500 ffffffff00000000
[  162.970795] bd80: ffffffc0784bbe20 ffffffc0000d3250 ffffffc07842e080 ffffffc000e44058
[  162.979076] bda0: ffffffc000c2af10 ffffffc000dc8800 ffffffc0001071c8 0000000000000000
[  162.987095] bdc0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  162.995109] bde0: ffffffc0784b8000 0000028000000000 00ffffc0784bbe20 ffffffc000000000
[  163.003392] be00: ffffffc07847c500 ffffffc0000ef6e8 ffffffc000dc8b28 ffffffc000dc8b28
[  163.011411] be20: 0000000000000000 ffffffc000085dd0 ffffffc0000d3158 ffffffc07842e080
[  163.019603] be40: 0000000000000000 0000000000000000 0000000000000000 ffffffc0000dc438
[  163.027622] be60: ffffffc0000d3158 0000000000000000 0000000000000000 ffffffc000dc8800
[  163.035726] be80: 0000000000000000 0000000000000000 ffffffc0784bbe90 ffffffc0784bbe90
[  163.043738] bea0: 0000000000000000 ffffffc000000000 ffffffc0784bbeb0 ffffffc0784bbeb0
[  163.051929] bec0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.060032] bee0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.068046] bf00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.076326] bf20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.084257] bf40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.092181] bf60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.100460] bf80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.108654] bfa0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[  163.116757] bfc0: 0000000000000000 0000000000000005 0000000000000000 0000000000000000
[  163.124861] bfe0: 0000000000000000 0000000000000000 5555555555555555 5555555555555555
[  163.133049] Call trace:
[  163.135579] [<ffffffc0000e2624>] update_blocked_averages+0x84/0x4c0
[  163.141621] [<ffffffc0000e9668>] pick_next_task_fair+0x240/0x520
[  163.148104] [<ffffffc0009e4434>] __schedule+0xe4/0x5d8
[  163.153323] [<ffffffc0009e496c>] schedule+0x44/0xb8
[  163.158456] [<ffffffc0009e75a8>] schedule_timeout+0x100/0x1a8
[  163.164489] [<ffffffc000107728>] rcu_gp_kthread+0x560/0x818
[  163.170160] [<ffffffc0000d3250>] kthread+0xf8/0x110
[  163.174933] [<ffffffc000085dd0>] ret_from_fork+0x10/0x40
[  163.180783] Code: b9411c80 35001900 f9406081 f9408880 (f9447c22) 
 

 

How could a USB boot be automated ?

Does this kernel panic come from a 800 Mhz ram setting ?

 Switch to the 1200/750 firmware and try again

Link to comment
Share on other sites

I had the firmware 1200/750 running but almost every day I had a kernel panic. I switched over to 1000/800 and had kernel panics every hour or so.

Then I changed the governor from " ondemand" to "conservative" and now I have an up-time of 5 days :)

 

kr.,

Patrick

Link to comment
Share on other sites

2 minutes ago, y52 said:

Where is the governor setting set or changed ?

 

This kernel instability was not observed on Yocto and Openwrt distributions provided by Espressobin. Does Armbian build creates one?

I changed the settings in

 

/etc/init.d/cpufrequtils

and

/etc/default/cpufrequtils

Link to comment
Share on other sites

I believe you changed this setting before booting the system?

Anyway, a 5 days uptime is not a high record for a presumably router application, where high availability is required.

 

How could I boot from USB without manual  startup ?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines