Rentong has quit [Remote host closed the connection]
hexa- has quit [Quit: WeeChat 3.1]
dangole_ has joined #openwrt-devel
dangole has quit [Ping timeout: 480 seconds]
hexa- has joined #openwrt-devel
Rentong has joined #openwrt-devel
dangole has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
dangole_ has quit [Ping timeout: 480 seconds]
svanheule has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
svanheule has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
dangole has quit [Remote host closed the connection]
dangole has joined #openwrt-devel
Rentong has joined #openwrt-devel
dangole has quit [Remote host closed the connection]
Rentong has quit [Ping timeout: 480 seconds]
indy has quit [Read error: Connection reset by peer]
indy has joined #openwrt-devel
<digitalcircuit>
Or, if I've got enough time/too late for 21.02.0 stable/etc, I'll wait on PATCHv2 a few days to try to figure out what stress-ng parameters recreate the kernel panic without needing to set up OpenSSH SFTP, etc.
<digitalcircuit>
slh: Following up on your testing comment, I've gotten 10/10 seven hour SFTP backups to succeed consecutively with the ipq806x patch ( https://bugs.openwrt.org/index.php?do=details&task_id=3099#comment9820 ), where previously (across 21.02.0-rc1 and -rc2) 5/30 backups succeeded with at most 2 consecutive successes.
<digitalcircuit>
Meanwhile, I haven't gotten any feedback on the mailing list patch, so I can submit a PATCHv2 with updated testing information in the commit message.
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
rmilecki has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<plntyk>
digitalcircuit, you could reply to your original message with the testing info without sending a v2
Rentong has quit [Remote host closed the connection]
<digitalcircuit>
plntyk, that sounds like a good idea, thank you! I imagine the commit message could be edited when merged if needed, too. Within the next few days I'll look into writing up my test results (including a simpler stress-ng test case if I get that working) and will find and CC the main ipq806x contributor on my reply.
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
<plntyk>
digitalcircuit, be aware the -rc3 is already out so not much time left
Rentong has quit [Ping timeout: 480 seconds]
<digitalcircuit>
plntyk, noted, heads up appreciated! I'll try to do it this Sunday EST (depending on how Father's Day stuff with family goes), might end up being Monday.
<digitalcircuit>
When you mention "main contributor of ipq806x", https://openwrt.org/submitting-patches#select_email_destination suggests checking the Makefile, though "target/linux/ipq806x/Makefile" doesn't seem to list any. I've CC'd the original patch author, Ansuel who also seems fairly active on ipq806x based on commit history. If there's others I should CC though I can do that.
<plntyk>
digitalcircuit, ynezz and hauke committed some ipq806x (via git log --pretty=fuller target/linux/ipq806x/ ) dunno if they have seen your patch or testing since you seem to be in a slightly different timezone from your activity
<plntyk>
afaik both are CET while your posts are really early for CET timezone
<digitalcircuit>
plntyk, again, thanks! Makes sense to potentially include them in a testing/justification of backport reply email. (I figured even with preparation I'd miss some aspects for my first patch submitted through a mailing list.)
Rentong has joined #openwrt-devel
lmore377 has quit [Quit: No Ping reply in 180 seconds.]
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
pmelange has joined #openwrt-devel
<pmelange>
Hi, I have had a PR waiting since April to fix a problem which appeared with me first test of 20.02.0-rc1. Without the change, qos-scripts is broken. There have been many comments in the PR from people who have tested the change, but so far nobody has been willing to do a review. Is there something that I need to do to get this PR reviewed? https://github.com/openwrt/openwrt/pull/4092
<pmelange>
Oops, 21.02.0-rc1 (obviously)
Rentong has quit [Remote host closed the connection]
dangole has quit [Read error: Connection reset by peer]
<enyc>
aparcar[m]: there was [at least] some bot relating to openwrt reproducible-builds that was blubing out on irc.libera.chat #openwrt-devel, thereby looking like it may have been placed in wrong place amongst the freenode exodus/fiasco, checking if its still popping up
<hauke>
enyc: I think lynxis takes care of the reproducible-builds
<enyc>
hauke lynxis aparcar[m] : this morning on irc.libera.chat 08:14 -KGB-0:#openwrt-devel- https://tests.reproducible-builds.org/openwrt/openwrt_bcm47xx.html has been updated. (100.0% images and 98.1% [...] etc etc on irc.libera.chat *presumably* this is a mistake to be over there and not on OFTC official channel [?]
<enyc>
just thought I'd point out as it seems out-of-place.
* enyc
caused or helped a LOT of projects to update pointers web pages and things in channels and so-on out of freenode... but there we go!
<stintel>
Slimey: this CPU is not supported. I've been working on a WatchGuard Firebox M200 for a while, which has a T1042 which is also PPC64 e5500, even musl libc doesn't properly support it due to it lacking altivec instructions
<stintel>
Slimey: if you want to have a go at adding support for it, you could have a look at https://git.openwrt.org/?p=openwrt/staging/stintel.git;a=shortlog;h=refs/heads/m200 to get an idea
<stintel>
but that's very WIP and experimental
ISG has joined #openwrt-devel
feriman has joined #openwrt-devel
<stintel>
iirc I was able to boot it but never managed to get network up and running, but that might be easier for your device
Tapper has quit [Quit: Tapper]
<aparcar[m]>
mangix: ping
ISG has quit [Read error: Connection reset by peer]
Rentong has joined #openwrt-devel
<mangix>
aparcar[m]: pong
<aparcar[m]>
mangix: you already responded via github, thanks