13:02:10 <jki> #startmeeting CIP IRC weekly meeting
13:02:10 <collab-meetbot> Meeting started Thu Sep 11 13:02:10 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:10 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:10 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:21 <jki> #topic AI review
13:02:31 <jki> - start define a CIP kernel threat model [Pavel]
13:02:37 <jki> pavel: just in time :)
13:03:06 <pave1> Yep, I've got something. I'll get robot to comment on it and then get list to comment on it.
13:03:36 <jki> ok, we are looking forward
13:03:44 <jki> no other AIs recorded
13:03:50 <jki> 5
13:03:52 <jki> 4
13:03:54 <jki> 3
13:03:55 <jki> 2
13:03:57 <jki> 1
13:03:59 <jki> #topic Kernel maintenance updates
13:04:07 <uli> i'm working on 4.19
13:04:48 <iwamatsu__81> I am reviewing 6.12.44 and released 6.12.y-cip/
13:04:51 <pave1> Reviews, 6.12.45 and .46.
13:05:37 <pave1> I'm working on 5.10.241-cip64. 5 targets are down, but I guess I'll just release it, anyway.
13:05:51 <jki> further topics?
13:06:27 <jki> (regarding target, we can touch that under testing)
13:06:35 <pave1> Yep.
13:07:02 <jki> 5
13:07:03 <jki> 4
13:07:04 <jki> 3
13:07:06 <jki> 2
13:07:07 <jki> 1
13:07:11 <jki> #topic Kernel release status
13:07:39 <jki> 6.1-rt late, was already discussed on the list
13:07:56 <jki> any -rt-rc in flight?
13:08:24 <pave1> Not that I'm aware of. I may need to poke rt people.
13:08:44 <jki> yeah, would be nice
13:09:03 <jki> ok, move on?
13:09:13 <jki> 5
13:09:15 <pave1> There's v6.1.146-rt53 available, but we are
13:09:15 <jki> 4
13:09:26 <pave1> already on v6.1.148-cip45
13:09:47 <pave1> so I don't believe that would be suitable thing to do.
13:09:51 <jki> so, when would their next be, roughly?
13:10:17 <pave1> 6.1-rt does not have predictable schedule.
13:11:07 <jki> hmm...
13:11:51 <jki> how old is their last release now?
13:12:22 <jki> End of July
13:12:33 <jki> fair to ask for an update, I would say
13:12:41 <pave1> (y).
13:13:06 <jki> at least for plans
13:13:08 <jki> ok
13:13:25 <jki> then let's move on
13:13:28 <jki> 5
13:13:30 <jki> 4
13:13:32 <jki> 3
13:13:33 <jki> 2
13:13:35 <jki> 1
13:13:36 <jki> #topic Kernel testing
13:14:03 <arisut> hardware testing are starting to get into KernelCI production https://dashboard.kernelci.org/tree/cip/linux-6.12.y-cip/7bbd509bd1edc32120cf3e551f887e4e6d75da72
13:14:45 <arisut> we added arm64 and arm
13:15:08 <jki> nice
13:15:10 <jki> pavel: can our offline boards be compensated via kernelci for your release?
13:15:19 <arisut> I currently made a PR for fixing some arm problems and x86 platforms
13:15:39 <arisut> and add x86 platforms
13:15:59 <pave1> Dunno. Failing tests are at https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2032660416 .
13:16:00 <arisut> r8a7743-iwg20d-q7 https://lava.ciplatform.org/scheduler/job/1307163 passed
13:16:25 <pave1> If someone tells me what do to test that with kernelci, I can try to do that.
13:16:31 <arisut> de0-nano-soc https://lava.ciplatform.org/scheduler/job/1307174 still failing
13:16:46 <arisut> r8a774a1-hihope-rzg2m-ex passed
13:16:59 <arisut> zynqmp-zcu102 passed
13:17:03 <iwamatsu__81> All vx2 board are offline.
13:17:15 <arisut> beaglebone-black passed
13:17:28 <arisut> x86-siemens-mcom  passed
13:17:44 <jki> arisut: could you on-board pavel?
13:18:06 <arisut> x86-siemens-mcom  actually need to be fixed
13:18:11 <jki> I thought our maintainers we using kernelci already
13:18:31 <arisut> what do you mean by on-board?
13:18:45 <jki> "If someone tells me what do to test that with kernelci, I can try to do that."
13:20:13 <arisut> I think pavel want to test the board failed with GitLab pipeline
13:21:00 <arisut> ?
13:21:11 <arisut> is that right ?
13:21:28 <pave1> Pavel has a kernel tree and wants to know if he should release it :-).
13:21:29 <jki> well, if the test broke not because of unavailability, then this is a different topic
13:21:45 <jki> we have several targets offline, and I thought that kernelci could help out for that
13:22:04 <pave1> Lets chat after the irc meeting?
13:22:08 <arisut> ok
13:22:15 <jki> perfect, thanks!
13:22:46 <jki> so, the boards in the denx lab will likely stay offline for several weeks, just to let you know
13:23:04 <pave1> Aha :-(.
13:23:19 <jki> we are organizing relocation
13:23:20 <arisut> yes some boards on cip lava are offline
13:23:29 <arisut> would be nice to have it working again
13:23:51 <jki> yes, but there are many steps until that state still :(
13:23:52 <iwamatsu__81> I can connect vx2 board to my LAB, is it helpful?
13:24:13 <jki> would be nice, yes
13:24:38 <arisut> also denx de0-nano-soc went offline
13:24:45 <jki> we in Munich may also re-connect few boards next week if all goes well
13:24:56 <jki> all denx boards are offline as the worker is offline
13:24:59 <iwamatsu__81> jan: OK, I will do it.
13:25:03 <arisut> I see
13:25:43 <jki> but while boards are being shipped, keeping them connected them will be hard :)
13:26:12 <jki> other testing topics?
13:26:14 <iwamatsu__81> NOTE; I'm talking with Yoshi about whether Toshiba can solve this too.
13:26:52 <jki> if you have boards locally already, that would help quicker, indeed
13:27:14 <jki> once shipping gets involved, it may take longer
13:27:20 <iwamatsu__81> I see.
13:27:37 <iwamatsu__81> I will do after this meeting.
13:27:51 <jki> great!
13:28:52 <jki> move on?
13:29:03 <arisut> pave1, by the way on gentoo-sources this are the patches that we added to that version of kernel https://gitweb.geodns.gentoo.org/proj/linux-patches.git/commit/?h=5.10&id=c87676c6285a4f1640115a672a068c5ba88d3b26
13:30:39 <jki> 5
13:30:41 <jki> 4
13:30:43 <jki> 3
13:30:45 <jki> 2
13:30:46 <jki> 1
13:30:48 <jki> #topic AOB
13:30:49 <pave1> arisut: DO you want them for -cip?
13:32:15 <jki> fixes or feature backport?
13:32:36 <arisut> depend if you are interested in picking them up, I don't know if we have platforms using asoc intel
13:32:53 <arisut> they are fixes initializing the sound card
13:33:11 <jki> fixes -> stable, backport -> cip
13:33:35 <pave1> I believe I seen them in -stable, already.
13:33:37 <arisut> such patch got added in the 5.10.242
13:33:56 <arisut> yes I was referring to the kernel you was testing
13:34:07 <arisut> 5.10.241-cip64
13:34:13 <pave1> So we can ignore them, right? They'll eventually get picked up.
13:34:18 <arisut> yes
13:34:20 <pave1> There's no need to rush these.
13:35:08 <arisut> ok
13:36:05 <jki> other topics for today?
13:37:26 <jki> 5
13:37:29 <jki> 4
13:37:31 <jki> 3
13:37:32 <jki> 2
13:37:35 <jki> 1
13:37:36 <jki> #endmeeting