15 15
lanefu

Espressobin support development efforts

Recommended Posts

Any idea why the the mPCIe is not initalizing

 

00:00.0 Ethernet controller [0200]: Qualcomm Atheros Device [168c:abcd] (rev 01)

 

In uboot it shows fine

 

Marvell>> pci init
Scanning PCI devices on bus 0
BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
00.00.00   0x168c     0x0030     Network controller      0x80

I also booted it with the ExpressoBin kernel from their website and it seemed to come up right

 

what could this be?

Share this post


Link to post
Share on other sites

Hello!

 

I have EspressoBin board and I have two different wifi cards. I used Debian mainline from https://www.armbian.com/espressobin/ 

 

For first wifi:

00:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter

I have following error in dmesg:

dmesg|grep ath9k
[    6.565634] ath9k 0000:00:00.0: enabling device (0000 -> 0002)
[    6.565774] ath9k 0000:00:00.0: request_irq failed
[    6.565823] ath9k: probe of 0000:00:00.0 failed with error -22

For another card:

00:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)

I have big kernel error:

[    5.849460] Internal error: : 96000010 [#1] PREEMPT SMP
[    5.854697] Modules linked in: ath5k(+) ath mac80211 cfg80211 rfkill bridge stp llc ip_tables x_tables
[    5.864151] CPU: 1 PID: 353 Comm: systemd-udevd Not tainted 4.14.14-mvebu64 #5
[    5.871883] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[    5.878633] task: ffffffc07a5a8000 task.stack: ffffff8009f08000
[    5.884730] PC is at ath5k_hw_read_srev+0xc/0x28 [ath5k]
[    5.890207] LR is at ath5k_hw_init+0x64/0x758 [ath5k]
[    5.895291] pc : [<ffffff8000c03884>] lr : [<ffffff8000bfc4bc>] pstate: 20000145
[    5.902760] sp : ffffff8009f0b980
[    5.906537] x29: ffffff8009f0b980 x28: ffffff800a108000 
[    5.911769] x27: ffffff8000c0d450 x26: 00000000014000c0 
[    5.917169] x25: ffffffc07b176560 x24: ffffffc07ad7b800 
[    5.922659] x23: ffffffc07b177560 x22: ffffff8000c0a1a8 
[    5.928418] x21: ffffff800a140000 x20: ffffffc07b175560 
[    5.933820] x19: ffffffc07b171560 x18: 0000000000000001 
[    5.939041] x17: 0000007f84f172f0 x16: ffffff8008224b48 
[    5.944618] x15: ffffffffffffffff x14: 0000000000000000 
[    5.950377] x13: ff00000000000000 x12: 0000000000000018 
[    5.955777] x11: 0101010101010101 x10: ffffffff7f7f7f7f 
[    5.961177] x9 : 0000000000000009 x8 : 0000000000000000 
[    5.966849] x7 : 000000000000401c x6 : 0000000000004020 
[    5.972161] x5 : ffffff8008e37000 x4 : 0000000000000704 
[    5.977653] x3 : 0000000000000003 x2 : 0000000000004020 
[    5.983411] x1 : ffffff800a144020 x0 : ffffffc07b171560 
[    5.988465] Process systemd-udevd (pid: 353, stack limit = 0xffffff8009f08000)
[    5.996294] Call trace:
[    5.998909] Exception stack(0xffffff8009f0b840 to 0xffffff8009f0b980)
[    6.005580] b840: ffffffc07b171560 ffffff800a144020 0000000000004020 0000000000000003
[    6.013419] b860: 0000000000000704 ffffff8008e37000 0000000000004020 000000000000401c
[    6.021699] b880: 0000000000000000 0000000000000009 ffffffff7f7f7f7f 0101010101010101
[    6.029801] b8a0: 0000000000000018 ff00000000000000 0000000000000000 ffffffffffffffff
[    6.037904] b8c0: ffffff8008224b48 0000007f84f172f0 0000000000000001 ffffffc07b171560
[    6.045914] b8e0: ffffffc07b175560 ffffff800a140000 ffffff8000c0a1a8 ffffffc07b177560
[    6.054016] b900: ffffffc07ad7b800 ffffffc07b176560 00000000014000c0 ffffff8000c0d450
[    6.062294] b920: ffffff800a108000 ffffff8009f0b980 ffffff8000bfc4bc ffffff8009f0b980
[    6.070313] b940: ffffff8000c03884 0000000020000145 ffffff800a140000 ffffff8000c0a1a8
[    6.078236] b960: 0000008000000000 ffffff8000c0aaa0 ffffff8009f0b980 ffffff8000c03884
[    6.086473] [<ffffff8000c03884>] ath5k_hw_read_srev+0xc/0x28 [ath5k]
[    6.092945] [<ffffff8000c00144>] ath5k_init_ah+0x154/0xd40 [ath5k]
[    6.099244] [<ffffff8000c03798>] ath5k_pci_probe+0x198/0x278 [ath5k]
[    6.105871] [<ffffff800855ca54>] local_pci_probe+0x3c/0xb0
[    6.111354] [<ffffff800855e040>] pci_device_probe+0xd0/0x158
[    6.117474] [<ffffff800864986c>] driver_probe_device+0x22c/0x2d8
[    6.123771] [<ffffff80086499d0>] __driver_attach+0xb8/0xc0
[    6.129172] [<ffffff8008647a14>] bus_for_each_dev+0x4c/0x98
[    6.135111] [<ffffff8008649170>] driver_attach+0x20/0x28
[    6.140331] [<ffffff8008648cdc>] bus_add_driver+0x1ac/0x218
[    6.146541] [<ffffff800864a358>] driver_register+0x60/0xf8
[    6.151861] [<ffffff800855c238>] __pci_register_driver+0x40/0x48
[    6.158291] [<ffffff8000c16018>] ath5k_pci_driver_init+0x18/0x1000 [ath5k]
[    6.165096] [<ffffff8008083980>] do_one_initcall+0x38/0x120
[    6.170942] [<ffffff800814ab68>] do_init_module+0x58/0x1b0
[    6.176879] [<ffffff8008149824>] load_module+0x1a3c/0x2180
[    6.182551] [<ffffff800814a1b4>] SyS_finit_module+0xa4/0xb8
[    6.188040] Exception stack(0xffffff8009f0bec0 to 0xffffff8009f0c000)
[    6.194969] bec0: 0000000000000012 0000007f99f677b8 0000000000000000 0000000000000012
[    6.202889] bee0: 0000000000000000 00000055c1921d48 0000000000000041 0000000000000041
[    6.210722] bf00: 0000000000000111 0000007fc5ce90d0 0000000000000000 0000000000000020
[    6.219358] bf20: 0000000000000000 0000000000000000 0000000000000004 0000000000000000
[    6.227376] bf40: 0000007f99f79f88 0000007f99e71790 0000000000000000 00000055c1921ce0
[    6.235566] bf60: 0000007f99f677b8 0000000000000000 00000055c19190c0 0000000000020000
[    6.243674] bf80: 0000000000000000 0000000000000000 0000000000000000 0000000000020000
[    6.251424] bfa0: 0000007fc5cea320 0000007fc5cea190 0000007f99f60d74 0000007fc5cea190
[    6.259882] bfc0: 0000007f99e717b4 0000000040000000 0000000000000012 0000000000000111
[    6.267630] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[    6.276091] [<ffffff8008083808>] __sys_trace_return+0x0/0x4
[    6.281860] Code: ffffff80 f9411801 d2880402 8b020021 (b9400021) 
[    6.288081] ---[ end trace b63085356c332b53 ]---
[    6.336127] mvneta d0030000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    6.351844] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.438530] mv88e6085 d0032004.mdio-mii:01 lan1: Link is Down

