Thursday, 2025-09-04

« Wednesday, 2025-09-03 Index Friday, 2025-09-05 »
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:59
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)06:20
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip06:51
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)07:02
*** tmerciai <tmerciai!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has joined #cip07:06
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip08:23
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)08:54
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip10:32
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has joined #cip12:57
arisuthi12:58
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip12:58
masamihello13:00
*** jki <jki!~jki@195.145.170.167> has joined #cip13:00
ulihello13:00
jkihi all13:00
pave1Hi!13:00
masamihi13:00
patersoncAfternoon13:00
jkithen let's start13:00
jki#startmeeting CIP IRC weekly meeting13:00
collab-meetbotMeeting started Thu Sep  4 13:00:59 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:00
jki#topic AI review13:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jkicurrently none recorded13:01
jki513:01
jki413:01
jki313:01
jki213:01
jki113:01
jki#topic Kernel maintenance updates13:01
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:01
ulii released 4.413:01
masamiThis week reported 3 new CVEs and 103 updated CVEs.13:01
pave1I'm doing reviews, 6.1.44 and .45.13:02
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has joined #cip13:02
iwamatsu_hello13:02
jkihi! we are at maintenance updates already13:03
iwamatsu_I reviewed 6.12.42 and 43,13:04
arisutcurrently kernel upstream is releasing new kernel as we talk 5.15.191,5.10.242, 5.4.29813:04
arisutfyi13:04
*** iwamatsu_7 <iwamatsu_7!~iwamatsu_@155.190.52.56> has joined #cip13:05
jkiany further updates?13:06
*** iwamatsu_7 <iwamatsu_7!~iwamatsu_@155.190.52.56> has quit IRC (Client Quit)13:07
*** iwamatsu_45 <iwamatsu_45!~iwamatsu_@155.190.52.56> has joined #cip13:07
*** iwamatsu_45 is now known as iwamatsu__13:07
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel release status13:07
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:07
jki4.4-rt is late IIRC13:07
pave1Yep, sorry about that. I don't foresee problems, should do it on friday or over weekend.13:08
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:09
jkiperfect13:09
jkianything else on this?13:09
jki513:09
jki413:09
jki313:09
jki213:10
jki113:10
jki#topic Kernel testing13:10
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:10
arisuto/13:10
arisutabout release we have a way to mask problematic cip kernel ?13:10
pave1Does that have anything to do with "currently upstream is releasing 5.4.298" announcement? :-)13:11
arisutin the case that the kernel have build issues or similar13:11
arisutjust asking13:11
pave1Not really, it may depend on severity.13:12
arisutI see, thanks13:12
arisutmaybe could be useful to have something to indicate that a version have serious problems13:14
patersoncOn the testing side of things, we've got some really high load on the LAVA server which is causing some issues13:14
arisutI talked with collabora about the issues and they are willing to share some filtering script13:15
arisutproblem is that we don't have root access to lava-cip servers13:15
patersoncindeed13:15
arisut:(13:16
arisutanother solution could be to ask LF to set cloudfare13:16
arisutthey already using it for kernel.org13:16
arisutprobably is the fastest solution as LF have already experience with that13:16
patersoncYea13:17
arisutqq13:17
patersoncI'll keep trying to narrow down the issue and talk to LF in tandem13:17
arisutalso broonie is using it for his lava server13:17
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has joined #cip13:17
arisutqq <- writing on the wrong keyboard lol13:17
*** iwamatsu_96 <iwamatsu_96!~iwamatsu_@155.190.52.56> has joined #cip13:18
*** iwamatsu_96 is now known as iwamatsu13:18
jkipatersonc: no one reacted on your lava load issue yet, right?13:19
patersoncNope. ALthough Cybertrust lab admin said it wasn't them13:19
pave1patersonc: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2021753921 I'm having more problems than usual with testing. Is that related / likely to get better on its own?13:19
jkiwe cannot identify the source??13:20
jkido all workers share the same token?13:20
arisutcollabora said is a know issue, there are some bots that are causing problems with lava13:20
jkiAI crawlers again, nothing authenticated?13:20
patersoncIt could just be web traffic, rather than api13:21
*** iwamatsu__ <iwamatsu__!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:21
jkican we close the web interface without affecting the API?13:21
arisutwithout server access we can only suppose13:21
jkiat least temporarily13:21
jkioh, that was the missing root access?!13:22
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:22
jkiwho has then, LF admins?13:22
arisutyes13:22
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has joined #cip13:22
jki-> LF ticket?13:22
patersoncI've already got a discussion open with our usual LF IT contactr13:23
jkiok13:23
arisutpatersonc, thanks !13:23
jkiguess we have to wait and see then...13:24
jkiother testing topics?13:25
patersoncFor now, kernel testing may take a hit. There are still some labs offline since I rebooted the LAVA master13:25
pave1Ok. I'll hit retry few more times ;).13:25
arisutI'm starting to add nfsrootfs build and x86 platforms13:25
jkionly one is offline right now, iwamatsu's13:26
*** iwamatsu <iwamatsu!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:26
jkibut several in "maintenance" state - is that what you mean?13:27
patersoncYea13:27
iwamatsu_maybe other lab does not reconnect yet.13:27
patersoncI put them all into maintenance until the lab owners reboot the labs13:27
patersoncLAVA doesn't like it when the server reboots. The labs don't automatically start working again - they want a reboot too13:28
jkidid you inform all lab owners already?13:28
patersoncYes13:28
arisutpatersonc, beaglebone could boot with nfsrootfs https://lava.ciplatform.org/scheduler/job/130545813:29
arisutbut we have still problems with r8a7743-iwg20d-q7 https://lava.ciplatform.org/scheduler/job/130545913:29
patersoncThanks arisut13:29
*** iwamatsu_89 <iwamatsu_89!~iwamatsu_@155.190.52.56> has joined #cip13:29
*** iwamatsu_89 is now known as iwamatsu13:29
arisutmaybe we could add some boot commands?13:30
arisutI see there is a  extra_kernel_args: lsm=capability,landlock,yama,loadpin,safesetid,selinux,bpf on some nfs machine13:30
patersoncI've never set those for the iwg20d boards before13:31
arisuton the collabora boards13:31
arisutmaybe we need something similar13:31
arisutI will investigate difference on the build13:31
patersoncThanks13:32
arisutnp13:32
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:32
iwamatsuit can not boot with zImage13:32
patersoncWe need to work out why zimage isn't working13:33
iwamatsuiwg20d need to use uImage with default bootloader13:33
patersoncArisut is there a way to get uimage out of kernelci?13:33
iwamatsumeybe it depends on address of boot imge.13:34
arisutpatersonc, I doubt :/ will check13:34
patersoncThanks13:35
arisutit cannot work with zimage or maybe it could work but is not tested ?13:35
patersoncMaybe we just need to check the uboot command13:36
arisutok13:36
arisutI will check about using uimage13:37
arisutlooks like we have a make target for uimage13:37
iwamatsuI think the bootloader didn't support zImage...13:37
arisutI hope that is still working on pipeline but looks like is not used anymore13:38
arisutI will check how to make it throw uimage13:38
arisutthanks13:39
patersoncThanks13:39
jkipatersonc: it's likely hopeless to wait for a denx lab reboot - just set it to active again and pray ;)13:39
patersoncyea13:39
jkiQuirin set both our labs to active as well - works without rebooting13:40
jkimaybe that issue was with older lava13:40
pave1jki: I can try to ask for reboot -- should I?13:40
jkipavel: only if we see issues, I would say13:40
patersoncjki: The issue is that the LAVA_DISPATCHER_IP variable doesn't get set. So NFS jobs will fail13:40
pave1jki: ok.13:40
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has joined #cip13:43
jkipatersonc: does not seem to be the case for our labs13:43
*** iwamatsu <iwamatsu!~iwamatsu_@155.190.52.56> has quit IRC (Ping timeout: 250 seconds)13:46
patersoncokay13:46
patersoncI'll keep an eye on it13:46
jkiyeah, just ping us13:46
jkimore testing topics?13:47
jki513:47
jki413:47
jki313:47
jki213:47
jki113:47
jki#topic AOB13:47
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:47
masamiI will be absent  next week13:48
patersoncSame here13:49
jkiok13:50
jkianything else for today?13:50
jki513:51
jki413:51
jki313:51
jki213:51
jki113:51
jki#endmeeting13:51
collab-meetbotMeeting ended Thu Sep  4 13:51:19 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:51
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-04-13.00.html13:51
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-04-13.00.txt13:51
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-04-13.00.log.html13:51
*** 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:51
jkithanks all!13:51
ulithanks13:51
iwamatsu_thank you13:51
masamithank you13:51
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:51
*** iwamatsu_ <iwamatsu_!~iwamatsu_@155.190.52.56> has quit IRC (Quit: Client closed)13:52
pave1Thank you!13:52
patersoncCheers13:52
*** jki <jki!~jki@195.145.170.167> has quit IRC (Quit: Leaving)13:53
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)14:07
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip14:21
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)15:50
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has left #cip20:48
« Wednesday, 2025-09-03 Index Friday, 2025-09-05 »

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