Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-20 Thread Reco
Hi. On Sat, Oct 20, 2018 at 01:44:36PM +0200, LinAdmin wrote: > On 19.10.2018 23:35, Reco wrote: > > Hi. > > > > On Fri, Oct 19, 2018 at 11:25:47PM +0200, LinAdmin wrote: > >> On 19.10.2018 20:12, Uwe Kleine-König wrote: > >>> Hello, > >>> > >>> On 10/19/2018 04:39 PM, LinAdmin wrote:

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-20 Thread LinAdmin
On 19.10.2018 23:35, Reco wrote: > Hi. > > On Fri, Oct 19, 2018 at 11:25:47PM +0200, LinAdmin wrote: >> On 19.10.2018 20:12, Uwe Kleine-König wrote: >>> Hello, >>> >>> On 10/19/2018 04:39 PM, LinAdmin wrote: When the system is idle, one CPU is always busy at least 50% with a

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-20 Thread Uwe Kleine-König
Hello, On 10/19/2018 11:25 PM, LinAdmin wrote: > On 19.10.2018 20:12, Uwe Kleine-König wrote: >> Hello, >> >> On 10/19/2018 04:39 PM, LinAdmin wrote: >>> When the system is idle, one CPU is always busy at least 50% >>> with a kworker thread which IMHO does not perform any useful >>> work. When

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-19 Thread Reco
Hi. On Fri, Oct 19, 2018 at 11:25:47PM +0200, LinAdmin wrote: > On 19.10.2018 20:12, Uwe Kleine-König wrote: > > Hello, > > > > On 10/19/2018 04:39 PM, LinAdmin wrote: > >> When the system is idle, one CPU is always busy at least 50% > >> with a kworker thread which IMHO does not perform

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-19 Thread LinAdmin
On 19.10.2018 20:12, Uwe Kleine-König wrote: > Hello, > > On 10/19/2018 04:39 PM, LinAdmin wrote: >> When the system is idle, one CPU is always busy at least 50% >> with a kworker thread which IMHO does not perform any useful >> work. When idle, the kernel 4.9.y built exclusively for >> Marvell

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-19 Thread Uwe Kleine-König
Hello, On 10/19/2018 04:39 PM, LinAdmin wrote: > When the system is idle, one CPU is always busy at least 50% > with a kworker thread which IMHO does not perform any useful > work. When idle, the kernel 4.9.y built exclusively for > Marvell has both CPU’s at below 1% load. How do you diagnose

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-19 Thread LinAdmin
Having further investigated the problems of armmp with Marvell I would like to thank Uwe for submitting a patch which resolves problem a). Problem b) arises because code intended only for TI chips gets initialized on Marvell. When disabling in kconfigs "POWER_AVS, POWER_AVS_OMAP,

Re: Problems using stock kernel armmp with Marvell 38x hardware.

2018-10-08 Thread Uwe Kleine-König
Hello, [I already replied to this mail in private by accident, so there is some old stuff in it for LinAdmin] On Tue, Sep 25, 2018 at 10:45:06AM +0200, LinAdmin wrote: > a) In the kernel config I used, the buffer management > CONFIG_MVNETA_BM_ENABLE was set, while in > config-4.9.0-8-armmp it is

Problems using stock kernel armmp with Marvell 38x hardware.

2018-09-25 Thread LinAdmin
Hi experts! I recently bought a NAS with the Marvell Armada 385 dual core CPU and 2x 8TB disks. The performance of the hardware is excellent but the software from the manufacturer is ugly with a rather old kernel (3.10). I succeeded cross-building a recent 4.9.y kernel using kernel config and