Kernel:

uname -a
Linux espressobin 4.14.14-mvebu64 #5 SMP PREEMPT Thu Jan 25 16:25:11 CET 2018 aarch64 GNU/Linux

Any ideas about ways to fix them? :( 

Share this post


Link to post
Share on other sites

Also, I noticed significant amount of "do_csum.part.0" in perf top output and hardware checksum offload does not work on mvneta:

 

ethtool -K eth0 rx on
Cannot get device udp-fragmentation-offload settings: Operation not supported
Cannot change rx-checksumming
Cannot get device udp-fragmentation-offload settings: Operation not supported
Could not change any device features

I collected this output with about 8Mbits of incoming UDP traffic. 

Screen Shot 2018-05-04 at 00.00.18.png

Also, this patch https://github.com/torvalds/linux/commit/ca5902a6547f662419689ca28b3c29a772446caa#diff-851bfc43b3ca32355b4c07d29dbba7f0 can offer some nice benefits and spread traffic processing to multiple queues. 

Share this post


Link to post
Share on other sites
7 hours ago, Pavel Odintsov said:

Looks like 4.16 kernel has number of nice features for EspressoBin (cpu scaling, crypto). Do you have any plans to offer builds on this kernel?


We do provide 4.16.7
 

armbian-config -> system
1. Change to the beta repository

2. Switch to alternative kernels, choose DEV

 

6 hours ago, Pavel Odintsov said:

Also, this patch


Is included in DEV and NEXT. At least those in yesterdays build.
 

Share this post


Link to post
Share on other sites

For me, there is no beta repository in armbian-config - system menu.

I can just switch back to the stable builds.

If that means that I have DEV repository, why am I still on 4.4.129?

uname -a
Linux espressobin 4.4.129-mvebu64 #5 SMP PREEMPT Sat Apr 28 08:55:21 CEST 2018 aarch64 GNU/Linux

 

Share this post


Link to post
Share on other sites
19 minutes ago, tom_i said:

For me, there is no beta repository in armbian-config - system menu.


Sorry.

"Nightly" "Switch to nightly automated builds"

 

is a proper term.

Share this post


Link to post
Share on other sites

Hmm.. strange, I don't have this option there :-/

Just:

Freeze    Disable kernel upgrades 
Stable    Switch to stable builds 
Lowlevel  Stop low-level messages on console  
Bootenv   Edit boot environment  
SSH       Reconfigure SSH daemon  
Firmware  Run apt update & apt upgrade 
Desktop   Install desktop

 

Share this post


Link to post
Share on other sites
9 minutes ago, tom_i said:

Hmm.. strange, I don't have this option there :-/

 

You are already on beta ... run update, reboot and you should see "Switch" "Switch to alternative kernels" there.


Edit:

I just tested switching and it works fine, logs: http://ix.io/19ob

| ____|___ _ __  _ __ ___  ___ ___  ___ | |__ (_)_ __  
|  _| / __| '_ \| '__/ _ \/ __/ __|/ _ \| '_ \| | '_ \ 
| |___\__ \ |_) | | |  __/\__ \__ \ (_) | |_) | | | | |
|_____|___/ .__/|_|  \___||___/___/\___/|_.__/|_|_| |_|
          |_|                                          

