13:02:08 <jki> #startmeeting CIP IRC weekly meeting 13:02:08 <collab-meetbot> Meeting 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:08 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:08 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting' 13:02:16 <jki> #topic AI review 13:02:22 <jki> none 13:02:31 <jki> 5 13:02:32 <jki> 4 13:02:34 <jki> 3 13:02:35 <jki> 2 13:02:37 <jki> 1 13:02:39 <jki> #topic Kernel maintenance updates 13:02:59 <uli_> i pushed 4.4 13:03:01 <masami> This week reported 375 new CVEs and 0 updated CVEs. 13:03:18 <pave1> New -stable release cycle began, so this will be busy. I'm reviewing 6.12.31 and .34. 13:04:01 <iwamatsu__> I am reviewing 6.12.34 13:05:45 <jki> ok - anything to add? 13:06:15 <jki> 5 13:06:17 <jki> 4 13:06:19 <jki> 3 13:06:20 <jki> 2 13:06:22 <jki> 1 13:06:25 <jki> #topic Kernel release status 13:06:34 <jki> all on track right now 13:07:02 <jki> anthing to add? 13:07:21 <jki> 5 13:07:23 <jki> 4 13:07:24 <jki> 3 13:07:26 <jki> 2 13:07:27 <jki> 1 13:07:30 <jki> #topic Kernel testing 13:08:14 <pave1> It would be cool to test 6.15, and there's something wrong with bbb target. 13:08:19 <pave1> I reported it on the list. 13:08:56 <jki> does it affect all bbb instances in all labs? 13:09:29 <pave1> It looks more random. Hitting retry enough times gets me green mark in the end. 13:10:04 <uli_> my observation is that if there are two tests running on bbb, the second one passes... 13:10:15 <uli_> i think one of the boards is bad 13:10:29 <uli_> i mean running concurrently 13:12:41 <jki> different devices, just checked - more likely test-case related 13:14:16 <jki> well, I guess someone has to dig deeper 13:14:16 <iwamatsu__> It seems to happen on the same device. 13:14:49 <jki> https://lava.ciplatform.org/scheduler/device/beaglebone - this one has quite a lot of errors, indeed 13:14:53 <iwamatsu__> https://lava.ciplatform.org/scheduler/job/1283012 13:14:53 <iwamatsu__> https://lava.ciplatform.org/scheduler/job/1283012 13:15:04 <jki> but this one as well: https://lava.ciplatform.org/scheduler/device/bbb-iwamatsu-01 13:15:10 <iwamatsu__> https://lava.ciplatform.org/scheduler/job/1283238 13:15:23 <jki> and this one: https://lava.ciplatform.org/scheduler/device/bbb-patersonc-01 13:15:42 <jki> moybe more issues at once 13:16:06 <iwamatsu__> It looks like the PHY initialization failed.. 13:16:43 <jki> under Linux? 13:17:10 <iwamatsu__> probably, yes 13:17:41 <patersonc> https://lava.ciplatform.org/results/query/~patersonc/bbb-failures?search=&length=100#table 13:17:46 <patersonc> Sorry I'm late 13:18:00 <patersonc> it looks like every BBB board has issues at times (see link) 13:18:09 <jki> that could be a kernel regression then 13:20:01 <jki> so - next step? 13:20:04 <pave1> It looks like it fails on kernels as new as 6.14. 13:20:13 <pave1> And I remember that board always was "flakey". 13:20:33 <pave1> Test 6.15 or maybe mainline there, and see if it fails, too? 13:20:48 <iwamatsu__> https://www.spinics.net/lists/netdev/msg1041291.html 13:21:01 <iwamatsu__> maybe same issue 13:21:50 <iwamatsu__> HW issue? https://www.spinics.net/lists/netdev/msg1041715.html 13:22:07 <pave1> Do we have C3 boards? 13:22:23 <pave1> Or should we just stick printks() there to affect timing and make the issue go away? :-) 13:23:19 <jki> maybe someone from TI has a proposal... :-) 13:23:55 <jki> but collecting the HW revisions would likely be a good idea 13:26:26 <jki> ok, I guess we should continue this topic via the mailing list, also involving the lab operators 13:26:38 <patersonc> Yep 13:27:02 <jki> anything else on testing? 13:27:36 <jki> 5 13:27:38 <jki> 4 13:27:40 <jki> 3 13:27:41 <jki> 2 13:27:43 <jki> 1 13:27:45 <jki> #topic AOB 13:28:39 <jki> other topics for today? 13:29:06 <jki> 5 13:29:08 <jki> 4 13:29:10 <jki> 3 13:29:12 <jki> 2 13:29:14 <jki> 1 13:29:16 <jki> #endmeeting