15:00:12 #startmeeting Fedora ARM Working Group Meeting 15:00:12 Meeting started Tue May 10 15:00:12 2022 UTC. 15:00:12 This meeting is logged and archived in a public location. 15:00:12 The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:12 The meeting name has been set to 'fedora_arm_working_group_meeting' 15:00:12 #chair pwhalen pbrobinson jlinton coremodule 15:00:12 #topic roll call 15:00:12 Current chairs: coremodule jlinton pbrobinson pwhalen 15:00:21 Hi everyone, who is around for an ARM meeting today? 15:02:27 I am around 15:02:32 I'm here 15:03:22 hi jforbes 15:03:24 hi pbrobinson 15:03:33 #topic 1) ==== Stable Releases ==== 15:03:43 #info Fedora 36 officially launches today! 15:05:04 #topic 2) ==== Kernel Status ==== 15:05:09 #info kernel-5.18.0-0.rc6.47.fc37 15:05:14 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1964165 15:05:27 has anyone tried the new kernel? 15:05:42 I haven't yet 15:06:38 #info Please test and report in #fedora-arm any issues. 15:06:42 I wonder if we should have the CLUSTER scheduling turned on. It causes problems on the ampere, and possibly others 15:07:50 (it seems the default was selected a back in the 5.16 timeframe, and I didn't notice errors on the little machines I was mostly using during that timeframe) 15:09:32 maybe so, jforbes could we do that? 15:10:36 I haven't set the configs for 5.18 yet, but I can give that a run 15:10:55 Configs are on my list for this week 15:11:59 cool, thanks 15:11:59 I've got a patch i've been contemplating to get rid of the borken messages, but until that gets clear I think we should probably have it off, or accept that the scheduler domains are broken, at least on ampere. 15:12:29 jlinton: I can turn it off just for aarch64 15:14:04 Yah, I saw its on x86, but didn't pay really close attention to how its being triggered there, if its tied to the PPTT the same way it is on aarch64 then it probably never triggers since I've not seen an x86 with a PPTT yet. 15:14:29 Will not pull that back to 5.17 though, so there will be time to test 5.18 15:15:17 well the machine still boots, but it tosses errors, and the first MC domain has 2 cores each, which probably kills benchmarks that run a lot of threads 15:15:57 jlinton: should show up in builds on rawhide starting tomorrow 15:16:43 thanks jforbes 15:17:12 #topic 3) ==== Bootloader Status ==== 15:17:12 #info grub2-2.06-40.fc37 15:17:13 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1963244 15:17:13 #info uboot-tools-2022.07-0.1.rc1.fc37 15:17:13 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1956320 15:19:46 I haven't tested either, anyone else? 15:21:59 #topic 4) ==== Fedora 37 status ==== 15:22:33 no more armhfp! for better or for worse 15:23:00 (I say better, less to test, hah) 15:23:15 * pwhalen shows up late 15:23:23 hi pwhalen 15:23:31 good mornin'! 15:23:34 #chair pwhalen jforbes 15:23:34 Current chairs: coremodule jforbes jlinton pbrobinson pwhalen 15:24:30 coremodule: Unfortunately I still have to build kernels or we may be in for a bit of an issue when doing stable rebases 15:24:41 Looks reasonable in openqa. Some of the failures look like needle issues 15:25:54 How long could we keep building a few core things for F36/arm? 15:26:07 aka could we extend its life out more than the usual two years? 15:27:24 The extended support version, that zombies on until people lose interest? 15:27:29 Nothing stops people from picking it up, but I dont think in the official koji instance 15:28:11 I would honestly rather not build a single 32bit arm kernel that doesn't have to be built since it is the longest build by a good bitr 15:30:06 Yah, i'm all on board with the lets kill it, because I don't think a full featured distro belongsĀ  on a 32-bit platform at this point. I'm just tossing out random ideas if someone really yells loudly. 15:31:16 #topic 5) ==== Open Floor ==== 15:31:27 Anything else for today? 15:31:45 nothing from me! thanks for picking it up 15:33:37 curious why containers are failing in f35 and not f36 for armhfp 15:34:22 nothing else from me :) 15:34:41 #endmeeting