Hi John and the rest,
The kernel version got bumped to 4.9 so I wondered if there is a 4.9
version of the patch?
Tried searching your staging tree but I couldn't find any.
Kind regards,
Bart
On Wed, Jul 5, 2017 at 9:54 PM, Jaap Buurman wrote:
> Dear all,
>
> I just had time to test it myself an
Dear all,
I just had time to test it myself and I can confirm that SQM cake is
still crashing the router. Hopefully we do have a nice lead now where
to look for the issue. If any more testing is needed in the future,
please let me know. Thank you very much again for your time and
effort, John!
Ki
Dear John,
I haven't had time to test it yet myself, but in the previously
mentioned topic by Bart van Zoest there have already been two reports
of crashing devices with SQM cake enabled unfortunately.
One of the posters provided a stack trace, which hopefully will be
useful in debugging the issu
Hi John and the rest,
This is great news! Hopefully this will solve the problems of the
people owning mt7621 with SQM QoS!
I have compiled a build with your revised patch for the D-Link
DIR-860L B1 located at
https://forum.lede-project.org/t/optimized-build-for-the-d-link-dir-860l/948
for the peop
On 29/06/17 20:14, Jaap Buurman wrote:
Dear John,
This patch sounds very very promising! I will compile and test this
first come this weekend. Thank you so very much for having a look at
this issue :)
Yours sincerely,
Jaap
___
Lede-dev mailing lis
Dear John,
This patch sounds very very promising! I will compile and test this
first come this weekend. Thank you so very much for having a look at
this issue :)
Yours sincerely,
Jaap
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists
Hi John,
great, you've found the reason for the problems on MT7621.
I'd gladly help with testing (here, also with the cake scheduler enabled where
I had these stalls rather frequently). However, two questions:
-) Is [1] the patch that fixes the problem? What has been changed there?
-) I guess, thi
Hi,
there have been various bug reports related to mt7621 where one of the
cores seems to have dead locked. while digging thorugh the SDK i found
that the recalibrate the delay loop after powering up all 4 cores.
checking /proc/cpuinfo we see that the 4 cores run at different bogo
mips. i pus
