* Maxim V FIlimonov (c...@bein.link) wrote:
> Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
> to be precise). The problem was that the load average was above 2. Including
> the fact that the board has 2 CPU cores, that's strange. Also, the network
> throughput was
On Saturday 20 September 2014 13:24:08 Ian Lepore wrote:
> Since it's happening only on that hardware, there's a good chance the
> problem is in the allwinner a10/a20 clock driver, not in the general
> eventtimer code. In fact, looking at the code it appears that a
> divide-by-16 is being set in t
On Sat, 2014-09-20 at 22:44 +0400, Maxim V FIlimonov wrote:
> Hello everyone,
>
> Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
> to be precise). The problem was that the load average was above 2. Including
> the fact that the board has 2 CPU cores, that's strange.
Hello everyone,
Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
to be precise). The problem was that the load average was above 2. Including
the fact that the board has 2 CPU cores, that's strange. Also, the network
throughput was way too slow: from 3 kilobytes per
Hello everyone,
Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
to be precise). The problem was that the load average was above 2. Including
the fact that the board has 2 CPU cores, that's strange. Also, the network
throughput was way too slow: from 3 kilobytes per
