bookworm has quit [Read error: Connection reset by peer]
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
Daanct12 has joined #openwrt-devel
KGB-2 has quit [Remote host closed the connection]
KGB-2 has joined #openwrt-devel
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #openwrt-devel
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
valku1 has joined #openwrt-devel
valku has quit [Ping timeout: 480 seconds]
valku1 is now known as valku
schwicht has joined #openwrt-devel
valku1 has joined #openwrt-devel
valku2 has joined #openwrt-devel
valku has quit [Ping timeout: 480 seconds]
valku2 is now known as valku
schwicht has quit [Ping timeout: 480 seconds]
valku has quit [Remote host closed the connection]
valku has joined #openwrt-devel
valku1 has quit [Ping timeout: 480 seconds]
valku has quit []
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
hbug has quit [Quit: hbug]
schwicht has joined #openwrt-devel
ssterling has quit [Ping timeout: 480 seconds]
schwicht has quit [Ping timeout: 480 seconds]
<f00b4r0>
nbd: quick update before I go; it seems the device doesn't want to crash again right now. I'll keep you updated
drikus has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #openwrt-devel
warpme has joined #openwrt-devel
<djfe>
funnily enough I kept on reading about your efforts on here. We just did install new APs (unifi 6 LR v3 - mt7622) and 5GHz (mt7915) is affected by list_del corruption
<djfe>
three of those APs, installed since tuesday
<djfe>
so yeah, I don't want to interfere with your testing f00b4r0 , but I could chime in in a couple of days if your device doesn't reproduce the issue anymore
<djfe>
what you see in Grafana are separate issues though:
<djfe>
the stack trace you can't see. the last time it happened was 21.08.25 at 09:09 I restarted wifi with "wifi" then to get 5GHz to work again
<djfe>
separate from that and offtopic are two issues you can see: memory leaks (3 separate ones). This could be the hostapd memory leak some people talked about in this irc channel
<djfe>
and also offtopic: airtime report for 5GHz (mt7915) is broken. (this is also the case for some other devices like the D-Link dap-x1860
<mrkiko>
anyone experiencing issues with modemmanager proto handler in snapshot?
ssterling has joined #openwrt-devel
<castiel652>
nbd: Hi I think there's an issue with mt7981's precal size. According to the document the size should be 54x1024+16+102x1024=159760, but when I set it in device tree it got a warning and said the size is 200720 which means the CAL_GROUP_SIZE it got in mt76 is larger.
<castiel652>
also the proprietary driver has a even larger CAL_GROUP_SIZE
valku has joined #openwrt-devel
warpme has quit []
caskd has quit [Ping timeout: 480 seconds]
minimal has joined #openwrt-devel
valku has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
caskd has joined #openwrt-devel
valku has joined #openwrt-devel
castiel652 has quit [Read error: Connection reset by peer]