Thursday, 2025-06-19

« Wednesday, 2025-06-18 Index Friday, 2025-06-20 »
*** monstr <monstr!~monstr@nat-108.starnet.cz> has joined #cip05:58
*** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip07:28
*** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 276 seconds)07:28
*** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip07:31
*** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 272 seconds)07:33
*** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip07:41
*** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 248 seconds)07:44
*** monstr <monstr!~monstr@nat-108.starnet.cz> has quit IRC (Ping timeout: 252 seconds)12:39
*** iwamatsu__ <iwamatsu__!~iwamatsu_@14.3.53.227> has joined #cip12:56
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has joined #cip12:57
*** jki <jki!~jki@95.157.49.24> has joined #cip13:00
jkihi!13:00
uli_hello13:00
masamihi13:00
pave1Hi!13:01
iwamatsu__Hi13:01
jkilet's go13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbotMeeting started Thu Jun 19 13:02:08 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbotThe 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
jki#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jkinone13:02
jki513:02
jki413:02
jki313:02
jki213:02
jki113:02
jki#topic Kernel maintenance updates13:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
uli_i pushed 4.413:02
masamiThis week reported 375 new CVEs and 0 updated CVEs.13:03
pave1New -stable release cycle began, so this will be busy. I'm reviewing 6.12.31 and .34.13:03
iwamatsu__I am reviewing 6.12.3413:04
jkiok - anything to add?13:05
jki513:06
jki413:06
jki313:06
jki213:06
jki113:06
jki#topic Kernel release status13:06
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:06
jkiall on track right now13:06
jkianthing to add?13:07
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel testing13:07
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:07
pave1It would be cool to test 6.15, and there's something wrong with bbb target.13:08
pave1I reported it on the list.13:08
jkidoes it affect all bbb instances in all labs?13:08
pave1It looks more random. Hitting retry enough times gets me green mark in the end.13:09
uli_my observation is that if there are two tests running on bbb, the second one passes...13:10
uli_i think one of the boards is bad13:10
uli_i mean running concurrently13:10
jkidifferent devices, just checked - more likely test-case related13:12
jkiwell, I guess someone has to dig deeper13:14
iwamatsu__It seems to happen on the same device.13:14
jkihttps://lava.ciplatform.org/scheduler/device/beaglebone - this one has quite a lot of errors, indeed13:14
iwamatsu__https://lava.ciplatform.org/scheduler/job/128301213:14
iwamatsu__https://lava.ciplatform.org/scheduler/job/128301213:14
jkibut this one as well: https://lava.ciplatform.org/scheduler/device/bbb-iwamatsu-0113:15
iwamatsu__https://lava.ciplatform.org/scheduler/job/128323813:15
jkiand this one: https://lava.ciplatform.org/scheduler/device/bbb-patersonc-0113:15
jkimoybe more issues at once13:15
iwamatsu__It looks like the PHY initialization failed..13:16
jkiunder Linux?13:16
iwamatsu__probably, yes13:17
patersonchttps://lava.ciplatform.org/results/query/~patersonc/bbb-failures?search=&length=100#table13:17
patersoncSorry I'm late13:17
patersoncit looks like every BBB board has issues at times (see link)13:18
jkithat could be a kernel regression then13:18
jkiso - next step?13:20
pave1It looks like it fails on kernels as new as 6.14.13:20
pave1And I remember that board always was "flakey".13:20
pave1Test 6.15 or maybe mainline there, and see if it fails, too?13:20
iwamatsu__https://www.spinics.net/lists/netdev/msg1041291.html13:20
iwamatsu__maybe same issue13:21
iwamatsu__HW issue? https://www.spinics.net/lists/netdev/msg1041715.html13:21
pave1Do we have C3 boards?13:22
pave1Or should we just stick printks() there to affect timing and make the issue go away? :-)13:22
jkimaybe someone from TI has a proposal... :-)13:23
jkibut collecting the HW revisions would likely be a good idea13:23
jkiok, I guess we should continue this topic via the mailing list, also involving the lab operators13:26
patersoncYep13:26
jkianything else on testing?13:27
jki513:27
jki413:27
jki313:27
jki213:27
jki113:27
jki#topic AOB13:27
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:27
jkiother topics for today?13:28
jki513:29
jki413:29
jki313:29
jki213:29
jki113:29
jki#endmeeting13:29
collab-meetbotMeeting ended Thu Jun 19 13:29:16 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:29
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-19-13.02.html13:29
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-19-13.02.txt13:29
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/06/cip.2025-06-19-13.02.log.html13:29
*** 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:29
jkithanks all!13:29
uli_thanks13:29
pave1Thank you!13:29
masamithank you13:29
iwamatsu__Thank you13:29
*** jki <jki!~jki@95.157.49.24> has quit IRC (Quit: Leaving)13:29
*** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:29
*** iwamatsu__ <iwamatsu__!~iwamatsu_@14.3.53.227> has quit IRC (Quit: Client closed)13:32
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip13:35
iwamatsu__It appears to be fixed in 6.12 and later. 929d8490f8790164f5f63671c1c58d6c50411cb213:35
*** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed)13:51
*** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Ping timeout: 265 seconds)14:09
*** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has joined #cip14:10
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip17:40
*** tmerciai2 <tmerciai2!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 276 seconds)17:43
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 276 seconds)21:12
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip21:16
*** tmerciai1 <tmerciai1!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 248 seconds)21:28
*** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Ping timeout: 244 seconds)22:30
*** prabhakalad <prabhakalad!~prabhakar@136.226.168.176> has joined #cip22:30
*** prabhakalad <prabhakalad!~prabhakar@136.226.168.176> has quit IRC (Ping timeout: 260 seconds)22:35
« Wednesday, 2025-06-18 Index Friday, 2025-06-20 »

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