13:02:58 <jki> #startmeeting CIP IRC weekly meeting
13:02:59 <collab-meetbot> Meeting started Thu Feb  6 13:02:58 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:07 <jki> #topic AI review
13:03:17 <jki> none in my list
13:03:28 <jki> anything missed?
13:03:55 <jki> 5
13:03:57 <jki> 4
13:03:58 <jki> 3
13:04:00 <jki> 2
13:04:01 <jki> 1
13:04:03 <jki> #topic Kernel maintenance updates
13:04:08 <uli_> i'm preparing 4.19
13:04:22 <masami> This week reported 22 new CVEs and 45 updated CVEs.
13:04:36 <iwamatsu__> hi all,
13:04:43 <iwamatsu__> I reviewed 6.1.128.
13:05:43 <jki> anything else?
13:06:17 <jki> 5
13:06:19 <jki> 4
13:06:21 <jki> 3
13:06:22 <jki> 2
13:06:24 <jki> 1
13:06:26 <jki> #topic Kernel release status
13:06:48 <jki> 4.4 is still late, waiting for 4.19 IIRC
13:06:52 <uli_> 4.19 is mostly done, i'll push an rc and request for reviews tomorrow
13:06:56 <uli_> 4.4 will follow.
13:07:33 <jki> just work, or any unforeseen complications / efforts?
13:07:41 <pave1> (Sorry, I was on wrong channel).
13:07:52 <uli_> no, it's just a larger amount of patches than it was for 4.4
13:08:04 <uli_> but the number of backports has not really increased
13:08:14 <uli_> at least for now
13:08:22 <jki> ok - please raise your hand if you need support
13:08:27 <uli_> will do
13:08:43 <jki> anything else of release status?
13:08:50 <pave1> I guess load test will come in two weeks with the -rc1 hitting stable...
13:10:40 <jki> I saw some announcement of Pavel on 6.12 backporting need
13:11:07 <pave1> Yeah, I need to run the scripts to collect the data.
13:11:14 <jki> what is the next step there?
13:11:33 <pave1> Next steps would be collect supported kernel configs, get TSC agreement on supported board.
13:11:43 <pave1> And then decide when to fork.
13:12:21 <jki> ok, great
13:12:39 <jki> next TSC call is skipped, so we have a bit more time for collecting things
13:13:11 <jki> still, the call for them should be sent - or was that included in your email?
13:13:28 <pave1> No, it was not. Normally Iwamatsu-san handles kernel config.
13:15:27 <jki> iwamatsu__: would you like to trigger this already?
13:17:02 <iwamatsu__> I think we need to decide on support boards first.
13:17:15 <iwamatsu__> kernel config will come after that.
13:17:44 <jki> I think we could already collect member suggestions this way
13:18:06 <jki> official decisions are with the TSC, but it might be easier if we have input already
13:18:35 <pave1> I guess we can ask for supported boards and configs on the list, then just ask TSC for approval.
13:19:13 <jki> yes
13:19:54 <iwamatsu__> I see, I will mail about kernel config for asking TSC for approval.
13:20:25 <jki> good, thanks in advance!
13:20:39 <jki> then let's move on...
13:20:43 <jki> 5
13:20:44 <jki> 4
13:20:46 <jki> 3
13:20:48 <jki> 2
13:20:49 <jki> 1
13:20:51 <jki> #topic Kernel testing
13:21:12 <patersonc> Hello. No exciting updates from me this week.
13:21:44 <arisut> same from me
13:22:09 <pave1> Could I get someone to take a look at 6.6 testing?
13:22:35 <jki> 6.6?
13:22:37 <pave1> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1657192619
13:23:06 <pave1> There's zynqmp failure. If it is real, we should report it to Greg.
13:23:20 <uli_> i have the same with 4.19
13:23:55 <patersonc> Interesting
13:24:47 <patersonc> 6.13 is booting
13:24:51 <patersonc> As is 6.12
13:25:01 <pave1> Yep. It does not go away with retries.
13:25:20 <pave1> If you believe it is real, I can try to report/debug it.
13:25:29 <patersonc> I'll take a look and try and work it out
13:25:39 <pave1> Thanks a lot!
13:25:45 <patersonc> Other LTS releases are okay by the looks of it, just not 6.6 or 4.19
13:26:08 <patersonc> https://lava.ciplatform.org/scheduler/device_type/zynqmp-zcu102?dt_dt_page=1&dt_search=&dt_length=1000#dt_
13:26:35 <iwamatsu__> 4.19 does not see to be a kernel issue.
13:27:33 <iwamatsu__> LAVA's file image download is failing. https://lava.ciplatform.org/scheduler/job/1244274#L23
13:28:11 <patersonc> You're right
13:28:15 <jki> all the time? no retries here?
13:28:23 <pave1> IIRC there was different failure on 6.6
13:28:34 <jki> such issues normally "go away" on retries
13:29:10 <patersonc> 4.19 issues have only been this morning
13:29:24 <pave1> 6.6: https://lava.ciplatform.org/scheduler/job/1244145 fails at "starting kernel".
13:29:25 <patersonc> Maybe the cybertrust lab has some internet issues today
13:30:41 <patersonc> Sadly that's the only lab with those boards
13:31:04 <pave1> The 6.6 thing does not seem to be connectivity issue.
13:31:09 <masami> I'll ask cybertrus lab's status
13:31:09 <patersonc> nope
13:31:32 <iwamatsu__> Chris and me retriy tests for 4.19 and 6.6 now ;-)
13:31:35 <patersonc> 6.6 issues were all yesterday
13:31:40 <pave1> +1, thanks!
13:32:12 <jki> perfect
13:32:20 <jki> anything else on testing?
13:32:46 <arisut> masami, I already did
13:32:59 <masami> arist: thanks.
13:33:37 <jki> 5
13:33:39 <jki> 4
13:33:41 <jki> 3
13:33:43 <jki> 2
13:33:45 <jki> 1
13:33:47 <jki> #topic AOB
13:33:58 <pave1> Last week, I was reviewing 6.1.128/129.
13:34:35 <pave1> I'll be travelling next week, this time with a bit better internet access.
13:35:03 <pave1> uli: There are 4.4 patches on the list: "Fix repeated WARNING in unpin_current_cpu()". Could we take them to 4.4?
13:35:24 <uli_> yes, i will pick them up
13:35:43 <pave1> Feel free to review them / speak up if they are not okay.
13:35:52 <uli_> sure
13:35:58 <pave1> Thanks!
13:36:34 <jki> anything else for today?
13:37:01 <jki> 5
13:37:03 <jki> 4
13:37:05 <jki> 3
13:37:07 <jki> 2
13:37:09 <jki> 1
13:37:11 <jki> #endmeeting