Welcome to ARMBIAN 5.43.180428 nightly Ubuntu 18.04 LTS 4.16.5-mvebu64   
System load:   0.18 0.30 0.13   Up time:       3 min
Memory usage:  6 % of 993MB     IP:            172.16.100.189
Usage of /:    8% of 15G    

[ 0 security updates available, 1 updates total: apt upgrade ]
Last check: 2018-05-04 08:36

Last login: Fri May  4 08:36:52 2018 from 172.16.100.175

 

Share this post


Link to post
Share on other sites

@Igor thank you so much! It works fine!

ssh flab2
 _____                                   _     _       
| ____|___ _ __  _ __ ___  ___ ___  ___ | |__ (_)_ __  
|  _| / __| '_ \| '__/ _ \/ __/ __|/ _ \| '_ \| | '_ \ 
| |___\__ \ |_) | | |  __/\__ \__ \ (_) | |_) | | | | |
|_____|___/ .__/|_|  \___||___/___/\___/|_.__/|_|_| |_|
          |_|                                          

Welcome to ARMBIAN 5.43.180428 nightly Ubuntu 16.04.4 LTS 4.16.5-mvebu64   
System load:   1.88 0.42 0.14  	Up time:       0 min		
Memory usage:  5 % of 2001MB 	IP:            192.168.1.11
Usage of /:    30% of 15G    	

New to Armbian? Check the documentation first: https://docs.armbian.com
Last login: Fri May  4 08:54:07 2018 from 192.168.1.4

root@espressobin:~# uname -r
4.16.5-mvebu64

But I still see "do_csum.part.0" in perf top. Looks like network card has some issues with checksum offload. What is the best way to report this issue to Marvell? 

 

Screen Shot 2018-05-04 at 10.09.23.png

