Thursday, 2025-09-18

*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:34
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)05:39
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has joined #cip06:34
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection)06:34
*** tmerciai <tmerciai!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has joined #cip06:45
*** rajm <rajm!~robert@host-81-178-147-206.as13285.net> has quit IRC (Remote host closed the connection)07:04
*** rajm <rajm!~robert@host-81-178-147-206.as13285.net> has joined #cip07:05
*** tmerciai <tmerciai!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has quit IRC (Ping timeout: 256 seconds)07:07
*** tmerciai <tmerciai!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has joined #cip07:07
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip07:16
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has joined #cip12:55
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has joined #cip13:00
pave1Hi!13:00
iwamatsu__hello13:01
patersoncAfternoon13:01
masamihello13:01
*** jki <jki!~jki@195.145.170.179> has joined #cip13:03
jkihi all, sorry :(13:03
jkialready started?13:03
patersoncnope13:03
jkiok13:04
jki#startmeeting CIP IRC weekly meeting13:04
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
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:04
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:04
jki#topic AI review13:04
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:04
jki- start define a CIP kernel threat model [Pavel]13:04
jkipavel: any news?13:04
pave1 working on ha. first version is in git now13:05
jkiok - please once you like to have feedback13:05
pave1still need to spell check and send i to list13:05
jkiperfect13:05
jkinothing else on my list otherwise13:05
jki513:05
jki413:05
jki313:05
jki213:06
jki113:06
jki#topic Kernel maintenance updates13:06
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:06
masamiThis week reported 449 new CVEs and 1 updated CVEs.13:06
pave1I'm doing reviews, 6.12.47 is out now13:06
jkiulrich: "Working on 4.19 ATM, it'll probably be ready on Monday."13:06
iwamatsu__I reviewed 6.12.44 and reviewing 6.12.45.13:07
jkiok, anything to add?13:08
jki513:09
jki413:09
jki313:09
jki213:09
jki113:09
jki#topic Kernel release status13:09
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:09
jki4.19 is late but comming next week13:09
jki6.1-rt?13:10
pave16.1-rt is late, I am currently working on it.13:10
iwamatsu__Pave1: Thanks for relelase 6.1.y-cip.13:11
pave1shuld be later today if it passes testing.13:11
jkigreat13:11
jkiany issues otherwise?13:12
jki513:12
jki413:12
jki313:12
jki213:12
jki113:12
jki#topic Kernel testing13:12
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:12
arisut_https://dashboard.kernelci.org/tree/cip/linux-6.1.y-cip/668a07393455734b16b88d0c167bb0de35785251?p=bt we started to have boot results from KernelCI13:13
arisut_on production13:13
jkiok, mostly unavailable test hw, right?13:14
arisut_we have most of the cip lava platforms13:14
arisut_arm64 are working13:14
arisut_x86_64 and beaglebone are not working13:15
arisut_beaglebone i see it work few times13:15
jkino x86 targets13:15
patersoncYes there are three13:15
arisut_probably works only on iwamatsu beagleboard13:16
patersoncoh, no working, sorry13:16
arisut_currently is hard to look into it as cip lava have yet 500 internal server problems13:16
jkiyeah, and I don't see any failing bbb there13:16
arisut_also x86_64 boards I see few time some success build13:16
arisut_not sure why13:17
arisut_for example de0-nano-soc worked with 6.12 cip but not with 6.1 cip13:18
arisut_and 5.10 cip13:18
arisut_https://lava.ciplatform.org/scheduler/job/130755413:19
arisut_https://lava.ciplatform.org/scheduler/alljobs?page=1&length=25&search=prod#table13:20
arisut_you can see all productions jobs here13:20
patersoncWhen the server behaves...13:20
jkiexactly... :(13:21
arisut_if someone want to help give a look and do fixes, would be helpful13:21
patersoncI'll try and find some patterns when it loads for me13:22
patersoncOn the topic of the server...13:22
arisut_as now we have pratically all the platforms activated13:22
arisut_patersonc, I see that on gitlab we are also testing on riscv13:22
arisut_and pave1 is using it13:22
arisut_we should enable it also on kernelci?13:23
patersoncLAVA 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
patersoncarisut_: We can, but currently there is only 1 of the RZ/Five boards, so it's a bit of a risk13:23
iwamatsu__for de0-nano-soc, I will take a look.13:23
arisut_iwamatsu__, thanks13:23
arisut_patersonc, ok13:23
patersoncAlso, RZ/Five doesn't used a standard rootfs so would require more work there13:25
patersoncIt would be better for CIP to pick another risc-v board as a reference platform13:25
jkiwell, VisionFive 2? but that's like choosing an RPi as reference13:26
patersoncIt's an option, and I think it's running mainline okay these days?13:26
iwamatsu__I am using Beagle-V. It is good status.13:27
patersoncI don't know if it was around for 6.1 though? But then if it's not, no other boards would be either13:27
jkiwidely, but I didn't track the last mile in the last year13:27
arisut_patersonc, kernelCI already have some other riscv board13:27
arisut_we could enable that13:27
jkifor 6.12, likely not 6.113:27
jkiBeagleV-Fire?13:29
arisut_ jh7100-starfive-visionfive-v1 and jh7110-starfive-visionfive-2-v1-3b13:29
patersoncKernelCI have some visionfive 2 boards by the looks of it13:29
jkivf-v2, not v1 anymore13:29
arisut_spacemit-k1-bananapi-f3  sun20i-d1-nezha13:29
jkiif we have a concret proposal, or at least a short-list: discuss in next TSC meeting?13:32
patersoncWhat SoC is the most "standard" risc-v?13:32
patersoncWe should avoid "interesting" designs :P13:32
jkidefinitely...13:34
jkipatersonc: would you drive this further from the testing wg?13:34
patersoncI can try and put a shortlist together, but I don't know much about risc-v :P13:35
jkithen collecting individual experiences with boards and upstream kernels would be step 113:36
arisut_maybe we should also try to see which kernelci riscv boards works with cip13:37
jkialso, if kernelci is testing boards, we can check, in which constellations13:37
jkiexactly13:37
arisut_I can send a PR for kernelci and check what is working13:38
patersoncThanks Arisu-san13:38
jkiregarding adding another openblocks from the denx set13:40
jkiturned out that this needs a bit of infrastructure update on our side first13:40
jkiwe can do if start of shipping the whole thing should take longer13:41
jkiotherwise, we can discuss the timeline at next TSC as well13:41
patersoncYes I think we need to discuss a new lab(s) next week13:42
arisut_wow13:42
jkiother testing topics for today?13:43
patersoncJust "sorry" for the poor server performance and mayhem13:43
jkiare sending the requests in fact? :)13:44
jkichallenging times for hosting websites...13:44
jkiok, then move on13:44
jki513:44
jki413:44
jki313:44
jki213:45
jki113:45
jki#topic AOB13:45
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:45
jkianything else?13:46
jki513:46
jki413:46
jki313:46
jki213:46
jki113:46
jki#endmeeting13:46
collab-meetbot`Meeting ended Thu Sep 18 13:46:32 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-18-13.04.html13:46
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-18-13.04.txt13:46
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-18-13.04.log.html13:46
*** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"13:46
jkithanks!13:46
iwamatsu__Thank you13:46
pave1thank you!13:46
masamithank you13:46
patersoncCheers13:47
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:47
*** jki <jki!~jki@195.145.170.179> has quit IRC (Quit: Leaving)13:47
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)14:31
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection)14:56
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 248 seconds)21:18
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.164> has joined #cip21:19
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.164> has quit IRC (Ping timeout: 256 seconds)21:28
*** tmerciai <tmerciai!~tmerciai3@net-188-217-32-125.cust.vodafonedsl.it> has quit IRC (Ping timeout: 258 seconds)22:14

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!