| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 06:46 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Ping timeout: 246 seconds) | 06:57 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 07:00 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 08:02 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 08:06 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Ping timeout: 246 seconds) | 08:13 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 08:13 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 09:10 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 09:55 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Ping timeout: 256 seconds) | 10:16 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 10:16 | |
| *** jki <jki!~jki@195.145.170.202> has joined #cip | 12:57 | |
| *** TalkingBot <TalkingBot!~talking@109-81-171-96.rct.o2.cz> has joined #cip | 12:57 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:58 | |
| jki | hi all | 13:00 |
|---|---|---|
| pave1 | Hi! | 13:00 |
| iwamatsu__ | Hi | 13:00 |
| arisut | hi | 13:00 |
| patersonc | Hello | 13:00 |
| jki | ok, let's go | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
| collab-meetbot | Meeting started Thu Oct 16 13:01:46 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | #topic AI review | 13:01 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | no old ones, and I've seen no new ones either | 13:02 |
| jki | 5 | 13:02 |
| jki | 4 | 13:02 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #topic Kernel maintenance updates | 13:02 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| pave1 | I am reviewing 6.12.52 and .53 | 13:02 |
| iwamatsu__ | I reviewed 6.12.49 and.50 | 13:03 |
| jki | anything to add? | 13:04 |
| jki | 5 | 13:04 |
| jki | 4 | 13:04 |
| jki | 3 | 13:04 |
| jki | 2 | 13:04 |
| jki | 1 | 13:04 |
| jki | #topic Kernel release status | 13:04 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| jki | all green | 13:05 |
| pave1 | 6.1-rt is near, but I don't think we have suitable 6.1-rt at the moment. | 13:05 |
| jki | when was the last stable one released? | 13:06 |
| jki | 6.1.155-rt55 - this week | 13:07 |
| jki | last week | 13:07 |
| jki | is that not suitable? | 13:07 |
| pave1 | Aha, ok, so I missed the announcement. That should make things easier. | 13:07 |
| jki | yeah, maybe ask Clark to announce on stable-rt as well ;) | 13:07 |
| jki | he only did on rt-users | 13:08 |
| pave1 | In that case I'll do 6.1.155-cip release and then 6.1.155-cip-rt release, ok? | 13:08 |
| jki | sounds good to me | 13:08 |
| 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 testing | 13:10 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| patersonc | Howdy | 13:10 |
| patersonc | Not much news from me | 13:10 |
| arisut | we have more than 100+ jobs scheduled on cip labs | 13:10 |
| patersonc | Yes they are going a bit slowly as we only have 1 board online | 13:11 |
| arisut | kernelci say is not a problem and we should have set a limit | 13:11 |
| jki | which board is the bottleneck? | 13:11 |
| jki | the mcom again? | 13:12 |
| patersonc | mcom and ipc227e | 13:12 |
| arisut | I asked also about the possibility to have priority for cip jobs on cip labs | 13:12 |
| patersonc | One issue is because the boots are failing, jobs only fail after 15 or 30 minutes when the timeout is hit | 13:12 |
| patersonc | arisut: Interesting idea. Does KernelCI submit any non-CIP jobs to lab-cip at the moment? | 13:13 |
| pave1 | Should we have shorter timeouts? If kernel does not boot within 5 minutes, it is unlikely to boot at all. | 13:13 |
| jki | sounds reasonable | 13:13 |
| arisut | looking from 100+ scheduled jobs looks like yes is sending also basename jobs | 13:13 |
| pave1 | (Even shorter timeouts would be possible; if there's no output on serial for 1 minute, ...) | 13:14 |
| arisut | and other not cip jobs | 13:15 |
| jki | we used to have more ipc227e... need to check with my colleagues again what happened to them | 13:16 |
| patersonc | Does anyone have time to look into the kernel config to see why the root isn't mounting for ipc227e? https://lava.ciplatform.org/scheduler/job/1316478#L884 | 13:16 |
| arisut | patersonc, I have also updated your list https://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=0 | 13:17 |
| patersonc | Thanks! I forgot to finish it :( | 13:18 |
| TalkingBot | ommand line: bzImage rootwait vga=792 ip=dhcp console=ttyS0,115200n8 lava_mac=00:90:05:af:00:7d | 13:18 |
| pave1 | ..should it have root=nfs or something? | 13:18 |
| arisut | what is TalkingBot ? | 13:18 |
| pave1 | Sorry. My pet. He is friendly :-). | 13:18 |
| arisut | what are you using it for? | 13:19 |
| pave1 | Notifications when I switch consoles. | 13:19 |
| iwamatsu__ | It looks like ramfs is not mounting. https://lava.ciplatform.org/scheduler/job/1316221#L1780 | 13:19 |
| patersonc | Let's talk about this after the meeting? | 13:20 |
| jki | ok | 13:21 |
| arisut | I agree | 13:21 |
| jki | other testing topics? | 13:21 |
| jki | 5 | 13:22 |
| jki | 4 | 13:22 |
| jki | 3 | 13:22 |
| jki | 2 | 13:22 |
| jki | 1 | 13:22 |
| jki | #topic AOB | 13:22 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:22 | |
| jki | patersonc: you had one... | 13:23 |
| patersonc | I did | 13:23 |
| patersonc | Are we currently supporting/testing RT with 6.12-cip? | 13:23 |
| jki | supporting: yes | 13:23 |
| jki | testing: I hope so :) | 13:23 |
| pave1 | +1 :-) | 13:23 |
| patersonc | CI isn't doing anything RT related yet because no one came up with any "RT" configs | 13:24 |
| jki | we don't do separate configs anymore, I hope | 13:24 |
| pave1 | So I guess what should happen: | 13:24 |
| pave1 | enable config_preempt_rt | 13:24 |
| pave1 | use same source tree. | 13:24 |
| pave1 | jki: I believe the default option is to have separate realtime configs. | 13:25 |
| pave1 | jki: Not all features work with preempt_rt. | 13:25 |
| pave1 | jki: (But it is possible that all features that we care about do). | 13:25 |
| jki | pavel: we have too many already, and that only creates more rotting | 13:25 |
| jki | preempt-rt.cfg snippet, please | 13:25 |
| jki | like we do in isar-cip-core | 13:26 |
| pave1 | Ok, that should do the trick. | 13:26 |
| jki | so, there is no rt-enabled job running for 6.12-cip right now? | 13:26 |
| patersonc | KernelCI works with snippets. Maybe we should start there | 13:26 |
| patersonc | jki: nope | 13:26 |
| jki | that would be very bad | 13:26 |
| arisut | w.r | 13:26 |
| arisut | works with fragment | 13:26 |
| uli | sorry for being late. working on 4.19, request for reviews will go out later today. | 13:27 |
| pave1 | What I was trying to say: | 13:27 |
| arisut | we could add a preempt-rt fragment | 13:27 |
| pave1 | 1) We might be able to get away with testing _just_ config_preempt_rt enabled | 13:27 |
| pave1 | 2) I'd not recommend it. | 13:27 |
| jki | ack | 13:27 |
| jki | we need both | 13:27 |
| jki | we don't have rt on arm-32 e.g. | 13:28 |
| jki | not even in upstream, I just had a discussion about that again | 13:28 |
| jki | so, what is needed to close the testing gap? who could do that? | 13:29 |
| patersonc | We'll add some jobs to the kernelci configuration | 13:29 |
| arisut | I'm working on that but we need also to fix de0 at the moment | 13:30 |
| patersonc | Indeed. We wanted to get all boards working with the current configs before expanding | 13:30 |
| arisut | we still have problems on booting some boards | 13:30 |
| arisut | yes | 13:30 |
| jki | is there an overview of open issues? | 13:31 |
| iwamatsu__ | I am working it, but I've been busy this week and haven't had time to it. | 13:31 |
| jki | not everything needs to be done by folks in this meeting, but others need to be aware of open topics | 13:31 |
| arisut | we have a mail and me and patersonc are talking by dm or issues | 13:31 |
| jki | ok | 13:31 |
| arisut | https://github.com/kernelci/kernelci-pipeline/pull/1325 | 13:32 |
| arisut | this is the de0 nano soc PR | 13:32 |
| arisut | that I'm working on | 13:32 |
| arisut | and of which I made the configuration diff but no one double checked it | 13:32 |
| arisut | yet | 13:32 |
| jki | so, the state is still "does not boot", right? | 13:34 |
| arisut | yes, patersonc spreadsheet that I updated today is correct | 13:35 |
| arisut | thanks for making the spreadsheet patersonc | 13:36 |
| arisut | that spreadsheet is the current situation updated as today | 13:37 |
| jki | hmm, that ci job linked in the PR is not for the nanosoc, is it? | 13:37 |
| arisut | mmm I messed up the link ? | 13:37 |
| arisut | is opening de0-nano-soc for me | 13:38 |
| patersonc | This doc: https://docs.google.com/spreadsheets/d/1UH9oi8ETJ6ndtd2tmFGEcc12L3JCPbtUbRgnWBYdshw/edit?gid=0#gid=0 | 13:38 |
| jki | https://lava.ciplatform.org/scheduler/job/1314804 -> ipc227e | 13:38 |
| jki | that's the one from https://github.com/kernelci/kernelci-pipeline/pull/1325 | 13:39 |
| arisut | jki, -> patersonc, docs | 13:39 |
| jki | ok, but you may have confused the PR readers ;) | 13:39 |
| arisut | i see, thanks | 13:39 |
| jki | well, maybe we can help with the RT 6.12 topic, but only next week | 13:41 |
| arisut | updated | 13:41 |
| jki | patersonc: is your original question answered? | 13:44 |
| patersonc | jki: Yep | 13:44 |
| jki | good :) | 13:45 |
| jki | other topics for today? | 13:45 |
| jki | 5 | 13:46 |
| jki | 4 | 13:46 |
| jki | 3 | 13:46 |
| jki | 2 | 13:46 |
| jki | 1 | 13:46 |
| jki | #endmeeting | 13:46 |
| collab-meetbot | Meeting ended Thu Oct 16 13:46:36 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:46 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/10/cip.2025-10-16-13.01.html | 13:46 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/10/cip.2025-10-16-13.01.txt | 13:46 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/10/cip.2025-10-16-13.01.log.html | 13: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/" | 13:46 | |
| jki | thanks! | 13:46 |
| pave1 | Thank you! | 13:46 |
| uli | thanks | 13:46 |
| pave1 | arisut: | 13:46 |
| patersonc | Thanks all | 13:46 |
| iwamatsu__ | Thank you | 13:46 |
| pave1 | bot is here: https://gitlab.com/tui/tui/-/blob/master/zpells/talking_irc.py?ref_type=heads | 13:47 |
| patersonc | If anyone has time to help look through our boot issues it would be very welcome :) | 13:47 |
| pave1 | arisut: It is useful because it makes noise when there's an activity on the channel. | 13:47 |
| pave1 | Fill in channel before hiting connect. | 13:47 |
| arisut | is practically reading messages ? | 13:49 |
| arisut | with tls | 13:50 |
| arisut | but why also writing messages ? like this <TalkingBot> ommand line: bzImage rootwait vga=792 ip=dhcp console=ttyS0,115200n8 lava_mac=00:90:05:af:00:7d | 13:51 |
| arisut | some kind of irc client with voice | 13:52 |
| pave1 | Yes, irc client with voice. | 13:53 |
| pave1 | And yes, I pasted text to wrong window, that's why it spoke. | 13:54 |
| pave1 | It will not speak on its own :). | 13:54 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 14:06 | |
| *** TalkingBot <TalkingBot!~talking@109-81-171-96.rct.o2.cz> has quit IRC (Remote host closed the connection) | 14:07 | |
| *** jki <jki!~jki@195.145.170.202> has quit IRC (Ping timeout: 256 seconds) | 15:02 | |
| *** jki <jki!~jki@62.156.206.48> has joined #cip | 15:25 | |
| *** jki <jki!~jki@62.156.206.48> has quit IRC (Remote host closed the connection) | 15:29 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Ping timeout: 244 seconds) | 17:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 17:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Remote host closed the connection) | 18:29 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 18:31 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Read error: Connection reset by peer) | 18:33 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 18:35 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Remote host closed the connection) | 18:39 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 18:40 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Remote host closed the connection) | 18:53 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 18:54 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Read error: Connection reset by peer) | 19:13 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 19:16 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Remote host closed the connection) | 19:28 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 19:30 | |
| *** uli_ <uli_!~quassel@static.153.40.69.159.clients.your-server.de> has joined #cip | 19:33 | |
| *** rajm-and <rajm-and!~robert@host-78-151-157-55.as13285.net> has joined #cip | 19:33 | |
| *** uli <uli!~quassel@static.153.40.69.159.clients.your-server.de> has quit IRC (Ping timeout: 248 seconds) | 19:37 | |
| *** rajm <rajm!~robert@host-78-151-157-55.as13285.net> has quit IRC (Ping timeout: 248 seconds) | 19:37 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Ping timeout: 256 seconds) | 19:51 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has joined #cip | 19:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@223.190.197.124> has quit IRC (Quit: Konversation terminated!) | 20:25 | |
| *** dl9pf <dl9pf!sid395223@user/dl9pf> has quit IRC (Quit: Connection closed for inactivity) | 20:43 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!