| *** tmerciai <tmerciai!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has quit IRC (Ping timeout: 258 seconds) | 00:05 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has quit IRC (Ping timeout: 258 seconds) | 04:07 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.174> has joined #cip | 04:09 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip | 05:27 | |
| *** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 256 seconds) | 05:31 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has joined #cip | 07:02 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has joined #cip | 12:55 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has quit IRC (Ping timeout: 250 seconds) | 12:58 | |
| *** jki <jki!~jki@62.156.206.40> has joined #cip | 13:00 | |
| jki | hi all | 13:00 |
|---|---|---|
| uli | hello | 13:00 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has joined #cip | 13:01 | |
| iwamatsu__ | hello | 13:01 |
| jki | seems we are few today | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot | Meeting started Thu Sep 11 13:02:10 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:02 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:02 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:02 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 13:02 | |
| jki | #topic AI review | 13:02 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | - start define a CIP kernel threat model [Pavel] | 13:02 |
| jki | pavel: just in time :) | 13:02 |
| pave1 | Yep, I've got something. I'll get robot to comment on it and then get list to comment on it. | 13:03 |
| *** iwamatsu__81 <iwamatsu__81!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has joined #cip | 13:03 | |
| jki | ok, we are looking forward | 13:03 |
| jki | no other AIs recorded | 13:03 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:03 |
| jki | 2 | 13:03 |
| jki | 1 | 13:03 |
| jki | #topic Kernel maintenance updates | 13:03 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| uli | i'm working on 4.19 | 13:04 |
| *** TalkingBot <TalkingBot!~talking@109-81-171-133.rct.o2.cz> has joined #cip | 13:04 | |
| iwamatsu__81 | I am reviewing 6.12.44 and released 6.12.y-cip/ | 13:04 |
| pave1 | Reviews, 6.12.45 and .46. | 13:04 |
| pave1 | I'm working on 5.10.241-cip64. 5 targets are down, but I guess I'll just release it, anyway. | 13:05 |
| jki | further topics? | 13:05 |
| jki | (regarding target, we can touch that under testing) | 13:06 |
| pave1 | Yep. | 13:06 |
| jki | 5 | 13:07 |
| jki | 4 | 13:07 |
| jki | 3 | 13:07 |
| jki | 2 | 13:07 |
| jki | 1 | 13:07 |
| jki | #topic Kernel release status | 13:07 |
| *** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:07 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has quit IRC (Ping timeout: 250 seconds) | 13:07 | |
| jki | 6.1-rt late, was already discussed on the list | 13:07 |
| jki | any -rt-rc in flight? | 13:07 |
| pave1 | Not that I'm aware of. I may need to poke rt people. | 13:08 |
| jki | yeah, would be nice | 13:08 |
| jki | ok, move on? | 13:09 |
| jki | 5 | 13:09 |
| pave1 | There's v6.1.146-rt53 available, but we are | 13:09 |
| jki | 4 | 13:09 |
| pave1 | already on v6.1.148-cip45 | 13:09 |
| pave1 | so I don't believe that would be suitable thing to do. | 13:09 |
| jki | so, when would their next be, roughly? | 13:09 |
| pave1 | 6.1-rt does not have predictable schedule. | 13:10 |
| jki | hmm... | 13:11 |
| jki | how old is their last release now? | 13:11 |
| jki | End of July | 13:12 |
| jki | fair to ask for an update, I would say | 13:12 |
| pave1 | (y). | 13:12 |
| jki | at least for plans | 13:13 |
| jki | ok | 13:13 |
| jki | then let's move on | 13:13 |
| jki | 5 | 13:13 |
| jki | 4 | 13:13 |
| jki | 3 | 13:13 |
| jki | 2 | 13:13 |
| jki | 1 | 13:13 |
| jki | #topic Kernel testing | 13:13 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:13 | |
| arisut | hardware testing are starting to get into KernelCI production https://dashboard.kernelci.org/tree/cip/linux-6.12.y-cip/7bbd509bd1edc32120cf3e551f887e4e6d75da72 | 13:14 |
| arisut | we added arm64 and arm | 13:14 |
| jki | nice | 13:15 |
| jki | pavel: can our offline boards be compensated via kernelci for your release? | 13:15 |
| arisut | I currently made a PR for fixing some arm problems and x86 platforms | 13:15 |
| arisut | and add x86 platforms | 13:15 |
| pave1 | Dunno. Failing tests are at https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2032660416 . | 13:15 |
| arisut | r8a7743-iwg20d-q7 https://lava.ciplatform.org/scheduler/job/1307163 passed | 13:16 |
| *** TalkingBot <TalkingBot!~talking@109-81-171-133.rct.o2.cz> has quit IRC (Remote host closed the connection) | 13:16 | |
| pave1 | If someone tells me what do to test that with kernelci, I can try to do that. | 13:16 |
| arisut | de0-nano-soc https://lava.ciplatform.org/scheduler/job/1307174 still failing | 13:16 |
| arisut | r8a774a1-hihope-rzg2m-ex passed | 13:16 |
| arisut | zynqmp-zcu102 passed | 13:16 |
| iwamatsu__81 | All vx2 board are offline. | 13:17 |
| arisut | beaglebone-black passed | 13:17 |
| arisut | x86-siemens-mcom passed | 13:17 |
| jki | arisut: could you on-board pavel? | 13:17 |
| arisut | x86-siemens-mcom actually need to be fixed | 13:18 |
| jki | I thought our maintainers we using kernelci already | 13:18 |
| arisut | what do you mean by on-board? | 13:18 |
| jki | "If someone tells me what do to test that with kernelci, I can try to do that." | 13:18 |
| arisut | I think pavel want to test the board failed with GitLab pipeline | 13:20 |
| arisut | ? | 13:21 |
| arisut | is that right ? | 13:21 |
| pave1 | Pavel has a kernel tree and wants to know if he should release it :-). | 13:21 |
| jki | well, if the test broke not because of unavailability, then this is a different topic | 13:21 |
| jki | we have several targets offline, and I thought that kernelci could help out for that | 13:21 |
| pave1 | Lets chat after the irc meeting? | 13:22 |
| arisut | ok | 13:22 |
| jki | perfect, thanks! | 13:22 |
| jki | so, the boards in the denx lab will likely stay offline for several weeks, just to let you know | 13:22 |
| pave1 | Aha :-(. | 13:23 |
| jki | we are organizing relocation | 13:23 |
| arisut | yes some boards on cip lava are offline | 13:23 |
| arisut | would be nice to have it working again | 13:23 |
| jki | yes, but there are many steps until that state still :( | 13:23 |
| iwamatsu__81 | I can connect vx2 board to my LAB, is it helpful? | 13:23 |
| jki | would be nice, yes | 13:24 |
| arisut | also denx de0-nano-soc went offline | 13:24 |
| jki | we in Munich may also re-connect few boards next week if all goes well | 13:24 |
| jki | all denx boards are offline as the worker is offline | 13:24 |
| iwamatsu__81 | jan: OK, I will do it. | 13:24 |
| arisut | I see | 13:25 |
| jki | but while boards are being shipped, keeping them connected them will be hard :) | 13:25 |
| jki | other testing topics? | 13:26 |
| iwamatsu__81 | NOTE; I'm talking with Yoshi about whether Toshiba can solve this too. | 13:26 |
| jki | if you have boards locally already, that would help quicker, indeed | 13:26 |
| jki | once shipping gets involved, it may take longer | 13:27 |
| iwamatsu__81 | I see. | 13:27 |
| iwamatsu__81 | I will do after this meeting. | 13:27 |
| jki | great! | 13:27 |
| jki | move on? | 13:28 |
| arisut | pave1, by the way on gentoo-sources this are the patches that we added to that version of kernel https://gitweb.geodns.gentoo.org/proj/linux-patches.git/commit/?h=5.10&id=c87676c6285a4f1640115a672a068c5ba88d3b26 | 13:29 |
| jki | 5 | 13:30 |
| jki | 4 | 13:30 |
| jki | 3 | 13:30 |
| jki | 2 | 13:30 |
| jki | 1 | 13:30 |
| jki | #topic AOB | 13:30 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:30 | |
| pave1 | arisut: DO you want them for -cip? | 13:30 |
| jki | fixes or feature backport? | 13:32 |
| arisut | depend if you are interested in picking them up, I don't know if we have platforms using asoc intel | 13:32 |
| arisut | they are fixes initializing the sound card | 13:32 |
| jki | fixes -> stable, backport -> cip | 13:33 |
| pave1 | I believe I seen them in -stable, already. | 13:33 |
| arisut | such patch got added in the 5.10.242 | 13:33 |
| arisut | yes I was referring to the kernel you was testing | 13:33 |
| arisut | 5.10.241-cip64 | 13:34 |
| pave1 | So we can ignore them, right? They'll eventually get picked up. | 13:34 |
| arisut | yes | 13:34 |
| pave1 | There's no need to rush these. | 13:34 |
| arisut | ok | 13:35 |
| jki | other topics for today? | 13:36 |
| jki | 5 | 13:37 |
| jki | 4 | 13:37 |
| jki | 3 | 13:37 |
| jki | 2 | 13:37 |
| jki | 1 | 13:37 |
| jki | #endmeeting | 13:37 |
| collab-meetbot | Meeting ended Thu Sep 11 13:37:36 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:37 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-11-13.02.html | 13:37 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-11-13.02.txt | 13:37 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/09/cip.2025-09-11-13.02.log.html | 13:37 |
| *** 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:37 | |
| jki | thanks! | 13:37 |
| uli | thanks | 13:37 |
| iwamatsu__81 | Thank you | 13:37 |
| pave1 | thank you! | 13:37 |
| arisut | thanks | 13:37 |
| arisut | pave1, I see from your link of Gitlab that one machine is riscv | 13:39 |
| arisut | we don't have enabled riscv in kernelci cip platforms because was not inside the cip platforms under testing | 13:40 |
| arisut | https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware | 13:41 |
| pave1 | Standby, I'll be back in 10 minutes. | 13:41 |
| arisut | vx2 are down on cip lab so they are down also for kernelci | 13:44 |
| arisut | would be nice to get also patersonc opinion on this | 13:47 |
| arisut | kernelci have no other vx2 platform, as other riscv platform we currently have few platforms other than the lava cip platforms but not sure about the status | 13:50 |
| pave1 | Sorry for the delay. | 13:53 |
| pave1 | Aha, so it looks like one machine is r-v and the other two are vx2 variants, so kernelci will not help me? | 13:54 |
| arisut | np | 13:54 |
| arisut | probably in this case no | 13:55 |
| arisut | as kernelci is using lava in the same way gitlab is doing it | 13:55 |
| pave1 | aha, ok. Let me push the kernels. | 13:56 |
| arisut | the problem here is that vx2 are down and kernelci have no other vx2 afaik | 13:56 |
| arisut | riscv afaik is not in the platform reference | 13:57 |
| arisut | only as candidate | 13:57 |
| arisut | are under consideration to be official but not official yet | 13:58 |
| pave1 | Yeah, risc-v seems to be "future" thing. Best be ready for that, but fortunately it is not widely used at the moment. | 14:00 |
| arisut | pave1, how do you keep track of patch you added over the stable linux ? | 14:03 |
| arisut | just as personal information | 14:03 |
| arisut | I'm trying to understand if we could exchange information on fixes bugs as gentoo-sources is doing a similar thing | 14:04 |
| pave1 | arisut: So this is mostly uli question :-). | 14:06 |
| pave1 | We keep additional patches (features) in a git tree. | 14:06 |
| arisut | in gentoo-sources we add patches here https://gitweb.geodns.gentoo.org/proj/linux-patches.git/ | 14:06 |
| arisut | feel free to check which patch are we adding | 14:06 |
| arisut | and use it on cip | 14:07 |
| pave1 | For 5.10 -- for example -- that would be in linux-5.10.y-cip-rebase. | 14:08 |
| pave1 | For older trees, where -stable is no longer maintained, we have v4.19.org in git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git repository. | 14:10 |
| arisut | I see | 14:10 |
| pave1 | Is gentoo interested in 4.19 and older? | 14:10 |
| pave1 | (And no, I don't think I'll go watch another repository as a patch source. -stable already supplies ... more than enough patches :-) ) | 14:10 |
| arisut | currently we stop at 5.10 | 14:10 |
| pave1 | Aha, good. So you don't need to deal with the lts-commit-list stuff. | 14:11 |
| pave1 | We normally should not have patches interesting to gentoo in our trees. | 14:11 |
| arisut | normally yes | 14:16 |
| pave1 | Here is example of patches we carry: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-5.10.y-cip-rebase . | 14:18 |
| pave1 | So now I've released 5.10.241-cip64. | 14:20 |
| arisut | but every now and then release have problems | 14:21 |
| arisut | upstream release not cip release and we usually patch it up | 14:22 |
| arisut | I see | 14:23 |
| pave1 | We are willing to skip stable release if it is known bad. Fortunately it is pretty seldom for our use. | 14:24 |
| pave1 | Could you take a look and show me how do I determine if 5.10.241-cip64 passes the testing? | 14:25 |
| arisut | oh I see | 14:25 |
| arisut | wait I will push a build with kci-dev | 14:27 |
| arisut | pave1, is currently running. you can see it here https://api.kernelci.org/viewer?search=kind%3Dcheckout&search=created%3E2025-09-10T14:28:52 | 14:29 |
| arisut | is the first item in the list | 14:29 |
| pave1 | Yep, thank you. So "child notes" will eventually contain test results? | 14:31 |
| arisut | eventually yes | 14:31 |
| arisut | and after the job finish the result will be pushed to the dashboard | 14:31 |
| pave1 | Could you paste the commands you used to get that going? | 14:31 |
| arisut | # kci-dev checkout --giturl https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git --branch linux-5.10.y-cip --tipoftree | 14:32 |
| pave1 | Thank you, I'm starting my own cheat sheet. Results should be available in ~ hour? | 14:33 |
| arisut | you can choose if sending to staging or production using --instance | 14:33 |
| arisut | in this case was a new release so I sent it to production | 14:33 |
| arisut | # kci-dev --instance production checkout --giturl https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git --branch linux-5.10.y-cip --tipoftree | 14:34 |
| arisut | this was the command | 14:34 |
| arisut | but usually for development staging should be used | 14:34 |
| arisut | https://gist.github.com/aliceinwire/4de8692c9e006a2ddf92717fe3aaef06 | 14:35 |
| arisut | CIP Testing Manual for KernelCI | 14:35 |
| pave1 | Ok. But if I get it wrong it will just load the servers, not cause some serious problems...? | 14:35 |
| arisut | yes probably will just load the servers | 14:36 |
| pave1 | Ok. Normally the results should take about an hour? | 14:36 |
| arisut | depends | 14:36 |
| arisut | we also have a retry function that if boot fails, will retry the test in such cases | 14:37 |
| arisut | so it could take more | 14:37 |
| arisut | sometime lavalabs have boots problems not related to kernel or platform | 14:37 |
| arisut | so we give them 3 try for see if work | 14:38 |
| arisut | of course usually one time is enough | 14:38 |
| arisut | so sometime it could take a bit more | 14:38 |
| pave1 | Good, so perhaps I won't have to hit retry manually. | 14:38 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has joined #cip | 14:39 | |
| arisut | also depend from pending or running tasks | 14:39 |
| *** iwamatsu__81 <iwamatsu__81!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has quit IRC (Ping timeout: 250 seconds) | 14:39 | |
| arisut | if there are many pending tasks it will take more | 14:39 |
| pave1 | (and perhaps on load from other people?) | 14:39 |
| arisut | on staging yes | 14:39 |
| pave1 | aha, makes sense. | 14:39 |
| arisut | production usually is not for kci-dev | 14:39 |
| arisut | this time was a release and could sent to dashboard without problem, so I started it anyway | 14:40 |
| pave1 | Ok, thank you, I'll try to play with it. | 14:41 |
| iwamatsu__ | I connected vx2 board to my lab. so, vx2 board is now available for use as CIP test hardware. | 14:41 |
| arisut | but usually for development it go in staging | 14:41 |
| arisut | remember that staging and production have a different api | 14:41 |
| arisut | and staging have no dashboard | 14:41 |
| pave1 | iwamatsu: So I can just hit retry in gitlab? :-) | 14:41 |
| arisut | staging api viewer is here https://staging.kernelci.org:9000/viewer?search=kind%3Dcheckout&search=created%3E2025-09-04T14:41:47 | 14:42 |
| pave1 | arisut: You are not really making it easy for people, are you? | 14:42 |
| iwamatsu__ | pave1: yes. | 14:42 |
| arisut | production viewer is here https://api.kernelci.org/viewer?search=kind%3Dcheckout&search=created%3E2025-09-10T14:42:42 | 14:42 |
| arisut | you can see now that the child started to come up https://api.kernelci.org/viewer?search=parent%3D68c2dc67991c68a3c7682373 | 14:43 |
| arisut | going back to fix some cip platform on kernelci | 14:43 |
| arisut | have a nice day | 14:43 |
| pave1 | Yes, thank you, have a nice day! | 14:44 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae036005.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 14:46 | |
| *** jki <jki!~jki@62.156.206.40> has quit IRC (Remote host closed the connection) | 15:01 | |
| *** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-48-83.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds) | 17:39 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!