12:03:18 <iwamatsu> #startmeeting CIP IRC weekly meeting
12:03:18 <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:18 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:03:18 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
12:03:34 <iwamatsu> #topic AI review
12:03:41 <iwamatsu> No AI today
12:03:55 <iwamatsu> 5
12:03:58 <iwamatsu> 4
12:03:59 <iwamatsu> 3
12:04:02 <iwamatsu> 2
12:04:03 <iwamatsu> 1
12:04:09 <iwamatsu> #topic Kernel maintenance updates
12:04:21 <pave1> I was reviewing 6.12.60 and 6.12.61.
12:04:25 <masami> This week reported 0 new CVEs and 2 updated CVEs.
12:04:51 <iwamatsu> I reviewed 6.12.58 and 59.
12:05:16 <iwamatsu> anyone else ?
12:05:23 <iwamatsu> 5
12:05:25 <iwamatsu> 4
12:05:27 <iwamatsu> 3
12:05:29 <iwamatsu> 2
12:05:30 <iwamatsu> 1
12:05:40 <iwamatsu> #topic Kernel testing
12:06:14 <iwamatsu> linux-4.19.y-cip-rt is late.
12:06:25 <pave1> Kernel testing -- https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/12320883271
12:06:34 <patersonc> Some more KernelCI pipeline improvements have been merged. Not sure if they've hit production yet. I'm still working on the RT side of things
12:06:49 <patersonc> New lab-cip-cariad is online
12:06:54 <arisut> working on kci-dev and presentation
12:07:00 <pave1> -- qemu says it does not have movbe required to run that kernel.
12:07:14 <pave1> Any ideas what is going on there?
12:07:58 <patersonc> Strange
12:08:11 <patersonc> Same "machine" is happy with the arm64 build
12:09:37 <pave1> Code I'm testing is not touching x86, so this is strange. But it does not really look random glitch.
12:10:08 <patersonc> Probably a lava issue tbh
12:10:12 <patersonc> rather than kernel
12:11:09 <pave1> Aha, ok. I would not mind if someone took a look :-).
12:12:52 <iwamatsu> Let's check if this happens with QEMU in other labs.
12:13:18 <iwamatsu> anything else?
12:13:27 <iwamatsu> 5
12:13:28 <iwamatsu> 4
12:13:29 <iwamatsu> 3
12:13:31 <iwamatsu> 2
12:13:32 <iwamatsu> 1
12:14:45 <iwamatsu> I mistook. next is Kernel maintenance updates
12:14:47 <iwamatsu> #topic Kernel maintenance updates
12:14:48 <patersonc> Same qemu job in:
12:14:48 <patersonc> renesas lab: https://lava.ciplatform.org/scheduler/job/1341501 (PASS)
12:14:48 <patersonc> iwamatsu lab: https://lava.ciplatform.org/scheduler/job/1341502 (PASS)
12:14:48 <patersonc> cariad lab: https://lava.ciplatform.org/scheduler/job/1341503 (PASS)
12:14:56 <iwamatsu> #topic Kernel maintenance updates
12:15:10 <pave1> I'm working on 4.19-rt.
12:15:14 <iwamatsu> linux-4.19.y-cip-rt is late.
12:15:20 <iwamatsu> Pave1: thanks!
12:15:32 <pave1> I hit merge conflict in cgroups, and am not quite sure what to do with it.
12:16:19 <pave1> Basically it looks like -rt changed locking, while -stable split the workqueue to three pieces.
12:18:08 <pave1> I can easily drop the conlicting patch from -stable, and release that, but...
12:18:25 <iwamatsu> Other one, I think it would be best to ask on RT ML...
12:20:01 <iwamatsu> other kernels are green.
12:20:25 <pave1> Yep, there's also chance newer -rts already had to solve this somehow.
12:20:32 <pave1> So I'll investigate more.
12:20:50 <iwamatsu> pave1: OK, thanks!
12:21:00 <iwamatsu> anything else?
12:21:03 <iwamatsu> 5
12:21:05 <iwamatsu> 4
12:21:07 <iwamatsu> 3
12:21:09 <iwamatsu> 2
12:21:11 <iwamatsu> 1
12:21:16 <iwamatsu> #topic AOB
12:21:55 <masami> I 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/105891053
12:23:14 <masami> it seems as if some configuration problem.
12:23:26 <masami> at the time
12:24:22 <pave1> That's the same error as https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2195944203
12:24:37 <iwamatsu> masami: I see, I will check it. Thanks for your information.
12:24:58 <masami> iwamatsu: thank you!
12:25:21 <patersonc> masami: That mail thread says it was a kernel config issue with the merged CIP config
12:26:24 <patersonc> But then why would it fail in only one lab?
12:27:38 <iwamatsu> We might need to investigate a bit more.
12:27:49 <iwamatsu> Hi Jan.
12:28:35 <jki> hi!
12:28:45 <jki> trying to catch up from the logs...
12:29:24 <jki> regarding the kernel configuration issue: see what we also had to do for qemu testing with cip-core
12:29:42 <jki> 6.12 merged_defconfig is more demanding than previous versions
12:30:26 <jki> might be that individual configs we had in, say, 6.1 are still missing in 6.12 and do not affect the merged result therefor
12:32:53 <jki> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/cc93d81b9b6b5cc6c4ae3631bdee8d9f54a6be1a
12:32:55 <iwamatsu> I see. but why does the problem occur only with qemu-03?
12:33:10 <jki> is that qemu tcg or kvm?
12:33:20 <jki> if kvm, which cpu model?
12:33:21 <jki> host?
12:34:08 <jki> "host" makes things non-comparable CPU feature-wise
12:35:31 <masami> from lava log: "Boot command: /usr/bin/qemu-system-x86_64 -cpu host -enable-kvm"
12:36:07 <jki> bingo
12:36:15 <jki> different host, different features then
12:36:16 <iwamatsu> OK. we need to confirm Toyooka-san.
12:37:58 <jki> other AOB: do you already have topics for the ETSC call on the radar?
12:38:33 <jki> well, "already" is relative - it's already next week :D
12:39:14 <iwamatsu> Not yet.
12:39:34 <pave1> Not really.
12:41:03 <pave1> jki: 4.19-rt: I hit fun with cgroups.
12:41:21 <jki> are you trying to backport the issue I reported
12:41:22 <jki> ?
12:41:31 <jki> or even yet another topic?
12:41:35 <pave1> That's likely different topic.
12:41:41 <jki> :(
12:42:17 <jki> please share more information then, we can try to look into this
12:42:22 <patersonc> jki: Could you share Jason's email address with me? (privately) I want to chase about the B-VFire boards
12:42:24 <jki> minimum is understanding what is affected
12:42:47 <jki> patersonc: sure
12:43:01 <pave1> It is easy to drop the patch from -cip-rt for now, and have a release today/tommorow.
12:43:02 <patersonc> Thanks
12:43:13 <pave1> Or I can try to figure it out, perhaps asking for help on lists.
12:44:05 <iwamatsu> other topics for today?
12:44:21 <iwamatsu> 5
12:44:23 <iwamatsu> 4
12:44:24 <iwamatsu> 3
12:44:27 <iwamatsu> 2
12:44:28 <iwamatsu> 1
12:44:40 <iwamatsu> #endmeeting