| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 06:56 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 07:00 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 08:41 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 08:45 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 08:46 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 09:03 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:04 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 09:09 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 09:09 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 10:22 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 10:22 | |
| *** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip | 10:35 | |
| *** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip | 11:44 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 264 seconds) | 11:58 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 11:59 | |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip | 11:59 | |
| *** jki <jki!~jki@95.157.49.24> has joined #cip | 11:59 | |
| jki | hi all | 11:59 |
|---|---|---|
| uli | hello | 12:00 |
| pave1 | Hi! | 12:00 |
| masami | hello | 12:00 |
| patersonc | Hey | 12:00 |
| iwamatsu | hello | 12:00 |
| jki | let's go | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
| collab-meetbot | Meeting started Thu Jan 29 12:01:08 2026 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:01 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | #topic AI review | 12:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | none on the list | 12:01 |
| jki | 5 | 12:01 |
| jki | 4 | 12:01 |
| jki | 3 | 12:01 |
| jki | 2 | 12:01 |
| jki | 1 | 12:01 |
| jki | #topic Kernel maintenance updates | 12:01 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| uli | i pushed 4.19 today, 4.4 is next | 12:01 |
| masami | This week reported 56 new CVEs and 2 updated CVEs. | 12:01 |
| pave1 | I'm doing reviews, 6.12.64, .67, .68. | 12:02 |
| iwamatsu | I reviewed 6.12.66 | 12:02 |
| jki | anything to add? | 12:04 |
| jki | 5 | 12:04 |
| jki | 4 | 12:04 |
| jki | 3 | 12:04 |
| jki | 2 | 12:04 |
| jki | 1 | 12:04 |
| jki | #topic Kernel release status | 12:04 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:04 | |
| pave1 | 6.1-rt is still a problem. | 12:05 |
| pave1 | I sent email at | 12:05 |
| jki | any feedback on any channel? | 12:05 |
| pave1 | Date: Thu, 22 Jan 2026 12:19:17 +0100 | 12:05 |
| pave1 | Subject: Re: [ANNOUNCE] 6.1.157-rt57 | 12:05 |
| jki | not via the list, I saw this | 12:05 |
| pave1 | cc-ed to lists. | 12:05 |
| jki | should we offer help to refresh the queue? | 12:06 |
| jki | maybe you could try offline first to assess the complexity | 12:06 |
| pave1 | I'm scared :-). We don't really have good way to test realtime. | 12:06 |
| jki | this is no reason to not update | 12:07 |
| jki | we have kernelci tests, and we have some downstream users | 12:07 |
| pave1 | Okay, I can try; with some luck it will just be no conflict. | 12:07 |
| jki | in the end, you already do that for 4.19 and 4.4 | 12:07 |
| jki | exactly | 12:07 |
| pave1 | Could we get CIP project to talk to Realtime project about expectations etc? | 12:07 |
| jki | Clark's maintenance is not paid by the RT project | 12:08 |
| jki | it's a RH contribution | 12:08 |
| pave1 | Maybe we should do 6.1 less often, or maybe we could talk realtime project to release more often or something. | 12:08 |
| pave1 | Aha. | 12:08 |
| jki | but, as I sugested long ago, you could join their calls to sync | 12:08 |
| jki | then you know more than what's on the list | 12:09 |
| pave1 | So I was there few times. It is wrong time at friday afternoon. | 12:09 |
| jki | too late? | 12:09 |
| jki | ok, that's unfortunate | 12:09 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:09 | |
| pave1 | Could we get help from linuxfoundations realtime project here? | 12:10 |
| jki | stable is not a direct work so far, only consulting to stable maintainers | 12:10 |
| pave1 | Ok, unfortunate. | 12:11 |
| pave1 | Let me take a look at the patches. | 12:11 |
| jki | yeah, I may bring that up again on the next regular project meeting, but that is March or April | 12:11 |
| jki | another topic - 4.19: regular and -rt releases are a bit out of sync | 12:12 |
| pave1 | Yes please. Likely update will be easy this iteration, but as likely we'll hit real problem one day. | 12:12 |
| jki | can we align the 4.19 release again? | 12:13 |
| pave1 | jki: Yes. I guess we should eventually do 4.19-rt (and 4.4-rt) not on time-based schedule but simply every second 4.19-cip release. | 12:13 |
| jki | e.g. | 12:13 |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 12:13 | |
| pave1 | 4.19-cip is out. Ok, I can make -rt release on top of that. | 12:14 |
| jki | that would be great | 12:15 |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 12:15 | |
| pave1 | Ok, added to the todo list :-). | 12:15 |
| jki | thanks! | 12:15 |
| jki | anything else on releases? | 12:16 |
| jki | 5 | 12:16 |
| jki | 4 | 12:16 |
| jki | 3 | 12:16 |
| jki | 2 | 12:16 |
| jki | 1 | 12:16 |
| jki | #topic Kernel testing | 12:16 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:16 | |
| patersonc | Hey | 12:18 |
| patersonc | I've been adding beaglev-fire support to kernelci. It's working, just need to check another thing then get the MR merged | 12:18 |
| patersonc | I also tried to add qemu-riscv64, but this hit some issues I still need to fix | 12:19 |
| patersonc | I guess that's it from me | 12:19 |
| pave1 | 6.18-stable testing points qemu failures: | 12:20 |
| pave1 | https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2291978755 | 12:20 |
| pave1 | Is that likely to be real failure or some testing problem? | 12:20 |
| jki | iwamatsu: there are some open MRs on cip-kernel-config, please check, one affects the bv-fire | 12:21 |
| patersonc | Seems to be unable to mount the file system. | 12:21 |
| iwamatsu | jki: Yes I know. I will check these. | 12:21 |
| pave1 | Thank you. | 12:22 |
| patersonc | qemu issue happened on two different labs, and two different qemu types, so maybe it's not an infrastructure issue? | 12:22 |
| jki | "EXT2-fs (vda): error: couldn't mount because of unsupported optional features (2c0)" | 12:22 |
| jki | rootfs does not fit to kernel config? | 12:23 |
| jki | https://lava.ciplatform.org/scheduler/job/1387035 | 12:23 |
| jki | maybe we lost a config option in the forward porting to 6.18 | 12:24 |
| patersonc | It looks like this has been failing on 6.18 stable for a while: https://lava.ciplatform.org/scheduler/alljobs?length=25&search=qemu_arm_defconfig_6.18&search=qemu_arm_defconfig_6.18&length=100#table | 12:24 |
| jki | same issue for qemu-arm64 | 12:25 |
| jki | is that the merged-defconfig or something special? | 12:25 |
| patersonc | It's qemu_arm_defconfig | 12:26 |
| jki | then there is something missing that | 12:26 |
| jki | check the effective ext4 options | 12:27 |
| jki | anything else on testing? | 12:30 |
| jki | 5 | 12:30 |
| jki | 4 | 12:30 |
| jki | 3 | 12:30 |
| jki | 2 | 12:30 |
| jki | 1 | 12:30 |
| jki | #topic AOB | 12:30 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:30 | |
| pave1 | Renesas defconfig: | 12:30 |
| pave1 | https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/merge_requests/157 | 12:31 |
| pave1 | Looks okay to me, but I guess that iwamatsu normally handles configs? | 12:31 |
| jki | right | 12:31 |
| iwamatsu | I will check it after this meeting. | 12:32 |
| pave1 | Thank you! | 12:32 |
| arisut_ | No updates from me | 12:33 |
| jki | good - anything else? | 12:34 |
| arisut_ | Actually one, there is interest on having kci-dev sending results directly to KCIDB | 12:34 |
| arisut_ | By that kci-dev could be used on kernel maintainer building scripts | 12:35 |
| arisut_ | so that it can add results direct to kcidb and should solve issues related to kernelci overload | 12:36 |
| arisut_ | Some kernel maintainer are already interested | 12:36 |
| arisut_ | Maybe could be used also in the cip kernel maintenance work flow | 12:37 |
| jki | is it used by cip maintainers now? | 12:37 |
| iwamatsu__ | not yet | 12:38 |
| arisut_ | Is not developed yet, we are working on it. Currently we got feedback from upstream kernel maintainer that could be useful | 12:38 |
| arisut_ | I actually just got such feedback few minutes ago directly | 12:39 |
| jki | ok, great - and even better if cip could benefit from it as well | 12:40 |
| arisut_ | Yes, that would be nice to integrate on cip gitlab pipeline | 12:41 |
| arisut_ | Or any other cip building environment | 12:41 |
| arisut_ | Also we discussed me and Patersonc on what we are Missing on kernelci | 12:43 |
| arisut_ | About kernelci configuration, but other than some rt problems looks like we are good | 12:43 |
| arisut_ | That’s all from me | 12:44 |
| jki | great, thanks! | 12:45 |
| jki | so, done for today? | 12:45 |
| arisut_ | Yes | 12:45 |
| jki | 5 | 12:45 |
| jki | 4 | 12:46 |
| jki | 3 | 12:46 |
| jki | 2 | 12:46 |
| jki | 1 | 12:46 |
| jki | #endmeeting | 12:46 |
| collab-meetbot | Meeting ended Thu Jan 29 12:46:06 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:46 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-29-12.01.html | 12:46 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-29-12.01.txt | 12:46 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/01/cip.2026-01-29-12.01.log.html | 12:46 |
| *** 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/" | 12:46 | |
| jki | thank you! | 12:46 |
| arisut_ | Thx everyone | 12:46 |
| iwamatsu | thank you | 12:46 |
| uli | thanks | 12:46 |
| pave1 | Thank you! | 12:46 |
| masami | thank you | 12:46 |
| *** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:46 | |
| *** jki <jki!~jki@95.157.49.24> has quit IRC (Quit: Leaving) | 12:48 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 12:54 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 14:15 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 14:15 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds) | 14:25 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 14:26 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds) | 14:55 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 14:56 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds) | 15:31 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 15:32 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 15:35 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 15:42 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 16:39 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 16:39 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Ping timeout: 255 seconds) | 16:46 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 16:46 | |
| *** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 16:51 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has joined #cip | 16:52 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer) | 16:54 | |
| *** tmerciai0 <tmerciai0!~tmerciai3@net-188-217-34-12.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 16:56 | |
| *** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip | 19:36 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!