<Ansuel>
Oh I never received notification of them asking for log... My bad
<robimarko>
I did but it happens completely randomly on my Dynalink that is always up
<Ansuel>
yes the main problem is repro... but i notice the key point are low reception (i guess lots of corruption/retrasmission) and disconnect and auth right after
<robimarko>
I also noticed that it doesnt really like AX20X cards from intel
<Ansuel>
when the fw was much more broken one way to repro it was to just disconnect and reconnect 20-30 times and you had the packet missing in the flow and being stalled
<Ansuel>
(aka they never reach the completition ring)
<Ansuel>
i guess those mask enables dump of the completition ring
<Ansuel>
robimarko might be a coincidence with the card used on windows (that really loves to disconnect and reconnect multiple times)
<robimarko>
It does the same on Linux as well
<Ansuel>
we should test if the problem is there with my ap migration patch... some crash were reported with that so maybe there is some problem in the fw with that logic? would be worth a test
<robimarko>
Oh, WLAN.HK.2.9-02509-QCAHKSWPL_SILICONZ-1 FW actually boots on MR7350
<Ansuel>
with coldboot ?
<robimarko>
Without, just rebuilding with coldboot
<Ansuel>
they learned the lesson with 2.7 with totally dropping support with ancient bdf
<robimarko>
And still the same log with coldboot
<robimarko>
So, its probably BDF as well
<Ansuel>
just as a test....
<Ansuel>
can you swap the bdf with something recent?
nixuser has quit [Remote host closed the connection]
nixuser has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
Mangix has joined #openwrt-devel
cmonroe has joined #openwrt-devel
<stintel>
having another go at bumping qoriq to 6.1
<stintel>
well, or at least adding 6.1 as testing kernel - I had actually done this months ago locally, but there was this ongoing discussion about the kernel config history in git and decided not to push because of that
<stintel>
also iirc I had a crash after some uptime, so I don't want to make 6.1 default just yet
<stintel>
sigh, kernel_oldconfig is missing a bunch of symbols again
Lechu has quit [Remote host closed the connection]
<Ansuel>
stintel should I add a step to check for kernel config flags?
<Ansuel>
maybe make kernel_oldconfig and see if the config changes?
<stintel>
in CI?
<stintel>
could be useful
<Ansuel>
yep similar to what we do for packages hash
<stintel>
but I think it's because I enable some non-default CONFIG_KERNEL_* options in the OpenWrt .config