Thursday, 2025-12-04

*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip07:04
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Read error: No route to host)07:06
*** monstr_ <monstr_!~monstr@nat-108f.starnet.cz> has joined #cip07:06
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has quit IRC (Quit: Konversation terminated!)07:09
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has joined #cip07:09
*** monstr_ <monstr_!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds)07:15
*** iwamatsu <iwamatsu!~iwamatsu@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip11:57
*** masami <masami!~masami@FL1-125-197-94-238.tky.mesh.ad.jp> has joined #cip11:59
iwamatsuHi12:01
masamihello12:01
pave1Hi!12:01
patersoncHey12:02
iwamatsuJan can not join today.  So, lets start.12:03
iwamatsu#startmeeting CIP IRC weekly meeting12:03
collab-meetbot`Meeting started Thu Dec  4 12:03:18 2025 UTC and is due to finish in 60 minutes.  The chair is iwamatsu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:03
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:03
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:03
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:03
iwamatsu#topic AI review12:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:03
iwamatsuNo AI today12:03
iwamatsu512:03
iwamatsu412:03
iwamatsu312:03
iwamatsu212:04
iwamatsu112:04
iwamatsu#topic Kernel maintenance updates12:04
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:04
pave1I was reviewing 6.12.60 and 6.12.61.12:04
masamiThis week reported 0 new CVEs and 2 updated CVEs.12:04
iwamatsuI reviewed 6.12.58 and 59.12:04
iwamatsu anyone else ?12:05
iwamatsu512:05
iwamatsu412:05
iwamatsu312:05
iwamatsu212:05
iwamatsu112:05
iwamatsu#topic Kernel testing12:05
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:05
iwamatsulinux-4.19.y-cip-rt is late.12:06
pave1Kernel testing -- https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1232088327112:06
patersoncSome more KernelCI pipeline improvements have been merged. Not sure if they've hit production yet. I'm still working on the RT side of things12:06
patersoncNew lab-cip-cariad is online12:06
arisutworking on kci-dev and presentation12:06
pave1-- qemu says it does not have movbe required to run that kernel.12:07
pave1Any ideas what is going on there?12:07
patersoncStrange12:07
patersoncSame "machine" is happy with the arm64 build12:08
pave1Code I'm testing is not touching x86, so this is strange. But it does not really look random glitch.12:09
patersoncProbably a lava issue tbh12:10
patersoncrather than kernel12:10
pave1Aha, ok. I would not mind if someone took a look :-).12:11
iwamatsuLet's check if this happens with QEMU in other labs.12:12
iwamatsuanything else?12:13
iwamatsu512:13
iwamatsu412:13
iwamatsu312:13
iwamatsu212:13
iwamatsu112:13
iwamatsuI mistook. next is Kernel maintenance updates12:14
iwamatsu #topic Kernel maintenance updates12:14
patersoncSame qemu job in:12:14
patersoncrenesas lab: https://lava.ciplatform.org/scheduler/job/1341501 (PASS)12:14
patersonciwamatsu lab: https://lava.ciplatform.org/scheduler/job/1341502 (PASS)12:14
patersonccariad lab: https://lava.ciplatform.org/scheduler/job/1341503 (PASS)12:14
iwamatsu#topic Kernel maintenance updates12:14
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:14
pave1I'm working on 4.19-rt.12:15
iwamatsulinux-4.19.y-cip-rt is late.12:15
iwamatsuPave1: thanks!12:15
pave1I hit merge conflict in cgroups, and am not quite sure what to do with it.12:15
pave1Basically it looks like -rt changed locking, while -stable split the workqueue to three pieces.12:16
pave1I can easily drop the conlicting patch from -stable, and release that, but...12:18
iwamatsuOther one, I think it would be best to ask on RT ML...12:18
iwamatsuother kernels are green.12:20
pave1Yep, there's also chance newer -rts already had to solve this somehow.12:20
pave1So I'll investigate more.12:20
iwamatsupave1: OK, thanks!12:20
iwamatsuanything else?12:21
iwamatsu512:21
iwamatsu412:21
iwamatsu312:21
iwamatsu212:21
iwamatsu112:21
iwamatsu#topic AOB12:21
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:21
masamiI found talking about "This kernel requires the following features not present on the CPU: movbe" in archive https://lists.cip-project.org/g/cip-dev/topic/generic_x86_kernel/10589105312:21
masamiit seems as if some configuration problem.12:23
masamiat the time12:23
pave1That's the same error as https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/219594420312:24
iwamatsumasami: I see, I will check it. Thanks for your information.12:24
masamiiwamatsu: thank you!12:24
patersoncmasami: That mail thread says it was a kernel config issue with the merged CIP config12:25
patersoncBut then why would it fail in only one lab?12:26
*** jki <jki!~jki@88.128.94.16> has joined #cip12:27
iwamatsuWe might need to investigate a bit more.12:27
iwamatsuHi Jan.12:27
jkihi!12:28
jkitrying to catch up from the logs...12:28
jkiregarding the kernel configuration issue: see what we also had to do for qemu testing with cip-core12:29
jki6.12 merged_defconfig is more demanding than previous versions12:29
jkimight be that individual configs we had in, say, 6.1 are still missing in 6.12 and do not affect the merged result therefor12:30
jkihttps://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/cc93d81b9b6b5cc6c4ae3631bdee8d9f54a6be1a12:32
iwamatsuI see. but why does the problem occur only with qemu-03?12:32
jkiis that qemu tcg or kvm?12:33
jkiif kvm, which cpu model?12:33
jkihost?12:33
jki"host" makes things non-comparable CPU feature-wise12:34
masamifrom lava log: "Boot command: /usr/bin/qemu-system-x86_64 -cpu host -enable-kvm"12:35
jkibingo12:36
jkidifferent host, different features then12:36
iwamatsuOK. we need to confirm Toyooka-san.12:36
jkiother AOB: do you already have topics for the ETSC call on the radar?12:37
jkiwell, "already" is relative - it's already next week :D12:38
iwamatsuNot yet.12:39
pave1Not really.12:39
pave1jki: 4.19-rt: I hit fun with cgroups.12:41
jkiare you trying to backport the issue I reported12:41
jki?12:41
jkior even yet another topic?12:41
pave1That's likely different topic.12:41
jki:(12:41
jkiplease share more information then, we can try to look into this12:42
patersoncjki: Could you share Jason's email address with me? (privately) I want to chase about the B-VFire boards12:42
jkiminimum is understanding what is affected12:42
jkipatersonc: sure12:42
pave1It is easy to drop the patch from -cip-rt for now, and have a release today/tommorow.12:43
patersoncThanks12:43
pave1Or I can try to figure it out, perhaps asking for help on lists.12:43
iwamatsuother topics for today?12:44
iwamatsu512:44
iwamatsu412:44
iwamatsu312:44
iwamatsu212:44
iwamatsu112:44
iwamatsu#endmeeting12:44
collab-meetbot`Meeting ended Thu Dec  4 12:44:40 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:44
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-04-12.03.html12:44
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-04-12.03.txt12:44
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/12/cip.2025-12-04-12.03.log.html12:44
*** 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/"12:44
jkithanks, bye!12:44
pave1thank you!12:45
iwamatsuThnak you!12:45
masamithank you12:45
*** jki <jki!~jki@88.128.94.16> has quit IRC (Quit: Leaving)12:45
patersoncSee you next week12:45
patersoncI assume we'll cancel this meeting next week?12:45
*** masami <masami!~masami@FL1-125-197-94-238.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:45
pave1patersonc: Does it collide with E-STC?12:46
pave1E-STC?12:46
pave1E-TSC?12:46
*** iwamatsu <iwamatsu!~iwamatsu@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Ping timeout: 246 seconds)12:49
patersoncMaybe12:58
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has quit IRC (Quit: Konversation terminated!)13:15
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip13:22
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has quit IRC (Ping timeout: 240 seconds)18:11
*** rajm <rajm!~robert@host-80-41-206-202.as13285.net> has joined #cip18:11

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