13:02:59 <jki> #startmeeting CIP IRC weekly meeting 13:02:59 <collab-meetbot`> Meeting started Thu Jul 17 13:02: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:02:59 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:59 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting' 13:03:04 <jki> #topic AI review 13:03:09 <jki> -none- 13:03:15 <jki> 5 13:03:17 <jki> 4 13:03:18 <jki> 3 13:03:19 <jki> 2 13:03:21 <jki> 1 13:03:22 <jki> #topic Kernel maintenance updates 13:03:35 <pave1> I was doing reviews - 6.12.37 and .39. 13:03:35 <masami> This week reported 84 new CVEs and 16 updated CVEs. 13:03:39 <uli_> i pushed 4.19 earlier today, 4.4 is next 13:04:07 <pave1> uli: Thanks for a release. I guess I should do -rt release on top of that. 13:04:11 <iwamatsu__> I reviewing 6.12.37 13:04:18 <uli_> welcome 13:06:19 <jki> anything to add? 13:06:38 <jki> 5 13:06:41 <jki> 4 13:06:42 <jki> 3 13:06:44 <jki> 2 13:06:46 <jki> 1 13:06:48 <jki> #topic Kernel release status 13:06:59 <jki> two kernels are currently late 13:07:35 <jki> or was 4.19 now released? 13:07:42 <uli_> it was, see above 13:07:51 <jki> ah, now I see :) 13:08:01 <jki> what about 5.10-rt? 13:08:31 <pave1> Let me check. 13:09:21 <pave1> Actually, let me check after the meeting. 13:09:44 <jki> ok, the tool says it was due on the 14th 13:10:02 <jki> then please check if we are missing anything for it - thanks! 13:10:11 <jki> anything else on releases? 13:10:40 <jki> 5 13:10:42 <jki> 4 13:10:43 <jki> 3 13:10:45 <jki> 2 13:10:47 <jki> 1 13:10:50 <jki> #topic Kernel testing 13:11:05 <patersonc> Nothing from me 13:11:35 <arisut> We got 6.1 and 6.12 working on KernelCI with cip configurations but still missing 5.15 13:11:47 <arisut> not sure why, currently checking 13:12:08 <arisut> also still working on adding the CIP laboratory boards to KernelCI 13:12:10 <pave1> Failures such as this -- https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.4.y -- I assume are not real? 13:13:45 <arisut> example of 6.1.y-cip running with cip configurations https://dashboard.kernelci.org/tree/cip/linux-6.1.y-cip/6fd9f5d39d93831ca6f2cef099a6a2a1b9feaa80 13:14:05 <patersonc> pave1: Looks like NFS is failing to mount on openblocks-iot-vx2-01 13:14:09 <arisut> defconfig+allnoconfig+cip://6.1.y-cip/arm64/qemu_arm64_defconfig 13:14:40 <arisut> x86_64_defconfig+allnoconfig+cip://6.1.y-cip/x86/cip_qemu_defconfig 13:14:49 <patersonc> pave1: It's working today though by the looks of it? 13:15:04 <arisut> multi_v7_defconfig+allnoconfig+cip://6.1.y-cip/arm/qemu_arm_defconfig 13:15:06 <pave1> patersonc: Would you place your bets in "stable broke networking in the kernel" or "mouse ate the cabling"? 13:15:18 <iwamatsu__73> openblocks-iot-vx2 does not work ethernet device. 13:16:18 <jki> and that is a regression? 13:16:43 <pave1> iwamatsu: As in "kernel bug", "broken hw" or "bad setup in test lab"? 13:18:32 <patersonc> Seems to work for some kernel configs/kernels and not others: https://lava.ciplatform.org/scheduler/device_type/x86-openblocks-iot-vx2 13:18:41 <iwamatsu__73> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-5.4.y all fail. 13:19:08 <patersonc> CIP kernels okay. stable kernels not okay? 13:20:12 <pave1> Is vx2 new addition to stable kernel testing? 13:20:38 <iwamatsu__73> If I remember correctly, it is a kernel config issue. 13:20:47 <jki> maybe yet another cip-kernel-config fallout? 13:21:07 <jki> we had/have too many of them in broken states 13:21:44 <iwamatsu__73> I will check the config and modify it to work with the LTS kernel as well. 13:22:10 <pave1> 5.15 has the same problem. 5.10 works ok on -stable. 13:22:18 <jki> we really need to get rid of these intermediate configs, maybe only maintain fixups for them up to the next cip kernel 13:22:25 <jki> no one looks at them in practice 13:22:45 <jki> that's basically my AOB topic :) 13:23:29 <jki> anything to add regarding testing? 13:24:04 <jki> 5 13:24:06 <jki> 4 13:24:08 <jki> 3 13:24:10 <jki> 2 13:24:11 <jki> 1 13:24:14 <jki> #topic AOB 13:24:31 <pave1> I'll be travelling next week. 13:24:48 <jki> and I will be offline next two weeks 13:25:00 <jki> who can take over? 13:26:17 <iwamatsu__73> I can takeover. 13:26:33 <jki> thanks in advance! 13:26:39 <iwamatsu__73> :-) 13:26:52 <jki> "further workflow improvements for cip-kernel-config" 13:27:24 <jki> I expressed one concern already, and we have the autogeneration of merged defconfig changes in the pipeline 13:27:34 <jki> what do others think about this? 13:28:12 <arisut> nice 13:28:53 <iwamatsu__73> I will merge it after this meeting. 13:29:27 <iwamatsu__73> Regarding maintenance of configs. 13:29:56 <iwamatsu__73> (VX2 and others) perhaps the 4.19.y config fixes are not reflected in the back LTS such as 5.4. 13:30:19 <iwamatsu__73> I will work on this. 13:30:38 <jki> yeah, it might be that 4.19 wasn't enbled for that hardware originally 13:31:17 <jki> more common was the issue that we didn't have features added in 6.1-cip and older in the stable configs that fed 6.12-cip 13:33:13 <jki> do you think we should address this automated or better via review in the future? 13:33:32 <iwamatsu__73> Yes, that is correct. Since that work is missing, I will check the commit and update it. 13:34:36 <iwamatsu__73> Perhaps it would be easier to do with review. 13:35:11 <jki> initially, sure 13:35:38 <jki> but it puts more load on config contributors and on the reviewer 13:37:14 <iwamatsu__73> Yes, I would like to create and automate a checking and upodate tool or CI. I plan to do this as well. 13:37:51 <jki> that would be great - maybe sync with Quirin, already discussed some ideas with him 13:37:59 <iwamatsu__73> nice 13:38:37 <jki> ok - any other businesses for today? 13:39:15 <jki> 5 13:39:17 <jki> 4 13:39:19 <jki> 3 13:39:20 <jki> 2 13:39:21 <jki> 1 13:39:23 <jki> #endmeeting