| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 248 seconds) | 04:08 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.48> has joined #cip | 04:09 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.48> has quit IRC (Ping timeout: 255 seconds) | 04:14 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 04:15 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:48 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Quit: Konversation terminated!) | 10:50 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 10:50 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:300f:8f8b:8ab8:a377> has joined #cip | 12:54 | |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip | 12:58 | |
| *** jki <jki!~jki@62.156.206.37> has joined #cip | 13:02 | |
| jki | hi all | 13:02 |
|---|---|---|
| jki | sorry for the delay | 13:02 |
| uli_ | hello | 13:02 |
| patersonc | Afternoon | 13:02 |
| pave1 | Hi! | 13:03 |
| masami | hello | 13:03 |
| iwamatsu__ | hello | 13:03 |
| jki | then let's start | 13:03 |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot | Meeting started Thu Nov 21 13:03:33 2024 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:03 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:03 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:03 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | #topic AI review | 13:03 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:03 |
| jki | sorry, got distracted again | 13:03 |
| pave1 | I got a link on that one on google, but was not able to open it. | 13:04 |
| pave1 | At some point, mailing version out would make sense :-). | 13:04 |
| jki | ah, that was the announcement thing | 13:04 |
| jki | let me check if I can fix | 13:04 |
| jki | yes, I can also post that on that thread | 13:04 |
| pave1 | That would be easiest, thanks! | 13:04 |
| jki | ok - other AIs are not recorded | 13:05 |
| jki | 5 | 13:05 |
| jki | 4 | 13:05 |
| jki | 3 | 13:05 |
| jki | 2 | 13:05 |
| jki | 1 | 13:05 |
| jki | #topic Kernel maintenance updates | 13:05 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| pave1 | I'm doing reviews, 4.4-st58, 6.1.117,118,119. | 13:05 |
| masami | This week reported 93 new CVEs and 19 updated CVEs. | 13:05 |
| uli_ | i've been preparing 4.4 | 13:05 |
| iwamatsu__ | I reviewed 6.1.117 , and I am reviewing 4.4-st58 | 13:06 |
| pave1 | There's fun situation where -stable is reverting security fixes because they break functionality. | 13:06 |
| pave1 | I guess I'll need to investigate more and bring up popcorn :-). | 13:06 |
| pave1 | Example is 8456fd1db 811371 o: 6.1| Revert "Bluetooth: hci_core: Fix possible buffer overflow" . | 13:07 |
| jki | huh, will that revert CVE states as well? :) | 13:07 |
| jki | anything else? | 13:09 |
| jki | 5 | 13:10 |
| jki | 4 | 13:10 |
| jki | 3 | 13:10 |
| jki | 2 | 13:10 |
| jki | 1 | 13:10 |
| jki | #topic Kernel release status | 13:10 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| jki | we have three late markers | 13:11 |
| jki | 4.4 will come out soon? | 13:11 |
| uli_ | once the reviews are through | 13:11 |
| uli_ | it's a big release, lots of backports | 13:11 |
| pave1 | 5.10-rt: There's .226-rt out, but that's old one. .229-rt-rc1 is out there, so I suggest to wait till that's released. | 13:12 |
| iwamatsu__ | for 6.1.y-cip, I am preparing it. | 13:12 |
| jki | ok, then things look more green next week | 13:12 |
| jki | I still wonder, though, is stable rt should further fall behind if it is our best option to wait that often | 13:14 |
| jki | anything else? | 13:15 |
| pave1 | I can do .226-rt based release, but that would be releasing old code. | 13:15 |
| pave1 | Maybe we should adjust our schedules for 4.19 / 5.10 rt to be less common. | 13:16 |
| jki | yes, that why I'm questioning to wait | 13:16 |
| jki | better become active and port forward | 13:16 |
| pave1 | ...or maybe admit that our releases are controlled by upstream ;-). | 13:16 |
| jki | at least when it is as easy as Clark put it - in most cases | 13:16 |
| jki | pavel: that will change anyway | 13:17 |
| jki | for 4.19 soon | 13:17 |
| jki | and then 5.10 and 6.1 as well | 13:17 |
| pave1 | Technially, forward porting rt changes to next stable is likely easy... | 13:17 |
| jki | exactly | 13:17 |
| pave1 | Hmm, true, self-maintenance. | 13:18 |
| jki | if the load explodes, we can still take measures | 13:18 |
| pave1 | But it would not get benefit of testing, and there could be fun if they decide to do something different. | 13:18 |
| patersonc | Do we know how long the RT project plan to maintain the older kernels? For the whole LTS cycle? | 13:18 |
| pave1 | Anyway, in this case, I wait for .229-rt? | 13:19 |
| pave1 | patersonc: Yes, that's what happened in the past. | 13:19 |
| jki | the RT project is not maintaining LTS, it's individual contributors | 13:19 |
| jki | (backed by companies, though, in many cases) | 13:19 |
| jki | the RT project supports LTS maintainer, and we could make use of that - specifically as member | 13:20 |
| patersonc | Okay. I wondered if most of the upstreaming effort was done we could ask them to redirect membership money for the maintenance work? | 13:21 |
| jki | we started to discusse this in the project, but there is no clear plan yet | 13:21 |
| pave1 | That's the discussion currently happening; there is an email asking members how to prioritize the work. | 13:21 |
| jki | yep | 13:21 |
| patersonc | Okay :) | 13:23 |
| jki | anyhing else on this topic? | 13:24 |
| jki | 5 | 13:24 |
| jki | 4 | 13:24 |
| jki | 3 | 13:24 |
| jki | 2 | 13:24 |
| jki | 1 | 13:24 |
| jki | #topic Kernel testing | 13:24 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:24 | |
| patersonc | I need to look into a couple of emails/requests sent this week - hopefully I'll get time later or tomorrow. | 13:25 |
| patersonc | I've no exciting updates to share though - sorry | 13:25 |
| pave1 | bbb is acting up. | 13:25 |
| pave1 | Could someone take a look? | 13:25 |
| jki | all bbb's or just in a specific lab? | 13:26 |
| pave1 | Plus it would be good to start testing 6.12.x. (Or probably we are already testing it and I just need a link). | 13:26 |
| patersonc | Good point - I forgot about that. Thanks pave1 | 13:26 |
| iwamatsu__ | one bbb on lab-cip-denx is not working now. | 13:27 |
| pave1 | iwamatsu: Is that why I need to hit 'retry' few times? | 13:28 |
| jki | if it is only one bbb instance, poke the lab owner | 13:30 |
| iwamatsu__ | pave1: It seems that one BBB is offline. It seems that tests often fail in BBB. | 13:31 |
| patersonc | The failures seem spread between multiple devices | 13:31 |
| patersonc | Scroll down on https://lava.ciplatform.org/scheduler/device_type/beaglebone-black?dt_search=&dt_length=100#dt_ and look for incomplete | 13:31 |
| patersonc | Failures seem to be for cip configs and for defconfig | 13:32 |
| iwamatsu__ | https://lava.ciplatform.org/scheduler/job/1224761#L546 | 13:32 |
| patersonc | But there are also passes for the same | 13:32 |
| pave1 | It fails on -stable-rc too, I just hit retry till I get a success... | 13:32 |
| iwamatsu__ | In most cases, the NFS mount has failed and has become a timeout.. | 13:33 |
| iwamatsu__ | OK ,I will check it. | 13:34 |
| jki | but if that happens in multiple labs and didn't happen (that often) in the past, it speaks more for a kernel regression | 13:34 |
| patersonc | And if it was an NFS server issue we'd expect to see similar issues for other devices | 13:35 |
| pave1 | At least https://lava.ciplatform.org/scheduler/job/1224454 is zimage: bad magic, bootloader-commands timing out. | 13:35 |
| pave1 | Hard to blame kernel for that. | 13:35 |
| patersonc | Indeed. And that's a healthcheck job | 13:37 |
| jki | simple to test: run older kernels multiple time in the same lab and see if they fail as well now | 13:37 |
| jki | if that healthcheck job is with an older kernel: done | 13:37 |
| patersonc | iwamatsu__: Let's chat via IRC/email about this when you have time? | 13:37 |
| iwamatsu__ | Sure | 13:38 |
| jki | good - thanks in advance to anyone doing the hard debugging :) | 13:38 |
| pave1 | jki: Bootloader claims zimage magic is wrong. It succeeds when repeated. That's before kernel was loaded. I believe kernel is not responsible. | 13:38 |
| jki | pavel: ack | 13:38 |
| jki | other testing topics? | 13:39 |
| jki | 5 | 13:40 |
| jki | 4 | 13:40 |
| jki | 3 | 13:40 |
| jki | 2 | 13:40 |
| jki | 1 | 13:40 |
| jki | #topic AOB | 13:40 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:40 | |
| jki | already wrote: I will likely not be available next week | 13:41 |
| jki | anyone able to pick up? | 13:41 |
| iwamatsu__ | I can takeover | 13:41 |
| jki | thanks! | 13:41 |
| iwamatsu__ | :-) | 13:41 |
| jki | other topics for today? | 13:41 |
| jki | 5 | 13:42 |
| jki | 4 | 13:42 |
| jki | 3 | 13:42 |
| jki | 2 | 13:42 |
| jki | 1 | 13:42 |
| jki | #endmeeting | 13:42 |
| collab-meetbot | Meeting ended Thu Nov 21 13:42:42 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:42 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-21-13.03.html | 13:42 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-21-13.03.txt | 13:42 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-21-13.03.log.html | 13:42 |
| *** 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:42 | |
| jki | thanks all! | 13:42 |
| uli_ | thanks | 13:42 |
| pave1 | Thank you! | 13:42 |
| iwamatsu__ | thank you | 13:42 |
| masami | thank you. | 13:42 |
| *** jki <jki!~jki@62.156.206.37> has quit IRC (Quit: Leaving) | 13:56 | |
| *** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 14:27 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 15:27 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:300f:8f8b:8ab8:a377> has quit IRC (Ping timeout: 256 seconds) | 18:55 | |
| *** rajm <rajm!~robert@host-81-178-148-108.as13285.net> has quit IRC (Remote host closed the connection) | 19:53 | |
| *** rajm <rajm!~robert@host-81-178-148-108.as13285.net> has joined #cip | 19:58 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Quit: Konversation terminated!) | 21:13 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip | 22:21 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!