Thursday, 2025-07-17

*** monstr <monstr!~monstr@nat-108.starnet.cz> has joined #cip05:31
*** monstr <monstr!~monstr@nat-108.starnet.cz> has quit IRC (Ping timeout: 252 seconds)05:36
*** monstr <monstr!~monstr@nat-108.starnet.cz> has joined #cip08:02
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 252 seconds)08:55
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip08:56
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Read error: Connection reset by peer)08:57
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip09:00
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has joined #cip12:50
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip12:57
*** jki <jki!~jki@2a00:5881:3041:2700:dd4d:23bd:b9d5:977f> has joined #cip13:01
jkihi all13:01
uli_hello13:01
pave1Hi!13:01
masamihello13:01
iwamatsu__hello13:02
jki#startmeeting CIP IRC weekly meeting13:02
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
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki-none-13:03
jki513:03
jki413:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
pave1I was doing reviews - 6.12.37 and .39.13:03
masamiThis week reported 84 new CVEs and 16 updated CVEs.13:03
uli_i pushed 4.19 earlier today, 4.4 is next13:03
pave1uli: Thanks for a release. I guess I should do -rt release on top of that.13:04
iwamatsu__I reviewing 6.12.3713:04
uli_welcome13:04
jkianything to add?13:06
jki513:06
jki413:06
jki313:06
jki213:06
jki113:06
jki#topic Kernel release status13:06
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:06
jkitwo kernels are currently late13:06
jkior was 4.19 now released?13:07
uli_it was, see above13:07
jkiah, now I see :)13:07
jkiwhat about 5.10-rt?13:08
pave1Let me check.13:08
pave1Actually, let me check after the meeting.13:09
jkiok, the tool says it was due on the 14th13:09
jkithen please check if we are missing anything for it - thanks!13:10
jkianything else on releases?13:10
*** iwamatsu__73 <iwamatsu__73!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip13:10
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Ping timeout: 272 seconds)13:10
jki513:10
jki413:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel testing13:10
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:10
patersoncNothing from me13:11
arisutWe got 6.1 and 6.12 working on KernelCI with cip configurations but still missing 5.1513:11
arisutnot sure why, currently checking13:11
arisutalso still working on adding the CIP laboratory boards to KernelCI13:12
pave1Failures 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:12
arisutexample of 6.1.y-cip running with cip configurations https://dashboard.kernelci.org/tree/cip/linux-6.1.y-cip/6fd9f5d39d93831ca6f2cef099a6a2a1b9feaa8013:13
patersoncpave1: Looks like NFS is failing to mount on openblocks-iot-vx2-0113:14
arisutdefconfig+allnoconfig+cip://6.1.y-cip/arm64/qemu_arm64_defconfig13:14
arisutx86_64_defconfig+allnoconfig+cip://6.1.y-cip/x86/cip_qemu_defconfig13:14
patersoncpave1: It's working today though by the looks of it?13:14
arisutmulti_v7_defconfig+allnoconfig+cip://6.1.y-cip/arm/qemu_arm_defconfig13:15
pave1patersonc: Would you place your bets in "stable broke networking in the kernel" or "mouse ate the cabling"?13:15
iwamatsu__73openblocks-iot-vx2 does not work ethernet device.13:15
jkiand that is a regression?13:16
pave1iwamatsu: As in "kernel bug", "broken hw" or "bad setup in test lab"?13:16
patersoncSeems to work for some kernel configs/kernels and not others: https://lava.ciplatform.org/scheduler/device_type/x86-openblocks-iot-vx213:18
iwamatsu__73https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-5.4.y all fail.13:18
patersoncCIP kernels okay. stable kernels not okay?13:19
pave1Is vx2 new addition to stable kernel testing?13:20
iwamatsu__73If I remember correctly, it is a kernel config issue.13:20
jkimaybe yet another cip-kernel-config fallout?13:20
jkiwe had/have too many of them in broken states13:21
iwamatsu__73I will check the config and modify it to work with the LTS kernel as well.13:21
pave15.15 has the same problem. 5.10 works ok on -stable.13:22
jkiwe really need to get rid of these intermediate configs, maybe only maintain fixups for them up to the next cip kernel13:22
jkino one looks at them in practice13:22
jkithat's basically my AOB topic :)13:22
jkianything to add regarding testing?13:23
jki513:24
jki413:24
jki313:24
jki213:24
jki113:24
jki#topic AOB13:24
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:24
pave1I'll be travelling next week.13:24
jkiand I will be offline next two weeks13:24
jkiwho can take over?13:25
iwamatsu__73I can takeover.13:26
jkithanks in advance!13:26
iwamatsu__73:-)13:26
jki"further workflow improvements for cip-kernel-config"13:26
jkiI expressed one concern already, and we have the autogeneration of merged defconfig changes in the pipeline13:27
jkiwhat do others think about this?13:27
arisutnice13:28
iwamatsu__73I will merge it after this meeting.13:28
iwamatsu__73Regarding maintenance of configs.13:29
iwamatsu__73(VX2 and others) perhaps the 4.19.y config fixes are not reflected in the back LTS such as 5.4.13:29
iwamatsu__73I will work on this.13:30
jkiyeah, it might be that 4.19 wasn't enbled for that hardware originally13:30
jkimore 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-cip13:31
jkido you think we should address this automated or better via review in the future?13:33
iwamatsu__73Yes, that is correct. Since that work is missing,  I will check the commit and update it.13:33
iwamatsu__73Perhaps it would be easier to do with review.13:34
jkiinitially, sure13:35
jkibut it puts more load on config contributors and on the reviewer13:35
iwamatsu__73Yes, I would like to create and automate a checking  and upodate tool or CI. I plan to do this as well.13:37
jkithat would be great - maybe sync with Quirin, already discussed some ideas with him13:37
iwamatsu__73nice13:37
jkiok - any other businesses for today?13:38
jki513:39
jki413:39
jki313:39
jki213:39
jki113:39
jki#endmeeting13:39
collab-meetbot`Meeting ended Thu Jul 17 13:39:23 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:39
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-17-13.02.html13:39
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-17-13.02.txt13:39
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/07/cip.2025-07-17-13.02.log.html13:39
*** 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:39
jkithanks!13:39
arisutthx13:39
uli_thanks13:39
masamithank you13:39
iwamatsu__73Thank you13:39
*** masami <masami!~masami@FL1-125-194-6-184.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:39
pave1Thank you!13:39
*** jki <jki!~jki@2a00:5881:3041:2700:dd4d:23bd:b9d5:977f> has quit IRC (Quit: Leaving)13:39
*** iwamatsu__73 <iwamatsu__73!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)13:42
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 276 seconds)14:53
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.166> has joined #cip14:54
*** monstr <monstr!~monstr@nat-108.starnet.cz> has quit IRC (Remote host closed the connection)14:57
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.166> has quit IRC (Ping timeout: 260 seconds)15:01
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip15:01

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