Reply To: Issues with mainline (4.12-rc7)

[dingbatca]

Running into many of the same issues. I have tried the mainline 4.12.0 and 4.12.1. Just found the above mention kernel tree. Moved over to the new 4.12.0 tree, recompile, install…

I was able to debug the boot from mmc on the 4.12.1 issue and found that the sdhc support was not able to be compiled in. Only option was a module. Gave up on that and moved over to boot from SATA, which works fine in mainline.

With the new kernel (4.12.0). These are the current issues I am seeing:

CPUFreq not working. Might have missed a module in my kernel compile.

root@espressobin:/lib/modules/4.12.0/kernel/drivers/cpufreq# ls
arm_big_little.ko     cpufreq-dt.ko            cpufreq_powersave.ko
arm_big_little_dt.ko  cpufreq_conservative.ko  cpufreq_userspace.ko
cppc_cpufreq.ko       cpufreq_ondemand.ko      qoriq-cpufreq.ko
root@espressobin:/lib/modules/4.12.0/kernel/drivers/cpufreq# lsmod | grep freq
cpufreq_dt             16384  0
cpufreq_userspace      16384  0
cpufreq_conservative    16384  0
cpufreq_ondemand       20480  0
cpufreq_powersave      16384  0

XOR raid engine crashing:

root@espressobin:/test# [  175.677321] md: recovery of RAID array md0
[  175.689895] mv_xor d0060900.xor: error on chan 0. intr cause 0x00000202
[  175.696561] mv_xor d0060900.xor: config       0x00008447
[  175.701860] mv_xor d0060900.xor: activation   0x00000000
[  175.707252] mv_xor d0060900.xor: intr cause   0x00000202
[  175.713002] mv_xor d0060900.xor: intr mask    0x03f703f7
[  175.718215] mv_xor d0060900.xor: error cause  0x00000000
[  175.723696] mv_xor d0060900.xor: error addr   0x00000000
[  175.729384] ------------[ cut here ]------------
[  175.734219] WARNING: CPU: 0 PID: 837 at drivers/dma/mv_xor.c:891 mv_xor_interrupt_handler+0x218/0x220
[  175.743552] Modules linked in: raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c md_mod loop cp4
[  175.793057] CPU: 0 PID: 837 Comm: md0_raid5 Not tainted 4.12.0 #1
[  175.798983] Hardware name: Globalscale Marvell ESPRESSOBin Board (DT)
[  175.805812] task: ffff80007a6a2180 task.stack: ffff80000f964000
[  175.811834] PC is at mv_xor_interrupt_handler+0x218/0x220
[  175.817316] LR is at mv_xor_interrupt_handler+0x218/0x220
[  175.823065] pc : [<ffff00000849bea0>] lr : [<ffff00000849bea0>] pstate: 800001c5
[  175.830970] sp : ffff80007ffb7eb0
[  175.834210] x29: ffff80007ffb7eb0 x28: ffff80007a6a2180 
[  175.839423] x27: ffff80007c881800 x26: ffff00000892a000 
[  175.845083] x25: ffff00000892a000 x24: ffff0000089499b8 
[  175.850563] x23: ffff80007ffb7f74 x22: 0000000000000000 
[  175.856225] x21: 0000000000000202 x20: 0000000000000202 
[  175.861527] x19: ffff80007c93d018 x18: ffffffffffffffff 
[  175.867098] x17: 0000ffff99732190 x16: ffff000008132e80 
[  175.872490] x15: ffff000008949990 x14: ffff000088a68677 
[  175.877881] x13: ffff000008a68685 x12: 0000000000000040 
[  175.883362] x11: 0000000000000000 x10: 0000000005f5e0ff 
[  175.889021] x9 : 000000000000003c x8 : ffff0000084df098 
[  175.894235] x7 : ffff00000892a000 x6 : 000000000000010c 
[  175.899805] x5 : 0000000000000001 x4 : 0000000000000001 
[  175.905287] x3 : 0000000000000007 x2 : 0000000000040c00 
[  175.910680] x1 : 0000000000040c00 x0 : 0000000000000000 
[  175.916340] ---[ end trace 7e73d6a794d41f87 ]---

All NICs coming in with the same MAC (uBoot setting, not kernel problem??):

root@espressobin:~# ifconfig -a | grep ether
        ether ce:c7:d3:27:72:1f  txqueuelen 532  (Ethernet)
        ether ce:c7:d3:27:72:1f  txqueuelen 1000  (Ethernet)
        ether ce:c7:d3:27:72:1f  txqueuelen 1000  (Ethernet)
        ether ce:c7:d3:27:72:1f  txqueuelen 1000  (Ethernet)

Really poor onboard NIC performance. 921 Mbits/sec @ 100% CPU usage. Same test on the espressobin using an Intel Pro 1000 (e1000e) NIC and I get 936 Mbits/sec @ 15% CPU usage. I believe this is caused by lack of hard acceleration on the NIC. Not sure if this is just not coded in, or if the NIC is just lacking the support outright?

Here is my current config

Any info, help, directions would be greatly appreciated.
Thanks
Adam (DingbatCA)