Share this post


Link to post
Share on other sites
39 minutes ago, Igor said:

 

You are already on beta ... run update, reboot and you should see "Switch" "Switch to alternative kernels" there.


Edit:

I just tested switching and it works fine, logs: http://ix.io/19ob


| ____|___ _ __  _ __ ___  ___ ___  ___ | |__ (_)_ __  
|  _| / __| '_ \| '__/ _ \/ __/ __|/ _ \| '_ \| | '_ \ 
| |___\__ \ |_) | | |  __/\__ \__ \ (_) | |_) | | | | |
|_____|___/ .__/|_|  \___||___/___/\___/|_.__/|_|_| |_|
          |_|                                          

Welcome to ARMBIAN 5.43.180428 nightly Ubuntu 18.04 LTS 4.16.5-mvebu64   
System load:   0.18 0.30 0.13   Up time:       3 min
Memory usage:  6 % of 993MB     IP:            172.16.100.189
Usage of /:    8% of 15G    

[ 0 security updates available, 1 updates total: apt upgrade ]
Last check: 2018-05-04 08:36

Last login: Fri May  4 08:36:52 2018 from 172.16.100.175

 

Aha, Ubuntu that's the reason :-/

I'm on Debian:

espressobin:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster

Welcome to ARMBIAN 5.43.180428 nightly Debian GNU/Linux buster/sid 4.4.129-mvebu64 

Share this post


Link to post
Share on other sites

Hi,

 

Is there any chance of getting a 4.17(-rc) kernel on the espressobin to test the new ptp support? Compiling it myself ends up in an error in the pci patches. once removed it fails when building the deb package (linux-headers-dev-mvebu64 not in control info)

 

Best,

schuschu

Share this post


Link to post
Share on other sites
On 5/9/2018 at 11:27 AM, schuschu said:

Hi,

 

Is there any chance of getting a 4.17(-rc) kernel on the espressobin to test the new ptp support? Compiling it myself ends up in an error in the pci patches. once removed it fails when building the deb package (linux-headers-dev-mvebu64 not in control info)

 

Best,

schuschu

You may try https://github.com/ioft/linux/tree/master with this config https://github.com/ioft/linux/blob/master/arch/arm64/configs/mvebu_v8_lsp_defconfig . It might be the case that ptp support isn't enabled by default.

Share this post


Link to post
Share on other sites
45 minutes ago, ebin-dev said:

@Igor has pushed a new message on Twitter related to EspressoBin:

 

EspressoBin firmware images were updated to:

 

u-boot-2017.03 release armada-17.10.3

A3700_utils release armada-17.10.5

atf-v1.3 release armada-17.10.8

 

(see log) and updated stable Stretch, Xenial and preview Bionic images are available.

 

Thank you, works like a charm.  

Share this post


Link to post
Share on other sites
On 5/10/2018 at 9:00 PM, ebin-dev said:

@Igor has pushed a new message on Twitter related to EspressoBin:

 

EspressoBin firmware images were updated to:

 

u-boot-2017.03 release armada-17.10.3

A3700_utils release armada-17.10.5

atf-v1.3 release armada-17.10.8

 

(see log) and updated stable Stretch, Xenial and preview Bionic images are available.

 

Has the Armbian versions naming been changed?

Initially I've setup the Armbian_5.38_Espressobin_Debian_stretch_default_4.4.112

 

The https://www.armbian.com/espressobin/ page doesn't show  a 4.4. tree any more.

Only the mainline kernel 4.14.y seems to be available now.

 

My current installation is running (after the apt upgrade) the 4.4.x kernel 

root@espressobin:/mnt/sda1/Distr# uname -a
Linux espressobin 4.4.131-mvebu64 #6 SMP PREEMPT Thu May 10 18:08:13 CEST 2018 aarch64 GNU/Linux

 

Will the mainline kernel 4.14.y downgrade the system ?

Could somebody clarify it?

Share this post


Link to post
Share on other sites
14 minutes ago, y52 said:

My current installation is running (after the apt upgrade) the 4.4.x kernel 

root@espressobin:/mnt/sda1/Distr# uname -a
Linux espressobin 4.4.131-mvebu64 #6 SMP PREEMPT Thu May 10 18:08:13 CEST 2018 aarch64 GNU/Linux

 

