13:01:46 <jki> #startmeeting CIP IRC weekly meeting
13:01:46 <collab-meetbot> Meeting started Thu Oct 16 13:01:46 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:46 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:46 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:53 <jki> #topic AI review
13:02:09 <jki> no old ones, and I've seen no new ones either
13:02:17 <jki> 5
13:02:19 <jki> 4
13:02:21 <jki> 3
13:02:22 <jki> 2
13:02:24 <jki> 1
13:02:26 <jki> #topic Kernel maintenance updates
13:02:58 <pave1> I am reviewing 6.12.52 and .53
13:03:19 <iwamatsu__> I reviewed 6.12.49 and.50
13:04:24 <jki> anything to add?
13:04:41 <jki> 5
13:04:43 <jki> 4
13:04:44 <jki> 3
13:04:46 <jki> 2
13:04:48 <jki> 1
13:04:49 <jki> #topic Kernel release status
13:05:00 <jki> all green
13:05:16 <pave1> 6.1-rt is near, but I don't think we have suitable 6.1-rt at the moment.
13:06:37 <jki> when was the last stable one released?
13:07:21 <jki> 6.1.155-rt55 - this week
13:07:33 <jki> last week
13:07:42 <jki> is that not suitable?
13:07:42 <pave1> Aha, ok, so I missed the announcement. That should make things easier.
13:07:59 <jki> yeah, maybe ask Clark to announce on stable-rt as well ;)
13:08:06 <jki> he only did on rt-users
13:08:26 <pave1> In that case I'll do 6.1.155-cip release and then 6.1.155-cip-rt release, ok?
13:08:55 <jki> sounds good to me
13:09:32 <jki> anything else?
13:10:01 <jki> 5
13:10:02 <jki> 4
13:10:03 <jki> 3
13:10:05 <jki> 2
13:10:06 <jki> 1
13:10:08 <jki> #topic Kernel testing
13:10:20 <patersonc> Howdy
13:10:24 <patersonc> Not much news from me
13:10:44 <arisut> we have more than 100+ jobs scheduled on cip labs
13:11:27 <patersonc> Yes they are going a bit slowly as we only have 1 board online
13:11:28 <arisut> kernelci say is not a problem and we should have set a limit
13:11:53 <jki> which board is the bottleneck?
13:12:04 <jki> the mcom again?
13:12:17 <patersonc> mcom and ipc227e
13:12:40 <arisut> I asked also about the possibility to have priority for cip jobs on cip labs
13:12:46 <patersonc> One issue is because the boots are failing, jobs only fail after 15 or 30 minutes when the timeout is hit
13:13:09 <patersonc> arisut: Interesting idea. Does KernelCI submit any non-CIP jobs to lab-cip at the moment?
13:13:32 <pave1> Should we have shorter timeouts? If kernel does not boot within 5 minutes, it is unlikely to boot at all.
13:13:48 <jki> sounds reasonable
13:13:52 <arisut> looking from 100+ scheduled jobs looks like yes is sending also basename jobs
13:14:13 <pave1> (Even shorter timeouts would be possible; if there's no output on serial for 1 minute, ...)
13:15:28 <arisut> and other not cip jobs
13:16:12 <jki> we used to have more ipc227e... need to check with my colleagues again what happened to them
13:16:40 <patersonc> Does anyone have time to look into the kernel config to see why the root isn't mounting for ipc227e?  https://lava.ciplatform.org/scheduler/job/1316478#L884
13:17:37 <arisut> patersonc, I have also updated your list https://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=0
13:18:07 <patersonc> Thanks! I forgot to finish it :(
13:18:11 <TalkingBot> ommand line: bzImage rootwait vga=792 ip=dhcp console=ttyS0,115200n8 lava_mac=00:90:05:af:00:7d
13:18:26 <pave1> ..should it have root=nfs or something?
13:18:41 <arisut> what is TalkingBot ?
13:18:51 <pave1> Sorry. My pet. He is friendly :-).
13:19:02 <arisut> what are you using it for?
13:19:18 <pave1> Notifications when I switch consoles.
13:19:59 <iwamatsu__> It looks like ramfs is not mounting. https://lava.ciplatform.org/scheduler/job/1316221#L1780
13:20:53 <patersonc> Let's talk about this after the meeting?
13:21:09 <jki> ok
13:21:42 <arisut> I agree
13:21:46 <jki> other testing topics?
13:22:48 <jki> 5
13:22:50 <jki> 4
13:22:51 <jki> 3
13:22:53 <jki> 2
13:22:54 <jki> 1
13:22:56 <jki> #topic AOB
13:23:07 <jki> patersonc: you had one...
13:23:11 <patersonc> I did
13:23:25 <patersonc> Are we currently supporting/testing RT with 6.12-cip?
13:23:36 <jki> supporting: yes
13:23:42 <jki> testing: I hope so :)
13:23:52 <pave1> +1 :-)
13:24:13 <patersonc> CI isn't doing anything RT related yet because no one came up with any "RT" configs
13:24:30 <jki> we don't do separate configs anymore, I hope
13:24:30 <pave1> So I guess what should happen:
13:24:40 <pave1> enable config_preempt_rt
13:24:47 <pave1> use same source tree.
13:25:15 <pave1> jki: I believe the default option is to have separate realtime configs.
13:25:24 <pave1> jki: Not all features work with preempt_rt.
13:25:35 <pave1> jki: (But it is possible that all features that we care about do).
13:25:42 <jki> pavel: we have too many already, and that only creates more rotting
13:25:58 <jki> preempt-rt.cfg snippet, please
13:26:04 <jki> like we do in isar-cip-core
13:26:21 <pave1> Ok, that should do the trick.
13:26:21 <jki> so, there is no rt-enabled job running for 6.12-cip right now?
13:26:23 <patersonc> KernelCI works with snippets. Maybe we should start there
13:26:32 <patersonc> jki: nope
13:26:33 <jki> that would be very bad
13:26:46 <arisut> w.r
13:26:53 <arisut> works with fragment
13:27:01 <uli> sorry for being late. working on 4.19, request for reviews will go out later today.
13:27:13 <pave1> What I was trying to say:
13:27:26 <arisut> we could add a preempt-rt fragment
13:27:30 <pave1> 1) We might be able to get away with testing _just_ config_preempt_rt enabled
13:27:35 <pave1> 2) I'd not recommend it.
13:27:41 <jki> ack
13:27:47 <jki> we need both
13:28:00 <jki> we don't have rt on arm-32 e.g.
13:28:26 <jki> not even in upstream, I just had a discussion about that again
13:29:09 <jki> so, what is needed to close the testing gap? who could do that?
13:29:46 <patersonc> We'll add some jobs to the kernelci configuration
13:30:04 <arisut> I'm working on that but we need also to fix de0 at the moment
13:30:34 <patersonc> Indeed. We  wanted to get all boards working with the current configs before expanding
13:30:49 <arisut> we still have problems on booting some boards
13:30:57 <arisut> yes
13:31:18 <jki> is there an overview of open issues?
13:31:34 <iwamatsu__> I am working it, but I've been busy this week and haven't had time to it.
13:31:43 <jki> not everything needs to be done by folks in this meeting, but others need to be aware of open topics
13:31:44 <arisut> we have a mail and me and patersonc are talking by dm or issues
13:31:54 <jki> ok
13:32:08 <arisut> https://github.com/kernelci/kernelci-pipeline/pull/1325
13:32:16 <arisut> this is the de0 nano soc PR
13:32:26 <arisut> that I'm working on
13:32:53 <arisut> and of which I made the configuration diff but no one double checked it
13:32:55 <arisut> yet
13:34:41 <jki> so, the state is still "does not boot", right?
13:35:04 <arisut> yes, patersonc spreadsheet that I updated today is correct
13:36:47 <arisut> thanks for making the spreadsheet patersonc
13:37:13 <arisut> that spreadsheet is the current situation updated as today
13:37:15 <jki> hmm, that ci job linked in the PR is not for the nanosoc, is it?
13:37:30 <arisut> mmm I messed up the link ?
13:38:09 <arisut> is opening de0-nano-soc for me
13:38:43 <patersonc> This doc: https://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=0
13:38:47 <jki> https://lava.ciplatform.org/scheduler/job/1314804 -> ipc227e
13:39:01 <jki> that's the one from https://github.com/kernelci/kernelci-pipeline/pull/1325
13:39:05 <arisut> jki, -> patersonc, docs
13:39:26 <jki> ok, but you may have confused the PR readers ;)
13:39:43 <arisut> i see, thanks
13:41:31 <jki> well, maybe we can help with the RT 6.12 topic, but only next week
13:41:42 <arisut> updated
13:44:31 <jki> patersonc: is your original question answered?
13:44:41 <patersonc> jki: Yep
13:45:10 <jki> good :)
13:45:16 <jki> other topics for today?
13:46:27 <jki> 5
13:46:29 <jki> 4
13:46:31 <jki> 3
13:46:33 <jki> 2
13:46:34 <jki> 1
13:46:36 <jki> #endmeeting