Thursday, 2025-02-06

*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:40
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Quit: Konversation terminated!)07:36
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip07:36
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Ping timeout: 244 seconds)12:05
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:51
*** jki <jki!~jki@p4fdbca61.dip0.t-ipconnect.de> has joined #cip12:57
jkihi all13:01
uli_hello13:01
masamihi13:01
arisuthi13:02
jkiseems we are a smaller round today - ok, let's go13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbotThe 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
jkinone in my list13:03
jkianything missed?13:03
jki513:03
jki413:03
jki313:03
jki213:04
jki113:04
jki#topic Kernel maintenance updates13:04
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:04
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:8391:bee4:a8cf:cdba> has joined #cip13:04
uli_i'm preparing 4.1913:04
masamiThis week reported 22 new CVEs and 45 updated CVEs.13:04
iwamatsu__hi all,13:04
iwamatsu__I reviewed 6.1.128.13:04
jkianything else?13:05
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
jki4.4 is still late, waiting for 4.19 IIRC13:06
uli_4.19 is mostly done, i'll push an rc and request for reviews tomorrow13:06
uli_4.4 will follow.13:06
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip13:07
jkijust work, or any unforeseen complications / efforts?13:07
pave1(Sorry, I was on wrong channel).13:07
uli_no, it's just a larger amount of patches than it was for 4.413:07
uli_but the number of backports has not really increased13:08
uli_at least for now13:08
jkiok - please raise your hand if you need support13:08
uli_will do13:08
jkianything else of release status?13:08
pave1I guess load test will come in two weeks with the -rc1 hitting stable...13:08
jkiI saw some announcement of Pavel on 6.12 backporting need13:10
pave1Yeah, I need to run the scripts to collect the data.13:11
jkiwhat is the next step there?13:11
pave1Next steps would be collect supported kernel configs, get TSC agreement on supported board.13:11
pave1And then decide when to fork.13:11
jkiok, great13:12
jkinext TSC call is skipped, so we have a bit more time for collecting things13:12
jkistill, the call for them should be sent - or was that included in your email?13:13
pave1No, it was not. Normally Iwamatsu-san handles kernel config.13:13
jkiiwamatsu__: would you like to trigger this already?13:15
iwamatsu__I think we need to decide on support boards first.13:17
iwamatsu__kernel config will come after that.13:17
jkiI think we could already collect member suggestions this way13:17
jkiofficial decisions are with the TSC, but it might be easier if we have input already13:18
pave1I guess we can ask for supported boards and configs on the list, then just ask TSC for approval.13:18
jkiyes13:19
iwamatsu__I see, I will mail about kernel config for asking TSC for approval.13:19
jkigood, thanks in advance!13:20
jkithen let's move on...13:20
jki513:20
jki413:20
jki313:20
jki213:20
jki113:20
jki#topic Kernel testing13:20
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:20
patersoncHello. No exciting updates from me this week.13:21
arisutsame from me13:21
pave1Could I get someone to take a look at 6.6 testing?13:22
jki6.6?13:22
pave1https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/165719261913:22
pave1There's zynqmp failure. If it is real, we should report it to Greg.13:23
uli_i have the same with 4.1913:23
patersoncInteresting13:23
patersonc6.13 is booting13:24
patersoncAs is 6.1213:24
pave1Yep. It does not go away with retries.13:25
pave1If you believe it is real, I can try to report/debug it.13:25
patersoncI'll take a look and try and work it out13:25
pave1Thanks a lot!13:25
patersoncOther LTS releases are okay by the looks of it, just not 6.6 or 4.1913:25
patersonchttps://lava.ciplatform.org/scheduler/device_type/zynqmp-zcu102?dt_dt_page=1&dt_search=&dt_length=1000#dt_13:26
iwamatsu__4.19 does not see to be a kernel issue.13:26
iwamatsu__LAVA's file image download is failing. https://lava.ciplatform.org/scheduler/job/1244274#L2313:27
patersoncYou're right13:28
jkiall the time? no retries here?13:28
pave1IIRC there was different failure on 6.613:28
jkisuch issues normally "go away" on retries13:28
patersonc4.19 issues have only been this morning13:29
pave16.6: https://lava.ciplatform.org/scheduler/job/1244145 fails at "starting kernel".13:29
patersoncMaybe the cybertrust lab has some internet issues today13:29
patersoncSadly that's the only lab with those boards13:30
pave1The 6.6 thing does not seem to be connectivity issue.13:31
masamiI'll ask cybertrus lab's status13:31
patersoncnope13:31
iwamatsu__Chris and me retriy tests for 4.19 and 6.6 now ;-)13:31
patersonc6.6 issues were all yesterday13:31
pave1+1, thanks!13:31
jkiperfect13:32
jkianything else on testing?13:32
arisutmasami, I already did13:32
masamiarist: thanks.13:32
jki513:33
jki413:33
jki313:33
jki213:33
jki113:33
jki#topic AOB13:33
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:33
pave1Last week, I was reviewing 6.1.128/129.13:33
pave1I'll be travelling next week, this time with a bit better internet access.13:34
pave1uli: There are 4.4 patches on the list: "Fix repeated WARNING in unpin_current_cpu()". Could we take them to 4.4?13:35
uli_yes, i will pick them up13:35
pave1Feel free to review them / speak up if they are not okay.13:35
uli_sure13:35
pave1Thanks!13:35
jkianything else for today?13:36
jki513:37
jki413:37
jki313:37
jki213:37
jki113:37
jki#endmeeting13:37
collab-meetbotMeeting ended Thu Feb  6 13:37:11 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:37
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-06-13.02.html13:37
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-06-13.02.txt13:37
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/02/cip.2025-02-06-13.02.log.html13:37
*** 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:37
jkithank you!13:37
pave1Thank you!13:37
uli_thanks13:37
masamithank you13:37
iwamatsu__Thank you13:37
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:37
*** jki <jki!~jki@p4fdbca61.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)13:37
arisutthanks13:37
patersonc4.19 job has passed now on that board13:38
uli_nice13:38
patersoncI'll investigate the 6.6 issue more13:38
pave1I was about to hit the retry button, but I'll leave that to you :-).13:38
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Ping timeout: 265 seconds)14:09
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip16:17
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)18:05
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:8391:bee4:a8cf:cdba> has quit IRC (Quit: Client closed)21:47

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