| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 01:51 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 06:53 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 07:04 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has joined #cip | 10:00 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has quit IRC (Ping timeout: 250 seconds) | 10:07 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has joined #cip | 10:08 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 10:13 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 11:28 | |
| *** masami <masami!~masami@FL1-125-197-94-238.tky.mesh.ad.jp> has joined #cip | 11:49 | |
| *** jki <jki!~jki@62.156.206.39> has joined #cip | 11:57 | |
| *** TalkingBot <TalkingBot!~talking@109-81-171-31.rct.o2.cz> has joined #cip | 11:58 | |
| jki | hi all | 11:59 |
|---|---|---|
| pave1 | Hi! | 12:00 |
| uli_ | hello | 12:00 |
| masami | hi | 12:00 |
| *** TalkingBot <TalkingBot!~talking@109-81-171-31.rct.o2.cz> has quit IRC (Remote host closed the connection) | 12:01 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:01 | |
| jki | so, let's go | 12:01 |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
| collab-meetbot | Meeting started Thu Nov 20 12:01:19 2025 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 | |
| iwamatsu__ | hello | 12:01 |
| jki | #topic AI review | 12:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| jki | i don't have any | 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 | |
| masami | This week reported 31 new CVEs and 0 updated CVEs. | 12:02 |
| uli_ | i'm working on 4.19 and 4.4 | 12:02 |
| masami | While triaging CVEs, I found a bug in the fix patch for CVE-2025-39808 and sent a patch. | 12:02 |
| pave1 | I am reviewing 6.12.58. | 12:02 |
| iwamatsu__ | I reviewed 6.12.57 | 12:02 |
| masami | it was merged into the mainline. https://github.com/torvalds/linux/commit/53f731f5bba0cf03b751ccceb98b82fadc9ccd1e | 12:02 |
| jki | very good! | 12:03 |
| *** pav31 <pav31!~talking@109-81-171-31.rct.o2.cz> has joined #cip | 12:04 | |
| jki | more topics? | 12:05 |
| jki | 5 | 12:05 |
| jki | 4 | 12:05 |
| jki | 3 | 12:05 |
| jki | 2 | 12:05 |
| jki | 1 | 12:05 |
| jki | #topic Kernel release status | 12:05 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:05 | |
| jki | 4.19 is late but in the making | 12:05 |
| jki | anything in addition? | 12:05 |
| jki | 5 | 12:06 |
| jki | 4 | 12:06 |
| jki | 3 | 12:06 |
| jki | 2 | 12:06 |
| jki | 1 | 12:06 |
| jki | #topic Kernel testing | 12:06 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:06 | |
| patersonc | Hello all | 12:06 |
| patersonc | I've been looking into the kernelCI pipelines in more detail and been adding some more support. Goal is to add some RT tests | 12:07 |
| patersonc | Pavel, are there any specific tests you'd like? | 12:07 |
| jki | doesn't kernelCI have tests already? | 12:07 |
| arisut | patersonc, please rebase the PR | 12:08 |
| patersonc | arisut: Yes I'll do that after this meeting | 12:08 |
| pave1 | There's cyclictest, but I've not really looked into other test. | 12:08 |
| patersonc | jki: Yes. We just need to enable them for CIP | 12:08 |
| pave1 | Testing realtime is not easy. | 12:08 |
| patersonc | RT tests already supported by KernelCI can be seen here: https://github.com/kernelci/kernelci-pipeline/blob/main/config/jobs.yaml#L2190 | 12:08 |
| patersonc | Look for the rt-tests-* | 12:09 |
| jki | yes, KernelCI lacks I/O testing, but there should be cyclictest + functional rt-tests | 12:09 |
| jki | all that under stress-ng, most likely | 12:09 |
| pav31 | Lets do that :-). | 12:09 |
| pave1 | It would be interesting to know how members use/test realtime. | 12:10 |
| pave1 | Hopefully people having real use for realtime also have some real tests ;-). | 12:10 |
| jki | yes, we have, but those are system tests with concrete products and often infrastructure around | 12:10 |
| jki | I'm remininding folks all the time that some tests also need to be externalized | 12:11 |
| pave1 | jki: I know, we had tests that involved oscilloscopes and hardware event sources. | 12:11 |
| jki | pavel: it's different today, more RT Ethernets with complex container stacks | 12:12 |
| jki | but also some tests that involve other I/O | 12:12 |
| pave1 | jki: Would it be possible to send a report 'we are testing these and these kernels with these results' maybe once in a year? | 12:12 |
| pave1 | jki: I assume it differs by industry, really. That elevator company is going to be interested in "are we toggling gpios when we should". | 12:13 |
| pave1 | jki: I assume some train control is on different level, perhaps doing gpio toggling by non-linux systems connected over ethernet. | 12:13 |
| jki | we are working to towards that, just reminded everyone at my event today of sharing kernel configs... | 12:13 |
| pave1 | Thank yuo! | 12:14 |
| pave1 | Thank you! | 12:14 |
| jki | so, what about the state of kernelci testing with de0-nano-soc? | 12:15 |
| jki | https://lore.kernel.org/cip-dev/f2c73b72-cbb3-49c1-8555-9341b3cd3535@siemens.com/T/#u | 12:15 |
| jki | also the Renesas board setups looked improveable to me, firmware-wise | 12:16 |
| jki | just like we standardized the worker images, we should likely standardized the firmware versions | 12:16 |
| patersonc | Did you manage to update the bootloaders in the end on your Renesas boards? | 12:16 |
| jki | yes, but that update was from 2013.01 to 2013.01 U-Boot | 12:17 |
| jki | that's... not helpful | 12:17 |
| patersonc | ha | 12:17 |
| iwamatsu__ | about de0-nano-soc: I apologize for the delay in reporting this.I am continuing investigation, but I still do not know the cause. | 12:17 |
| jki | iwamatsu__: thanks - you can cross-check with the isar-cip-core integration I shared, that worked for me | 12:18 |
| iwamatsu__ | jki: ok | 12:18 |
| jki | we can also update what we have in our lab on the de0 in Munich, unifying things ideally | 12:18 |
| jki | I just gave one nano-soc to pasquale for deployment at Siemens Prague lab | 12:19 |
| jki | will take some time, though | 12:19 |
| jki | regarding other board shippments: I'm awaiting for support from our export control folks, they are very busy unfortunately | 12:20 |
| patersonc | I'm assuming that not all devices have upstream bootloader support. Maybe it would be a good side-project for CIP to get this sorted for their reference platforms? | 12:21 |
| patersonc | Thank you jki | 12:21 |
| jki | while kernelci may be happy with tftp booting, full cip images need recent upstream U-Boot with EFI support | 12:22 |
| jki | so we may need to be more picky regarding firmware in the future | 12:22 |
| jki | the TI AM62px looks good so far, and the upcoming BeagleV Fire will likely do so as well | 12:23 |
| arisut | my de0-nano-soc patch got merged today | 12:23 |
| jki | the Nano SoC was... left behind by the SoC vendor in upstream | 12:24 |
| jki | oh! didn't get a notice yet | 12:24 |
| arisut | is adding the de0-nano-soc context on boot | 12:24 |
| jki | arisut: which patch(es) are you exactly referring to? | 12:25 |
| arisut | and add nfs | 12:25 |
| arisut | https://github.com/kernelci/kernelci-pipeline/pull/1325 | 12:25 |
| jki | ah, kernelci - didn't track that | 12:25 |
| jki | interesting - do they help us already? | 12:26 |
| arisut | what do you mean by help us? | 12:26 |
| jki | help with making de0-nano-soc boot in kernelci | 12:27 |
| jki | maybe even without firmware updates? | 12:27 |
| arisut | it should boot with the correct context but is one month old pull request | 12:28 |
| arisut | and add nfs | 12:28 |
| arisut | so should help | 12:28 |
| jki | already ran pipelines with them that failed before? | 12:29 |
| jki | like with 6.12-cip? | 12:29 |
| arisut | I should check | 12:29 |
| arisut | is still a patch I sent one month ago | 12:30 |
| jki | I cannot track which of the pipelines you shared last times where run with our without those changes | 12:30 |
| arisut | for trying to workout de0 problems | 12:30 |
| arisut | without | 12:31 |
| jki | but even if those changes should resolve issues, we should still consolidate our firmware versions on our test devices | 12:31 |
| arisut | last time pipeline was on production | 12:31 |
| jki | ...then without those changes | 12:31 |
| arisut | there is no such patch on production yet | 12:31 |
| arisut | as is merged today | 12:31 |
| patersonc | I guess we'll come back to it next week after the next production roll-out and subsequent CIP push | 12:32 |
| arisut | yes | 12:32 |
| jki | further testing topics? | 12:33 |
| jki | 5 | 12:34 |
| jki | 4 | 12:34 |
| jki | 3 | 12:34 |
| jki | 2 | 12:34 |
| jki | 1 | 12:34 |
| jki | #topic AOB | 12:34 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:34 | |
| jki | BeagleV Fire - TSC confirmed our proposal | 12:35 |
| jki | how many to request now, how to distribute them? | 12:35 |
| pave1 | I would not mind having a toy to play with, but I'm probably fine with doing testing remotely. | 12:36 |
| patersonc | If TSC approves, I'd like 4 for the LAVA labs. 2 for lab-cip-iwamatsu and 2 for lab-cip-cariad | 12:36 |
| jki | uli_: will you need one as well? | 12:37 |
| uli_ | i would not mind to have one | 12:37 |
| jki | for isar-cip-core enabling, I'd like to have one at least initially | 12:37 |
| iwamatsu__ | Contribution to isar-cip-core, Toshiba can do it. | 12:38 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 12:38 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:38 | |
| jki | iwamatsu__: thanks in advance! | 12:38 |
| jki | then we should be fine with 6 | 12:39 |
| jki | maybe we at Siemens will get some independently, we are also enabling Xenomai on RISC-V right now | 12:39 |
| jki | and my colleague doing that expressed interest to follow the CIP board selection :) | 12:39 |
| patersonc | \o/ | 12:40 |
| jki | patersonc: then you have all data to request the boards, likely one-by-one, right? | 12:40 |
| jki | direct shippings recommended ;) | 12:40 |
| jki | other topics for today? | 12:41 |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection) | 12:41 | |
| patersonc | jki: Do you want me to order all of them? | 12:42 |
| jki | I would try to make the requests on one bunch, linking them | 12:42 |
| patersonc | sure | 12:42 |
| jki | but not one request for all boards, because then you would end up having to redistribute them | 12:42 |
| jki | if you can handle that, would be great, yes | 12:43 |
| patersonc | I'll figure it out :) | 12:43 |
| jki | otherwise raise your hand if I can help | 12:43 |
| jki | okay... | 12:43 |
| jki | closing remarks, topics? | 12:43 |
| jki | 5 | 12:44 |
| jki | 4 | 12:44 |
| jki | 3 | 12:44 |
| jki | 2 | 12:44 |
| jki | 1 | 12:44 |
| jki | #endmeeting | 12:44 |
| collab-meetbot | Meeting ended Thu Nov 20 12:44:30 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:44 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-20-12.01.html | 12:44 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-20-12.01.txt | 12:44 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/11/cip.2025-11-20-12.01.log.html | 12:44 |
| *** 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:44 | |
| jki | thanks! | 12:44 |
| iwamatsu__ | Thank you | 12:44 |
| uli_ | thanks | 12:44 |
| pave1 | Thank you! | 12:44 |
| masami | thank you | 12:44 |
| arisut | thx | 12:44 |
| *** masami <masami!~masami@FL1-125-197-94-238.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:44 | |
| *** jki <jki!~jki@62.156.206.39> has quit IRC (Quit: Leaving) | 12:44 | |
| patersonc | Thanks | 12:45 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae043235.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 12:45 | |
| *** pav31 <pav31!~talking@109-81-171-31.rct.o2.cz> has quit IRC (Remote host closed the connection) | 12:46 | |
| patersonc | arisut: Can you remember why we have "normal" baseline-jobs for arm64, but baseline-nfs-jobs for arm and x86 in jobs-cip,yaml? | 12:46 |
| arisut | because they currently work | 12:47 |
| patersonc | Okay :) | 12:48 |
| *** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Quit: So long and thanks for all the bits.) | 13:52 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has joined #cip | 22:26 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds) | 22:40 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-52-5.cust.vodafonedsl.it> has joined #cip | 22:41 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!