13:04:07 <jki> #startmeeting CIP IRC weekly meeting
13:04:07 <collab-meetbot`> Meeting started Thu Sep 18 13:04:07 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:04:07 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:04:07 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:04:17 <jki> #topic AI review
13:04:36 <jki> - start define a CIP kernel threat model [Pavel]
13:04:52 <jki> pavel: any news?
13:05:08 <pave1> working on ha. first version is in git now
13:05:29 <jki> ok - please once you like to have feedback
13:05:30 <pave1> still need to spell check and send i to list
13:05:35 <jki> perfect
13:05:49 <jki> nothing else on my list otherwise
13:05:55 <jki> 5
13:05:57 <jki> 4
13:05:59 <jki> 3
13:06:00 <jki> 2
13:06:02 <jki> 1
13:06:04 <jki> #topic Kernel maintenance updates
13:06:26 <masami> This week reported 449 new CVEs and 1 updated CVEs.
13:06:41 <pave1> I'm doing reviews, 6.12.47 is out now
13:06:42 <jki> ulrich: "Working on 4.19 ATM, it'll probably be ready on Monday."
13:07:18 <iwamatsu__> I reviewed 6.12.44 and reviewing 6.12.45.
13:08:43 <jki> ok, anything to add?
13:09:28 <jki> 5
13:09:30 <jki> 4
13:09:31 <jki> 3
13:09:33 <jki> 2
13:09:35 <jki> 1
13:09:39 <jki> #topic Kernel release status
13:09:52 <jki> 4.19 is late but comming next week
13:10:06 <jki> 6.1-rt?
13:10:30 <pave1> 6.1-rt is late, I am currently working on it.
13:11:02 <iwamatsu__> Pave1: Thanks for relelase 6.1.y-cip.
13:11:02 <pave1> shuld be later today if it passes testing.
13:11:42 <jki> great
13:12:06 <jki> any issues otherwise?
13:12:30 <jki> 5
13:12:32 <jki> 4
13:12:33 <jki> 3
13:12:34 <jki> 2
13:12:36 <jki> 1
13:12:38 <jki> #topic Kernel testing
13:13:05 <arisut_> https://dashboard.kernelci.org/tree/cip/linux-6.1.y-cip/668a07393455734b16b88d0c167bb0de35785251?p=bt we started to have boot results from KernelCI
13:13:15 <arisut_> on production
13:14:16 <jki> ok, mostly unavailable test hw, right?
13:14:38 <arisut_> we have most of the cip lava platforms
13:14:44 <arisut_> arm64 are working
13:15:23 <arisut_> x86_64 and beaglebone are not working
13:15:36 <arisut_> beaglebone i see it work few times
13:15:41 <jki> no x86 targets
13:15:52 <patersonc> Yes there are three
13:16:01 <arisut_> probably works only on iwamatsu beagleboard
13:16:02 <patersonc> oh, no working, sorry
13:16:23 <arisut_> currently is hard to look into it as cip lava have yet 500 internal server problems
13:16:28 <jki> yeah, and I don't see any failing bbb there
13:16:54 <arisut_> also x86_64 boards I see few time some success build
13:17:23 <arisut_> not sure why
13:18:15 <arisut_> for example de0-nano-soc worked with 6.12 cip but not with 6.1 cip
13:18:40 <arisut_> and 5.10 cip
13:19:07 <arisut_> https://lava.ciplatform.org/scheduler/job/1307554
13:20:01 <arisut_> https://lava.ciplatform.org/scheduler/alljobs?page=1&length=25&search=prod#table
13:20:15 <arisut_> you can see all productions jobs here
13:20:57 <patersonc> When the server behaves...
13:21:11 <jki> exactly... :(
13:21:24 <arisut_> if someone want to help give a look and do fixes, would be helpful
13:22:15 <patersonc> I'll try and find some patterns when it loads for me
13:22:23 <patersonc> On the topic of the server...
13:22:25 <arisut_> as now we have pratically all the platforms activated
13:22:41 <arisut_> patersonc, I see that on gitlab we are also testing on riscv
13:22:51 <arisut_> and pave1 is using it
13:23:01 <arisut_> we should enable it also on kernelci?
13:23:10 <patersonc> LAVA server: Looks like we're having the same issues as the other week with a lot of server requests causing very high server load. LF are investigating using CloudFlare to help protect the server.
13:23:36 <patersonc> arisut_: We can, but currently there is only 1 of the RZ/Five boards, so it's a bit of a risk
13:23:42 <iwamatsu__> for de0-nano-soc, I will take a look.
13:23:49 <arisut_> iwamatsu__, thanks
13:23:54 <arisut_> patersonc, ok
13:25:11 <patersonc> Also, RZ/Five doesn't used a standard rootfs so would require more work there
13:25:27 <patersonc> It would be better for CIP to pick another risc-v board as a reference platform
13:26:09 <jki> well, VisionFive 2? but that's like choosing an RPi as reference
13:26:56 <patersonc> It's an option, and I think it's running mainline okay these days?
13:27:19 <iwamatsu__> I am using Beagle-V. It is good status.
13:27:23 <patersonc> I don't know if it was around for 6.1 though? But then if it's not, no other boards would be either
13:27:27 <jki> widely, but I didn't track the last mile in the last year
13:27:33 <arisut_> patersonc, kernelCI already have some other riscv board
13:27:39 <arisut_> we could enable that
13:27:43 <jki> for 6.12, likely not 6.1
13:29:10 <jki> BeagleV-Fire?
13:29:11 <arisut_> jh7100-starfive-visionfive-v1 and jh7110-starfive-visionfive-2-v1-3b
13:29:12 <patersonc> KernelCI have some visionfive 2 boards by the looks of it
13:29:40 <jki> vf-v2, not v1 anymore
13:29:59 <arisut_> spacemit-k1-bananapi-f3  sun20i-d1-nezha
13:32:08 <jki> if we have a concret proposal, or at least a short-list: discuss in next TSC meeting?
13:32:25 <patersonc> What SoC is the most "standard" risc-v?
13:32:38 <patersonc> We should avoid "interesting" designs :P
13:34:18 <jki> definitely...
13:34:48 <jki> patersonc: would you drive this further from the testing wg?
13:35:17 <patersonc> I can try and put a shortlist together, but I don't know much about risc-v :P
13:36:29 <jki> then collecting individual experiences with boards and upstream kernels would be step 1
13:37:00 <arisut_> maybe we should also try to see which kernelci riscv boards works with cip
13:37:01 <jki> also, if kernelci is testing boards, we can check, in which constellations
13:37:08 <jki> exactly
13:38:18 <arisut_> I can send a PR for kernelci and check what is working
13:38:32 <patersonc> Thanks Arisu-san
13:40:14 <jki> regarding adding another openblocks from the denx set
13:40:35 <jki> turned out that this needs a bit of infrastructure update on our side first
13:41:02 <jki> we can do if start of shipping the whole thing should take longer
13:41:35 <jki> otherwise, we can discuss the timeline at next TSC as well
13:42:13 <patersonc> Yes I think we need to discuss a new lab(s) next week
13:42:35 <arisut_> wow
13:43:26 <jki> other testing topics for today?
13:43:45 <patersonc> Just "sorry" for the poor server performance and mayhem
13:44:14 <jki> are sending the requests in fact? :)
13:44:38 <jki> challenging times for hosting websites...
13:44:52 <jki> ok, then move on
13:44:56 <jki> 5
13:44:57 <jki> 4
13:44:59 <jki> 3
13:45:00 <jki> 2
13:45:02 <jki> 1
13:45:03 <jki> #topic AOB
13:46:01 <jki> anything else?
13:46:23 <jki> 5
13:46:25 <jki> 4
13:46:27 <jki> 3
13:46:28 <jki> 2
13:46:30 <jki> 1
13:46:32 <jki> #endmeeting