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. I'm sure printk cause problems on some hardware i.e. Wt3020 . There is hypothesis that is because kernel try to emit messages by misconfigured 56k serial line, but who knows. This should be debugged and fixed but I have not idea how to do this. Another issue not related with printk is tx queue hung, when queue is full but we do not get any TX status interrupt. This was mitigated in my previous set that caused throughput regression and should be now fixed by latest RFC/RTF set. But there are other issues, that could cause troubles. Stanislaw
