13:01:36 <jki> #startmeeting CIP IRC weekly meeting
13:01:36 <collab-meetbot> Meeting started Thu Nov  7 13:01:36 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:36 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:36 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:51 <jki> #topic AI review
13:01:57 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:02:37 <jki> the announcement email draft feels ready, will share later, still polishing on the blog post
13:02:59 <jki> no other AIs recorded
13:03:10 <jki> 5
13:03:11 <jki> 4
13:03:13 <jki> 3
13:03:15 <jki> 2
13:03:16 <jki> 1
13:03:17 <jki> #topic Kernel maintenance updates
13:03:35 <pave1> I'm doing reviews, 6.1.114, 115, 116.
13:03:45 <masami> This week reported 51 new CVEs and 0 updated CVEs.
13:04:13 <iwamatsu__> I reviewed 6.1.116-rc
13:06:06 <jki> are we generating filtering reports for the new CVEs already now?
13:06:36 <csteiger> I tried my hand on it today for the first time
13:06:59 <masami> this one. https://lists.cip-project.org/g/cip-dev/message/17215
13:07:28 <jki> ah, missed that - nice!
13:07:46 <iwamatsu__> csteiger: thanks for your work!
13:08:24 <csteiger> I hope it is useful for you guys :)
13:08:59 <jki> what would be a next useful step for that?
13:11:02 <jki> more architectures? :)
13:11:45 <csteiger> If you have wishes let me know, it is very easy to add more stuff
13:11:57 <csteiger> More configs, archs etc
13:12:55 <jki> opinions? suggestions?
13:14:32 <jki> well, we can also continue this on the list later on
13:14:47 <jki> anything else on this topic block?
13:15:15 <jki> 5
13:15:16 <jki> 4
13:15:18 <jki> 3
13:15:20 <jki> 2
13:15:21 <jki> 1
13:15:23 <jki> #topic Kernel release status
13:15:35 <jki> there are two releases late
13:15:46 <jki> any news on 4.19-upstream?
13:16:16 <iwamatsu__> No update, but rc version has been reeleased
13:16:25 <jki> ok, that is good
13:16:44 <iwamatsu__> It may be released in a few days.
13:16:51 <jki> formally late is also 5.10-rt, but I suppose that is also waiting for the next 5.10 which is due tomorrow
13:17:25 <pave1> I'll need to investigate, but release is easy once upstream does it.
13:18:02 <jki> anything else regarding releases?
13:18:34 <jki> 5
13:18:36 <jki> 4
13:18:37 <jki> 3
13:18:38 <jki> 2
13:18:40 <jki> 1
13:18:42 <jki> #topic Kernel testing
13:18:54 <patersonc> Hello
13:18:57 <patersonc> There's an MR open adding LAVA support for the new MCOM platform. I'll get the configs added to the server today for testing, then we can get it merged.
13:19:20 <jki> that's great to hear!
13:19:29 <arisut> kci-dev as been released to pypi, now can be installed by pip install kci-dev
13:20:17 <pave1> arisut: Wow, nice :-).
13:20:18 <arisut> we are planning to add new feature like bisection and artifact download
13:20:48 <arisut> documentation is here https://kernelci.github.io/kci-dev/
13:20:54 <jki> looks like this is looking for cip-users now :) - great!
13:21:26 <patersonc> :)
13:21:42 <pave1> patersonc: We have failure on 6.11-rc, and it won't go away with retries.
13:21:44 <pave1> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1531015121
13:21:53 <pave1> I did not investigate much more.
13:21:56 <patersonc> Thanks pave1 - I'll take a look
13:21:57 <arisut> and you can see my talk at OSSJ where I'm talking about kci-dev a bit. Talk @OSSJ: https://www.youtube.com/watch?v=vNMNJAdm-fo
13:22:01 <pave1> (You have copy in the email).
13:22:17 <pave1> Thank you!
13:22:20 <arisut> https://pypi.org/project/kci-dev/
13:23:18 <arisut> is still in beta but feel free to try it and give feedback
13:23:35 <patersonc> Thanks arisut
13:24:03 <arisut> thanks you
13:25:37 <jki> anything else on testing?
13:25:44 <patersonc> Not from me
13:26:06 <jki> 5
13:26:07 <jki> 4
13:26:09 <jki> 3
13:26:10 <jki> 2
13:26:12 <jki> 1
13:26:14 <jki> #topic AOB
13:27:20 <patersonc> pave1: It looks like there has been a successful boot on BBB for that kernel - just never both in the same GitLab job. Slightly worrying. I'll try and dig further. Maybe iwamatsu__ has some suggestions
13:28:11 <pave1> Yeah, so for the record, bbb was flakey before. I did run more than few retries in recent history.
13:28:47 <iwamatsu__> I dont have information about it now, so I also check it.
13:28:56 <patersonc> pave1: Have you seen a pattern with particular boards failing/not failing?
13:29:32 <pave1> Not really. It was "bbb failed again, just hit retry, it will work".
13:30:50 <jki> where does it fail, boot-up? or already in u-boot while loading the kernel?
13:32:11 <patersonc> I've seen both
13:32:34 <pave1> One example is:
13:32:35 <pave1> bootz 0x82000000 - 0x88000000
13:32:35 <pave1> zimage: Bad magic!
13:32:36 <pave1> bootloader-commands timed out after 282 seconds
13:33:37 <jki> that download issues by u-boot are familiar to us in the xenomai lab
13:34:03 <jki> we plan (for too long) to add some retries there as well
13:34:57 <jki> still wondering why LAVA has nothing like that by default...
13:35:40 <jki> even worse: this sometimes hits our heathcheck jobs, and then the board is first of all "offline"
13:37:31 <jki> anyway - will let you know if we happen to find some workarounds for that first
13:37:32 <patersonc> Yea...
13:37:59 <jki> other topics for today?
13:38:49 <jki> 5
13:38:50 <jki> 4
13:38:52 <jki> 3
13:38:54 <jki> 2
13:38:55 <jki> 1
13:38:57 <jki> #endmeeting