FWIW, we recently noticed a similar issue with our CUBIC senders after
we've enabled FQ on them (4.15 kernel.)
Disabling train detection in hystart did fix the problem:
# echo 2 > /sys/module/tcp_cubic/parameters/hystart_detect
[1]
https://github.com/torvalds/linux/blob/master/net/ipv4/tcp_cubic
Have a look at https://forum.openwrt.org/t/crashlog-retrieval-mips/19731. It
seems cat /sys/kernel/debug/crashlog after a reboot caused by a crash
mightcreveal some more details.
Good luck
Sebastian
On February 18, 2020 7:35:31 PM GMT+01:00, "Toke Høiland-Jørgensen"
wrote:
>Rich Brown
Rich Brown writes:
> Folks,
>
> I was running OpenWrt 19.07-rc2 on my Archer C7v2, and experienced a
> potentially-repeatable crash under heavy network traffic load.
>
> I was uploading several long videos to Youtube (> 5GBytes each) and
> watching Netflix on my 7mbps/768kbps DSL connection. Thin
Folks,
I was running OpenWrt 19.07-rc2 on my Archer C7v2, and experienced a
potentially-repeatable crash under heavy network traffic load.
I was uploading several long videos to Youtube (> 5GBytes each) and watching
Netflix on my 7mbps/768kbps DSL connection. Things were working fine (latency
