<xdarklight>
rsalvaterra: upstream suggests that our downstream xt_flowoffload module is the actual problem
<rsalvaterra>
xdarklight: I see, thanks for the info!
djStolen has joined #openwrt-devel
<xdarklight>
I'm not sure if Aleksander is here on IRC. he's doing some great detective + improvement (including bugfix) work on the Lantiq target currently - that finding is part of his testing/improvement efforts
<Borromini>
xdarklight: i think his nick is lynxis
<xdarklight>
Borromini: I think lynxis is Alexander Couzens
<xdarklight>
Borromini: I meant Aleksander Jan Bajkowski (abajk on github)
m has joined #openwrt-devel
m has quit []
<plntyk>
xdarklight, first one was right
m has joined #openwrt-devel
<Borromini>
xdarklight: ok, sorry.
mcarroll76 has quit [Remote host closed the connection]
<rsalvaterra>
xdarklight: I'm looking at 650-netfilter-add-xt_FLOWOFFLOAD-target.patch, but it's mostly Mandarin to me.
<rsalvaterra>
It sets up two flow tables, but only one of them has the NF_FLOWTABLE_HW_OFFLOAD flag set.
<xdarklight>
rsalvaterra: based on the comment on the mailing list I thought "oh so we just need to add an if somewhere". for me this turned into "I'll let someone else take over"
<rsalvaterra>
Why two flow tables? Is one of them for software flow offloading, the other one for hardware flow offloading? It looks like it…
<rsalvaterra>
xdarklight: Yeah, netfilter is a bit scary.
SamantazFox has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
m has quit [Quit: Leaving]
m has joined #openwrt-devel
danitool has joined #openwrt-devel
m has quit [Remote host closed the connection]
dannyAAM has joined #openwrt-devel
philipp64|work has quit [Read error: Connection reset by peer]
philipp64|work has joined #openwrt-devel
philipp64|work has quit [Remote host closed the connection]
philipp64|work has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
dedeckeh has joined #openwrt-devel
Luke-Jr has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
netprince has quit [Remote host closed the connection]
netprince has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
<xdarklight>
nbd: for some reason it's not displaying the stacktrace for me, but symptoms are the same (connecting a client to the ath9k interface -> a few seconds later the device reboots, presumably due to a watchdog reset)
<xdarklight>
nbd: the Home Hub 5A uses an AR9287 and is limited to the 2.4GHz band (in case that matters)
djStolen has quit [Read error: Connection reset by peer]
<xdarklight>
nbd: ath10k works fine for me though and the reporter of that bug-ticket mentions that mt76 is working for her
<PaulFertser>
It's odd getting full kernel output was problematic from a KVM machine.
djStolen has joined #openwrt-devel
<xdarklight>
PaulFertser: in my case I am connected via serial console to my device and I get literally nothing. it goes from "oh hey there's a new client on wlan1" back to "hello from the bootrom, let me load u-boot for you"
robimarko has joined #openwrt-devel
<xdarklight>
so unfortunately I am not able to provide more info :/
<PaulFertser>
xdarklight: probably wrong access goes straight to something essential like WDT unit, that's unfortunate.
<hauke>
Linux should lock if the reboot was triggered by a watchdog event
<hauke>
xdarklight: I think there is even an interface in the watchdog driver and it should be implemented for lantiq
<hauke>
there is a reset cause register somewhere in the RCU register block which contains the reson of the last boot
<PaulFertser>
I mean probably something happens and the code directly writes to some MMIO register causing immediate reboot, not that it's the WDT doing its job.
<xdarklight>
hauke: I'll check that tomorrow, right now I went back to a "known good" revision and will head to bed now
<xdarklight>
PaulFertser: ah, that's also possible
SamantazFox has joined #openwrt-devel
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Ping timeout: 480 seconds]
jlsalvador2 is now known as jlsalvador
Borromini has quit [Quit: leaving]
robimarko has quit [Quit: Page closed]
slh64 has quit [Ping timeout: 480 seconds]
slh has quit [Ping timeout: 480 seconds]
rmilecki has quit [Ping timeout: 480 seconds]
Tusker has joined #openwrt-devel
djStolen has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]