Hi Tom, On Sat, Feb 09, 2019 at 01:28:32PM +0100, Tom Psyborg wrote: > On 09/02/2019, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: > > On Sat, Feb 09, 2019 at 12:11:03PM +0100, Tom Psyborg wrote: > >> Can you reproduce interface freeze with this patch if you enable debug > >> options to print all dbg messages? > > > > Haven't tried that, but I expect enabling debug messages will > > cause troubles at hardware where printk make CPU hog. > > > > Stanislaw > > > > Take a look at my comment from 23.01.2019. on this link: > https://bugs.openwrt.org/index.php?do=details&task_id=2018 > There might be a chance dbg printks do not cause problems. This is very likely just overheat because of missing TSSI. It happends on boards where MT7620A is used without heatsink (and easy to reproduce, I've tried. We just need TSSI and for bad board design it will mean limiting to one TX-queue soon after serious traffic starts). We should tell those users to glue heatsink on the chip for $0.05 they can fix this in hardware -- and implement TSSI to mitigate at least the very worst effects (such as hardware stuck until reset). So dkg printks can make this worse, of course, because logging overhead also burns CPU cycles and increases system load. I remember in Rt5350 (and other predecessors of Rt6352 aka. MT7620) also had problems like that and it was possible to improve it by all sorts of things like removing power from unused ports of the Ethernet switch -- so for those boards (like Xiaomi MiWiFi mini) even this maybe the trick, because they also only use 3 out of 5 ports, and maybe we need to try harder to disable the power of unused ports (and also those without cable plugged in only periodicly power them up and check for link).... Cheers Daniel
