Tapper has quit [Ping timeout: 480 seconds]
minimal has quit []
victhor has quit [Ping timeout: 480 seconds]
shibboleth has quit [Ping timeout: 480 seconds]
<stintel> hauke: thanks for fixing the brcmfmac deadlock
<stintel> there seems to be quite a big increase in Pi Zero W boot / connect time though :(
<stintel> [ 51.958511] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<stintel> [ 36.000551] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<stintel> hmmm maybe because I enabled LOCKDEP
<dwfreed> even 36 seconds seems high
<stintel> dwfreed: for Pi Zero it's normal
<stintel> or normal-ish
<stintel> actually you are right
<dwfreed> 52 seconds to wlan0 ready on my nbg6817
<dwfreed> (19.07 though)
<dwfreed> 55 for wlan1
<stintel> it should be much faster
<stintel> [ 14.584531] kmodloader: - jitterentropy_rng - 0
<dwfreed> netifd start is around 44 seconds
<stintel> so kernel is ready, then it takes 22 (!) seconds to connect
<stintel> that's not normal
<stintel> irclogs/2021/02/Freenode/#openwrt-devel.log:20|13:33:54< stintel> [ 12.414680] urngd: jent-rng init failed, err: 2 [ 21.940740] random: crng init done [ 35.963169] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<stintel> yeah
<stintel> seems close enough
<stintel> hmm, but I'm pretty sure it was faster after noltari added target/linux/generic/pending-5.10/840-hwrng-bcm2835-set-quality-to-1000.patch
<stintel> that resulted in `random: crng init done` after ~1s
<stintel> [ 35.102248] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<stintel> ok, disabling CONFIG_KERNEL_PROVE_LOCKING brought it back from ~52 to ~35
<stintel> so leaving that enabled in my config is not a good idea
dangole_ has quit [Ping timeout: 480 seconds]
<stintel> noltari: can you review https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=shortlog;h=refs/heads/rpizero2 ?
goliath has quit [Quit: SIGSEGV]
<stintel> maybe the firmware package name could be better
<stintel> but honestly what a fucking mess
strobo_ has joined #openwrt-devel
strobo has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
danitool has quit [Ping timeout: 480 seconds]
strobo has joined #openwrt-devel
strobo_ has quit [Ping timeout: 480 seconds]
valku has joined #openwrt-devel
Tapper1 has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
<owrt-snap-builds> Build [#351](https://buildbot.openwrt.org/master/images/#builders/40/builds/351) of `ipq40xx/mikrotik` completed successfully.
goliath has joined #openwrt-devel
_lore_ has quit [Ping timeout: 480 seconds]
nitroshift has joined #openwrt-devel
mrkiko has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
<owrt-snap-builds> Build [#348](https://buildbot.openwrt.org/master/images/#builders/22/builds/348) of `ipq40xx/generic` completed successfully.
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
strobo has quit [Ping timeout: 480 seconds]
rua has quit []
rua has joined #openwrt-devel
Tapper1 has quit [Read error: Connection reset by peer]
Grommish has joined #openwrt-devel
* enyc meeps
<enyc> stintel: wow mini gigabit device... I'd like to see router style devices with 8+ integrated ethernet ports, wonder why they don't exist already etc...
<enyc> [maybe they do=
<Grommish> enyc: ER10x sorta, if you squint a lot and ignore the fact it's basically a router and a switch badly mashed together
_lore_ has joined #openwrt-devel
pmelange has joined #openwrt-devel
rsalvaterra has quit [Quit: rsalvaterra]
rsalvaterra has joined #openwrt-devel
* enyc meeps
<neggles> I mean there's quite a few devices with 8+ ethernet that are either direct to CPU or effectively direct to CPU
pmelange has left #openwrt-devel [#openwrt-devel]
<neggles> mikrotik CCR2004-16G-2S+ has two 8-port switch chips each with with 10G to the CPU, plus 2x10G SFP+ direct-to-CPU, the EdgeRouter Infinity has 8x SFP+ direct-to-CPU
<neggles> and of course there's the plethora of x86_64 firewall devices from aliexpress/various UTM vendors with ~4-16 intel NICs on them and varying amounts of actual horsepower
pmelange has joined #openwrt-devel
pmelange has left #openwrt-devel [#openwrt-devel]
<neggles> the RB5009UG+S+IN has 10Gbps CPU uplink to a switch chip with 1xSFP+ / 1x2.5G / 7x1G, and it's using an SoC and a switch chip which are pretty much fully supported in mainline / with DSA
<neggles> if you don't use the SFP+, or you switch on some ports, it's not overcommited at all :P
victhor has joined #openwrt-devel
danitool has joined #openwrt-devel
f00b4r0__ has joined #openwrt-devel
<nitroshift> _lore_, did you have time to look around balancing mvneta across both armada385 cores?
T-Bone has quit [Ping timeout: 480 seconds]
<_lore_> nitroshift: nope sorry
felix has quit []
<nitroshift> _lore_, no problems :)
felix has joined #openwrt-devel
strobo has joined #openwrt-devel
strobo_ has joined #openwrt-devel
strobo has quit [Ping timeout: 480 seconds]
dangole_ has joined #openwrt-devel
sbrown has joined #openwrt-devel
strobo_ has quit [Ping timeout: 480 seconds]
strobo has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
Tusker has quit [Remote host closed the connection]
dangole_ has quit [Remote host closed the connection]
dangole_ has joined #openwrt-devel
slh has quit [Ping timeout: 480 seconds]
slh64 has quit [Ping timeout: 480 seconds]
slh64 has joined #openwrt-devel
slh has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
svanheule has quit [Quit: svanheule]
svanheule has joined #openwrt-devel
sbrown has quit [Remote host closed the connection]
<karlp> hrm, I suspect odhcpd is picking up host libubox, instead of buildroot libubox?
<karlp> I get src/config.c:1125:17: error: implicit declaration of function 'mkdir_p'; did you mean 'mkdirat'?
<karlp> I definitely have an old libubox on my host.
<karlp> hrm, something else, updated host libubox, no issue.
floof58 has joined #openwrt-devel
gladiac has quit [Quit: k thx bye]
gladiac has joined #openwrt-devel
<Habbie> aparcar[m], 'opkg install auc' yields a non-working auc until i reboot, presumably because something needs to be reloaded before rpcd-mod-rpcsys works; is that a bug? should something be triggering some reload?
<stintel> does restarting rpcd help ?
<Habbie> likely, will test that later
floof58 has quit [Ping timeout: 480 seconds]
minimal has joined #openwrt-devel
floof58 has joined #openwrt-devel
<dangole_> Habbie: I supposedly fixed this recently with commit 32ba52e217 rpcd: reload rpcd on installation of rpcd-mod-*
<Habbie> dangole_, ah thanks, i'll look at that - presumably that one is not in 21.02 yet
<Habbie> (should have mentioned 21.02, sorry)
<dangole_> Habbie: no, not backported yet, but we should
<rsalvaterra> Looks like Nick's already aware of the update zstd code bloat, thankfully… https://marc.info/?l=linux-crypto-vger&m=163692587329663&w=4
<rsalvaterra> *updated
nitroshift has quit [Quit: Gone that way --->]
zx2c4_ has quit []
zx2c4_ has joined #openwrt-devel
zx2c4_ is now known as zx2c4
pmelange has joined #openwrt-devel
<hurricos> Hey, who maintains ipq40xx?
<hurricos> I want to know whether I can safely sysupgrade a SXTsq 5 ac
<hurricos> without taking it down :^)
<hurricos> ..... I bet anyone would have made a compat revision if sysupgrade DIDN'T work from 21.02.0-rc3
<Habbie> stintel, yes, /etc/init.d/rpcd restart works :)
<Habbie> dangole_, commit looks good, i did not test it
<pmelange> There currently aren't any docker sdk images for 21.02.1 on dockerhub. Was this done intentionally for some reason? Is it possible to get the process started to generate the sdk images? Currently freifunk-berlin is waiting on those docker images so that our buildbot can get to work building our firmware which is based on 21.02.1.
danitool has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
floof58_ has joined #openwrt-devel
floof58 has quit []
floof58_ has quit []
floof58 has joined #openwrt-devel
f00b4r0__ has quit [Quit: Quitte]
<aparcar[m]> Habbie: I think the version you’re installing is highly outdated. I’ll work with Daniel on it
<Habbie> 0.2.4-1
<Habbie> but, other than the rpcd restart thing, it does work
<stintel> hurricos: we don't have target maintainers anymore
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 480 seconds]
KGB-0 has quit [Ping timeout: 480 seconds]
<florian_> clear
<stintel> florian_: ?
<florian_> wrong terminal
<stintel> gotcha :)
f00b4r0 has joined #openwrt-devel
KGB-0 has joined #openwrt-devel
minimal has quit []
pmelange has left #openwrt-devel [#openwrt-devel]
Borromini has joined #openwrt-devel
<mangix> Ansuel: ping
<dwfreed> mangix: they are not here right now
<mangix> Thing is I’ve noticed he comes on when mentioned before. Maybe he looks at public logs…
dangole_ has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
Tusker has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
<dwfreed> mangix: more likely just impeccable timing
<mkresin> dangole: mind to have a look at this w921v_fw_cutter related PR: https://github.com/openwrt/openwrt/pull/2678/
<owrt-2102-builds> Build [#142](https://buildbot.openwrt.org/openwrt-21.02/images/#builders/65/builds/142) of `gemini/generic` failed.
Borromini has quit [Quit: leaving]
minimal has joined #openwrt-devel
<dangole> mkresin: imho #2678 is a non-problem. the extractor runs once and all memory is freed anyway when the execution ends.
<mkresin> dangole: thanks!
xdarklight has quit [Quit: ZNC - https://znc.in]
Acinonyx has joined #openwrt-devel
Acinonyx_ has quit [Ping timeout: 480 seconds]