Thursday, 2024-11-07

*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 255 seconds)04:45
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip04:46
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip08:06
*** rajm <rajm!~robert@host-81-178-148-108.as13285.net> has quit IRC (Remote host closed the connection)10:50
*** rajm <rajm!~robert@host-81-178-148-108.as13285.net> has joined #cip12:15
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:a117:16f1:68e7:44b1> has joined #cip12:35
*** jki <jki!~jki@195.145.170.159> has joined #cip12:58
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has joined #cip12:59
*** csteiger <csteiger!~csteiger@147.161.170.253> has joined #cip12:59
*** csteiger <csteiger!~csteiger@147.161.170.253> has quit IRC (Remote host closed the connection)12:59
jkihi all13:00
pave1Hi!13:00
*** csteiger <csteiger!~csteiger@dslb-092-072-049-075.092.072.pools.vodafone-ip.de> has joined #cip13:00
iwamatsu__hello13:00
masamihi13:00
patersoncAfternoon all13:00
csteigerHi!13:00
arisuthi13:00
jkiok, let's go13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting started Thu Nov  7 13:01:36 2024 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe 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 review13:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:01
jkithe announcement email draft feels ready, will share later, still polishing on the blog post13:02
jkino other AIs recorded13:02
jki513:03
jki413:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
pave1I'm doing reviews, 6.1.114, 115, 116.13:03
masamiThis week reported 51 new CVEs and 0 updated CVEs.13:03
iwamatsu__I reviewed 6.1.116-rc13:04
jkiare we generating filtering reports for the new CVEs already now?13:06
csteigerI tried my hand on it today for the first time13:06
masamithis one. https://lists.cip-project.org/g/cip-dev/message/1721513:06
jkiah, missed that - nice!13:07
iwamatsu__csteiger: thanks for your work!13:07
csteigerI hope it is useful for you guys :)13:08
jkiwhat would be a next useful step for that?13:08
jkimore architectures? :)13:11
csteigerIf you have wishes let me know, it is very easy to add more stuff13:11
csteigerMore configs, archs etc13:11
jkiopinions? suggestions?13:12
jkiwell, we can also continue this on the list later on13:14
jkianything else on this topic block?13:14
jki513:15
jki413:15
jki313:15
jki213:15
jki113:15
jki#topic Kernel release status13:15
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:15
jkithere are two releases late13:15
jkiany news on 4.19-upstream?13:15
iwamatsu__No update, but rc version has been reeleased13:16
jkiok, that is good13:16
iwamatsu__It may be released in a few days.13:16
jkiformally late is also 5.10-rt, but I suppose that is also waiting for the next 5.10 which is due tomorrow13:16
pave1I'll need to investigate, but release is easy once upstream does it.13:17
jkianything else regarding releases?13:18
jki513:18
jki413:18
jki313:18
jki213:18
jki113:18
jki#topic Kernel testing13:18
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:18
patersoncHello13:18
patersoncThere's an MR open adding LAVA support for the new MCOM platform. I'll get the configs added to the server today for testing, then we can get it merged.13:18
jkithat's great to hear!13:19
arisutkci-dev as been released to pypi, now can be installed by pip install kci-dev13:19
pave1arisut: Wow, nice :-).13:20
arisutwe are planning to add new feature like bisection and artifact download13:20
arisutdocumentation is here https://kernelci.github.io/kci-dev/13:20
jkilooks like this is looking for cip-users now :) - great!13:20
patersonc:)13:21
pave1patersonc: We have failure on 6.11-rc, and it won't go away with retries.13:21
pave1https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/153101512113:21
pave1I did not investigate much more.13:21
patersoncThanks pave1 - I'll take a look13:21
arisutand you can see my talk at OSSJ where I'm talking about kci-dev a bit. Talk @OSSJ: https://www.youtube.com/watch?v=vNMNJAdm-fo13:21
pave1(You have copy in the email).13:22
pave1Thank you!13:22
arisuthttps://pypi.org/project/kci-dev/13:22
arisutis still in beta but feel free to try it and give feedback13:23
patersoncThanks arisut13:23
arisutthanks you13:24
jkianything else on testing?13:25
patersoncNot from me13:25
jki513:26
jki413:26
jki313:26
jki213:26
jki113:26
jki#topic AOB13:26
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:26
patersoncpave1: It looks like there has been a successful boot on BBB for that kernel - just never both in the same GitLab job. Slightly worrying. I'll try and dig further. Maybe iwamatsu__ has some suggestions13:27
pave1Yeah, so for the record, bbb was flakey before. I did run more than few retries in recent history.13:28
iwamatsu__I dont have information about it now, so I also check it.13:28
patersoncpave1: Have you seen a pattern with particular boards failing/not failing?13:28
pave1Not really. It was "bbb failed again, just hit retry, it will work".13:29
jkiwhere does it fail, boot-up? or already in u-boot while loading the kernel?13:30
patersoncI've seen both13:32
pave1One example is:13:32
pave1bootz 0x82000000 - 0x8800000013:32
pave1zimage: Bad magic!13:32
pave1bootloader-commands timed out after 282 seconds13:32
jkithat download issues by u-boot are familiar to us in the xenomai lab13:33
jkiwe plan (for too long) to add some retries there as well13:34
jkistill wondering why LAVA has nothing like that by default...13:34
jkieven worse: this sometimes hits our heathcheck jobs, and then the board is first of all "offline"13:35
jkianyway - will let you know if we happen to find some workarounds for that first13:37
patersoncYea...13:37
jkiother topics for today?13:37
jki513:38
jki413:38
jki313:38
jki213:38
jki113:38
jki#endmeeting13:38
collab-meetbotMeeting ended Thu Nov  7 13:38:57 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:38
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-07-13.01.html13:38
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-07-13.01.txt13:38
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/11/cip.2024-11-07-13.01.log.html13:38
*** 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:38
jkithanks, all!13:39
pave1Thank you!13:39
arisutthanks13:39
masamithank you13:39
patersoncttfn13:39
iwamatsu__thank you13:39
*** csteiger <csteiger!~csteiger@dslb-092-072-049-075.092.072.pools.vodafone-ip.de> has quit IRC (Quit: Leaving)13:39
*** masami <masami!~masami@FL1-118-111-145-206.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:42
iwamatsu__hmm, BBB does not download artifacts13:45
iwamatsu__https://lava.ciplatform.org/scheduler/job/1218595#L29713:45
iwamatsu__And using musb-hdrc for download13:46
iwamatsu__with other test, it uses ethernet device and success. and it is same device (bbb-01). https://lava.ciplatform.org/scheduler/job/1218571#L29113:48
patersoncBut both tests/images are the same? Why would the behaviour change?13:49
iwamatsu__They are the same binary(1218595 and 1218571).13:51
patersoncyea13:51
iwamatsu__I seem to have failed to initialize U-boot.13:55
iwamatsu__Success: https://lava.ciplatform.org/scheduler/job/1218571#L25313:55
iwamatsu__fail: https://lava.ciplatform.org/scheduler/job/1218595#L25813:56
iwamatsu__> Net:   Could not get PHY for ethernet@4a100000: addr 013:56
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)14:15
pave1~.14:25
*** jki <jki!~jki@195.145.170.159> has quit IRC (Quit: Leaving)14:36
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Quit: Konversation terminated!)17:50
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip17:51
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:a117:16f1:68e7:44b1> has quit IRC (Quit: Client closed)19:16
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 260 seconds)20:51
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has joined #cip21:02
*** prabhakalad <prabhakalad!~prabhakar@165.225.197.26> has quit IRC (Ping timeout: 260 seconds)22:34
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:4df6:4669:b8d9:5255> has joined #cip23:57

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!