Will the mainline kernel 4.14.y downgrade the system ?

Could somebody clarify it?

 

the Kernel 4.4 isnt 4.40 - so 14 for kernel 4.14 is greater than 4 for kernel 4.4

So it should be a  up-grade from 4.4 to 4.14 - as Iam reading the versions numbers right :) 

Share this post


Link to post
Share on other sites
7 minutes ago, guidol said:

 

the Kernel 4.4 isnt 4.40 - so 14 for kernel 4.14 is greater than 4 for kernel 4.4

So it should be a  up-grade from 4.4 to 4.14 - as Iam reading the versions numbers right :) 

It is rather confusing.

Which kernel version does the "Armbian_5.44_Espressobin_Debian_stretch_next_4.14.40.img" provide for?

Could somebody post a "uname -a" ?

Share this post


Link to post
Share on other sites
46 minutes ago, y52 said:

Only the mainline kernel 4.14.y seems to be available now.


We promote 4.14.y simply because it is a better choice now. Click on area rounded with red color ... to see other (older) choices.

 

image.png
 

Share this post


Link to post
Share on other sites
20 minutes ago, y52 said:

It is rather confusing.

Which kernel version does the "Armbian_5.44_Espressobin_Debian_stretch_next_4.14.40.img" provide for?

 


What is consing? You have a kernel version in a filename. 


"default" = old kernel, which is 4.4.something for this board

"next" = new kernel, which is 4.14.something for this board

 

If you want to upgrade your default 4.4 to 4.14 you need to switch branches. Manually or with armbian-config.

Share this post


Link to post
Share on other sites
21 minutes ago, Igor said:


What is consing? You have a kernel version in a filename. 

Thanks Igor, That's what I thought as well. The previous participant's answer was confusing. 

I believe it would be difficult for me downgrading now from 4.4 kernel to 4.14.

Which areas does the 4.14 perform better compared to 4.4 to evaluate future uses ?

1 hour ago, y52 said:

EspressoBin firmware images were updated to:

 

u-boot-2017.03 release armada-17.10.3

A3700_utils release armada-17.10.5

atf-v1.3 release armada-17.10.8

Thanks for updating the U-boot as well.

Has the DTB been changed at the same time?

After # apt upgrade the DTB files were changed as follows :

# ls -al dtb/marvell/armada-37*
-rw-r--r-- 1 root root 12011 May 10 18:09 dtb/marvell/armada-3720-community.dtb
-rw-r--r-- 1 root root 12891 May 10 18:09 dtb/marvell/armada-3720-db-B.dtb
-rw-r--r-- 1 root root 12861 May 10 18:09 dtb/marvell/armada-3720-db-C.dtb
-rw-r--r-- 1 root root 12727 May 10 18:09 dtb/marvell/armada-3720-db.dtb
-rw-r--r-- 1 root root 12064 May 10 18:09 dtb/marvell/armada-37x0-customer.dtb

 

Which board version is the "armada-3720-community.dtb" intended for?

My v.5_0 board stucks shortly after OS booting with this DTB .  

It works stable with another one "armada-3720-community-v5.dtb", provided by GlobalScale. It's a bit troublesome.

Share this post


Link to post
Share on other sites
5 minutes ago, y52 said:

Has the DTB been changed at the same time?


If you use our build and you upgrade/change kernel via armbian-config you don't need to worry about that. https://github.com/armbian/build/blob/development/config/bootscripts/boot-espressobin.cmd#L22-L23

 

Mainline uses different DT name (armada-3720- espressobin.dtb) and it could be aligned once but now is as is. 

 

8 minutes ago, y52 said:

Which areas does the 4.14 perform better compared to 4.4 to evaluate future uses ?


Mainline kernels have much higher quality standards than vendor kernels which are usually full of dirty tricks and quick patches. Usually, vendor kernels have more special advantages but I think there are no more reasons (advantages) to stay on a kernel 4.4.y anymore.

Share this post


Link to post
Share on other sites
13 minutes ago, y52 said:

I believe it would be difficult for me downgrading now from 4.4 kernel to 4.14.

 

it isnt a downgrade, because you "could/should" read the 4.4 as "4.04" in compare to "4.14" - so the 14 is greater than the pure 4.
the 4 isnt a 4.40.x

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
15 15