| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:50 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Read error: No route to host) | 05:54 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:56 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:21 | |
| *** toscalix <toscalix!~toscalix@90.167.243.153> has joined #cip | 09:44 | |
| *** uli <uli!~uli@55d4f8c0.access.ecotel.net> has joined #cip | 10:25 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:25 | |
| *** jki <jki!~jki@195.145.170.180> has joined #cip | 11:55 | |
| *** fbezdeka <fbezdeka!~flo@147.161.165.92> has joined #cip | 11:58 | |
| jki | Hi all! | 12:01 |
|---|---|---|
| masami | hello | 12:01 |
| uli | hello | 12:01 |
| iwamatsu | hi | 12:01 |
| patersonc[m] | Hello | 12:02 |
| fbezdeka | Hi! | 12:02 |
| pave1 | Hi! | 12:02 |
| alicef | hi | 12:02 |
| jki | let's go then: | 12:03 |
| jki | #startmeeting CIP IRC weekly meeting | 12:03 |
| collab-meetbot` | Meeting started Thu Aug 4 12:03:02 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:03 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:03 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:03 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | #topic AI review | 12:03 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | 1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm | 12:03 |
| alicef | fbezdeka pr as been merged | 12:04 |
| fbezdeka | Build failures should be resolved, there were some test failures now | 12:04 |
| alicef | https://github.com/kernelci/kernelci-core/pull/1299 | 12:04 |
| jki | great news | 12:05 |
| jki | who's looking into the test failures right now? | 12:05 |
| fbezdeka | Thanks for your support, alicef. | 12:05 |
| fbezdeka | One report was a board/lab issue, and some CVEs were found | 12:06 |
| alicef | we could probably just skip chromebooks as they are not relevant for cip at the moment | 12:07 |
| patersonc[m] | Do you have a link to the nfs issue? | 12:08 |
| fbezdeka | Maybe... I'm not sure. It's still a x68_64 defconfig, isn't it? | 12:08 |
| jki | if that is true, I would not too quickly drop that target | 12:08 |
| alicef | ok | 12:09 |
| fbezdeka | nfs: https://storage.staging.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip69-517-g92709d8ae585/arm/omap2plus_defconfig/gcc-10/lab-cip/baseline-cip-nfs-beaglebone-black.html | 12:09 |
| patersonc[m] | Could have been a lab issue I guess | 12:11 |
| patersonc[m] | Or does it alway happen? | 12:11 |
| patersonc[m] | s/alway/always/ | 12:11 |
| iwamatsu | CIP' | 12:11 |
| iwamatsu | CIP's BBB log: https://lava.ciplatform.org/scheduler/job/719474 | 12:12 |
| fbezdeka | Can't tell if it happens every time... | 12:12 |
| fbezdeka | reported CVEs for 4.4-cip: https://staging.kernelci.org/test/job/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip69-517-g92709d8ae585/plan/smc/ | 12:12 |
| pave1 | Well, if someone wants to translate that to human terms... | 12:13 |
| pave1 | ...but it is probably WONTFIX anyway :-). | 12:13 |
| jki | means we now need filter list for CVE tests?? | 12:14 |
| alicef | the smc cve are probably same as cip lab smc cve | 12:14 |
| alicef | just probably kernelci with a more updated version of smc | 12:14 |
| pave1 | jki: It is arm64, for start. Plus it claims qemu has spectre problem. So ... someone fix the test :-). | 12:15 |
| jki | where are those tests maintained? also in kernelci context? | 12:15 |
| jki | and, yes, arm64 should be filtered both from builds and tests on 4.4-cip | 12:16 |
| alicef | linaro: https://github.com/Linaro/test-definitions/tree/master/automated/linux/spectre-meltdown-checker-test | 12:16 |
| jki | are all CVEs reported by the test already tracked in our https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec? | 12:18 |
| jki | means, do we just need to translate the descisions into a filter list, or do we still need an expert review of them | 12:19 |
| fbezdeka | If arm64 is out of scope for 4.4-cip, I could try to filter that with another kernelci MR | 12:20 |
| jki | fbezdeka: that would be great, TIA | 12:20 |
| jki | anything else about this for now? | 12:21 |
| uli | 'phy \"4a101000.mdio:00\" not found' in https://storage.staging.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip69-517-g92709d8ae585/arm/[...] vs 'net eth0: phy found : id is : 0x7c0f1' in https://lava.ciplatform.org/scheduler/job/719474 | 12:21 |
| uli | it smells to me like something is broken in that first board. | 12:21 |
| uli | or the driver is marginal somehow | 12:22 |
| alicef | also lab cip have some similar error net eth0: phy \"4a101000.mdio:01\" not found on slave 1, err -19 | 12:22 |
| alicef | from https://lava.ciplatform.org/scheduler/job/719474 | 12:23 |
| uli | it might actually not have the second phy, because that occurs in both logs | 12:23 |
| uli | but i don't actually know that board, i just had a look at the log right now | 12:23 |
| masami | I checked. CVE-2018-3615 isn't tracked in cip-kernel-sec. | 12:23 |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 12:26 | |
| jki | ok, then I guess someone should also check that | 12:26 |
| jki | if our tracking is complete | 12:27 |
| masami | CVE-2018-3615 is Intel SGX's problem, arm64 doesn't affect. Intel published micro code for the fix. | 12:27 |
| jki | if nothing needs / can to be done on kernel, we don't need to do anything for it, just ignore it | 12:29 |
| jki | but let's see what all remains after arm64 is filtered | 12:30 |
| jki | next topic? | 12:30 |
| jki | 3 | 12:31 |
| jki | 2 | 12:31 |
| jki | 1 | 12:31 |
| jki | 2. Check cip devices on kernelci old pull request - patersonc | 12:31 |
| patersonc[m] | No time yet, sorry | 12:32 |
| jki | other AIs I missed? | 12:32 |
| jki | 3 | 12:32 |
| jki | 2 | 12:32 |
| jki | 1 | 12:32 |
| jki | #topic Kernel maintenance updates | 12:32 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:32 | |
| uli | reviewed 5.10.135 | 12:33 |
| masami | there was 5 new CVEs and 4 updated CVEs. I think no notable issues. | 12:33 |
| pave1 | 5.10.135 and 136 reviews. | 12:33 |
| pave1 | 4.4-rt release. | 12:34 |
| iwamatsu | I reviewed 5.10.135 | 12:34 |
| pave1 | I'll still need to look at Xen and write mail about that. | 12:34 |
| jki | anything else here? | 12:36 |
| jki | 3 | 12:38 |
| jki | 2 | 12:38 |
| jki | 1 | 12:38 |
| jki | #topic Kernel testing | 12:38 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:38 | |
| patersonc[m] | Most work was on the KernelCI MR, and getting the Renesas lava lab back online | 12:39 |
| patersonc[m] | I don't know if you have any other topics Alice? | 12:39 |
| pave1 | I wonder if we want to start compile-testing various defconfigs for 4.4. I'd even include arm64 and other unsupported architectures if it is easy. | 12:40 |
| pave1 | Avoiding regressions is easy if they are catched soon... | 12:40 |
| patersonc[m] | Didn't we just take out a load of arm64 stuff from 4.4? | 12:41 |
| pave1 | I meant for gitlab. | 12:41 |
| jki | what is the point in doing it in gitlab over kernelci? | 12:41 |
| pave1 | It is what I am currently using. | 12:42 |
| alicef | not much as I stated last time currently kernelci is keeping logs of cip tests indefinetly | 12:43 |
| pave1 | It would be for catching regressions in stuff that is not in ci configs. | 12:43 |
| alicef | so that we can look into old builds and such | 12:43 |
| pave1 | ...like the sound driver jan reported. | 12:43 |
| patersonc[m] | It's pretty easy to add more build configs to the gitlab setup if wanted - let me know the list and I can add | 12:44 |
| patersonc[m] | Presumably we could add to the kernelci setup as well? | 12:44 |
| jki | I agree on having the defconfigs - though that would be been fine with multiv7_defconfig | 12:44 |
| alicef | patersonc[m]: that would be nice | 12:44 |
| jki | but we should really evolve kernelci to be on-par with out gitlab (and rather go much beyond) | 12:45 |
| jki | therefore: same policies | 12:45 |
| fbezdeka | I'm confused a bit now: Should I still remove arm64 builds for kernelci (4.4-cip only)? | 12:45 |
| jki | IMHO, I would disable that for now - can be reverted at any point when we see new value or feel bored | 12:47 |
| jki | I have one more topic related to the BBB: | 12:50 |
| jki | I heard that the cip-kernel-config for 5.10 does not boot | 12:50 |
| jki | does the BBB run in our CI successfully? | 12:50 |
| patersonc[m] | let me check | 12:52 |
| iwamatsu | https://lava.ciplatform.org/scheduler/job/720340 | 12:52 |
| patersonc[m] | It did when we merged it all | 12:52 |
| iwamatsu | BBB is booting with 5.10.y | 12:53 |
| jki | ah, good data point. need to sort out what isar-cip-core is building / should be building as config | 12:53 |
| jki | thanks | 12:53 |
| jki | anything else regarding testing? | 12:54 |
| jki | 3 | 12:54 |
| jki | 2 | 12:54 |
| jki | 1 | 12:54 |
| jki | #topic AOB | 12:55 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:55 | |
| patersonc[m] | o/ | 12:56 |
| patersonc[m] | Did anyone see this message on IRC a few days ago? "So are there any, like, facilities running CIP in prod, right now?" | 12:56 |
| jki | nope | 12:56 |
| jki | pointer? | 12:56 |
| patersonc[m] | just looking | 12:56 |
| patersonc[m] | Where are the logs stored now? | 12:57 |
| patersonc[m] | Anyway, side Q - should more people try and get a persistent IRC connection so we can answer such questions? | 12:58 |
| alicef | use a bouncer | 12:58 |
| alicef | or matrix bridge? | 12:59 |
| patersonc[m] | Found it: https://ircbot.wl.linuxfoundation.org/logs/%23cip/%23cip.2022-08-01.log.html | 12:59 |
| jki | can we set up a bot that replies with "please also try the mailing list"? | 13:01 |
| patersonc[m] | Matrix bridge works for me | 13:01 |
| patersonc[m] | jki: could be an idea | 13:01 |
| jki | or would someone still be able to reach that person after so many days? | 13:01 |
| patersonc[m] | But we can't have it do that to every message | 13:01 |
| jki | yes, we likely need AI :D | 13:02 |
| patersonc[m] | Or change the topic to tell people to contact the ML if there is no reply | 13:02 |
| alicef | in the topic already there is the mailing list link | 13:04 |
| patersonc[m] | pave1: Do you have a list of configs you want adding to the gitlab/kernelci 4.4-cip builds? | 13:04 |
| jki | another topic: I'll likely not be able to run the meetings for the upcoming 3 weeks (travels, vacation) | 13:06 |
| jki | very likely next week, maybe in two weeks, and definitely not in 3 | 13:06 |
| pave1 | patersonc -- will get that to you. | 13:07 |
| patersonc[m] | Thanks | 13:07 |
| iwamatsu | Japan will be a traditional holiday next week. | 13:07 |
| jki | skip next week? | 13:07 |
| pave1 | I'm not sure about next weeks, still hope for some holidays. | 13:08 |
| iwamatsu | if other member is no problem. | 13:08 |
| patersonc[m] | I'm off on the 18th | 13:08 |
| patersonc[m] | pave1: Or raise an issue https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/issues and https://github.com/orgs/kernelci/projects/11 | 13:08 |
| patersonc[m] | pave1: But email is fine | 13:09 |
| pave1 | patersonc> email is better. | 13:09 |
| masami | I may be able to attend next meeting. | 13:10 |
| alicef | by the way recently kernelci mailing is changing afair | 13:10 |
| jki | in any case, someone would have to take the lead for next week first of all | 13:11 |
| alicef | https://groups.io/g/kernelci/topic/92374991#1560 | 13:11 |
| alicef | we are moving to kernelci@lists.linux.dev | 13:12 |
| jki | ok, folks, anything else? | 13:15 |
| pave1 | masami -- can you take a lead next week? It is as easy as #startmeeting etc... | 13:15 |
| masami | pavel: ok. I'll do that. | 13:16 |
| pave1 | logs from last meeting are quite helpful, you can just paste from them. | 13:16 |
| pave1 | Thank you! | 13:16 |
| jki | great, thanks! | 13:17 |
| masami | np | 13:17 |
| jki | so, closing in.... | 13:18 |
| jki | 3 | 13:18 |
| jki | 2 | 13:18 |
| jki | 1 | 13:18 |
| jki | #endmeeting | 13:18 |
| collab-meetbot` | Meeting ended Thu Aug 4 13:18:52 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:18 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/08/cip.2022-08-04-12.03.html | 13:18 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/08/cip.2022-08-04-12.03.txt | 13:18 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/08/cip.2022-08-04-12.03.log.html | 13:18 |
| *** 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 12: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:18 | |
| jki | thank you all! | 13:18 |
| iwamatsu | thank you | 13:19 |
| uli | thanks | 13:19 |
| pave1 | thank you! | 13:19 |
| patersonc[m] | Thanks all | 13:19 |
| masami | thank you | 13:19 |
| alicef | I will be probably away next week 11th | 13:19 |
| alicef | thanks you | 13:19 |
| jki | bye! | 13:19 |
| jki | and happy vacation to all who take it ;) | 13:19 |
| pave1 | Happy vacation and good luck to people around China... | 13:21 |
| fbezdeka | bye! | 13:22 |
| *** jki <jki!~jki@195.145.170.180> has quit IRC (Remote host closed the connection) | 13:23 | |
| *** fbezdeka <fbezdeka!~flo@147.161.165.92> has left #cip | 13:29 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:39 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 13:54 | |
| *** uli <uli!~uli@55d4f8c0.access.ecotel.net> has left #cip (Leaving) | 14:36 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 15:03 | |
| *** toscalix <toscalix!~toscalix@90.167.243.153> has quit IRC (Quit: Konversation terminated!) | 16:42 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 17:02 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 17:51 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 18:20 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 245 seconds) | 19:32 | |
| *** zar <zar!~quassel@mail.nazaryev.ru> has joined #cip | 19:40 | |
| *** zar_ <zar_!~quassel@mail.nazaryev.ru> has quit IRC (Read error: Connection reset by peer) | 19:40 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 252 seconds) | 22:12 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 23:51 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!