fedora_arm_working_group_meeting
LOGS
15:04:49 <pwhalen> #startmeeting Fedora ARM Working Group Meeting
15:04:49 <zodbot> Meeting started Tue May  3 15:04:49 2022 UTC.
15:04:50 <zodbot> This meeting is logged and archived in a public location.
15:04:50 <zodbot> The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:04:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:04:50 <zodbot> The meeting name has been set to 'fedora_arm_working_group_meeting'
15:04:50 <pwhalen> #chair pwhalen pbrobinson jlinton coremodule
15:04:50 <zodbot> Current chairs: coremodule jlinton pbrobinson pwhalen
15:04:50 <pwhalen> #topic roll call
15:05:00 * jlinton waves
15:05:01 <pwhalen> Sorry for the late start, distracted again
15:05:30 <pwhalen> who else is around for a meeting today?
15:05:56 <jlinton> The sounds of silence?
15:05:57 * nirik was going to mention his armv7 qemu date bug again...
15:07:08 <pwhalen> If no one else is here I think we can skip the meeting. Does anyone have anything pressing to discuss?
15:07:36 <jlinton> No, more a FYI
15:07:37 <jlinton> https://imgur.com/a/YRCgjMQ
15:07:59 <jlinton> thats fedora running bare metal in ACPI mode on a lenvo flex5G, stock kernel/etc (aka I didn't compile anything)
15:08:39 * core_module is here, but doesn't have anything of note to discuss at the meeting.
15:09:19 <pwhalen> nirik: right, sorry that bug slipped my mind. Added to the tracker now
15:09:42 <pwhalen> jlinton: awesome, no wayland?
15:09:45 <nirik> upgrading qemu / edk2-arm didn't change anything... not sure where the bug lies. ;(
15:10:17 <jlinton> That is what it did, I left it at the default.
15:10:40 <jlinton> the gocha's were around blackisting the UFS driver, and manually booting the kernel rather than leaving grub in the path.
15:10:41 <pwhalen> my x86_64 box did the same when I installed a recent nightly
15:11:42 <pwhalen> Ok, lets start now that we have more of a quorum
15:11:51 <pwhalen> #topic 1) ==== Stable Releases ====
15:12:09 <pwhalen> Any new issues in our stable releases?
15:13:28 <pwhalen> Seems lots of people are now hitting the systemd/resolv issue.
15:13:58 <coremodule> ugh.
15:14:16 <coremodule> I haven't heard anything this week, but I haven't looked this week either.
15:14:27 <pwhalen> #info Bug 2074083 - dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
15:14:40 <coremodule> on the systemd/resolv bug
15:14:47 <nirik> I thought it was fixed in updates?
15:15:06 <coremodule> there was an update, but it didn't fix the issue
15:15:27 <nirik> https://bodhi.fedoraproject.org/updates/FEDORA-2022-01079468a3
15:15:27 <coremodule> .bug 2074083
15:15:29 <zodbot> coremodule: 2074083 – dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf' - https://bugzilla.redhat.com/2074083
15:15:30 <nirik> but it's in testing
15:15:43 <nirik> ah, and it did not fix it indeed.
15:17:00 <pwhalen> We've been crying about it in IoT since January.
15:17:24 <pwhalen> Any other issues to discuss?
15:17:40 * pbrobinson is here, sorry I'm late
15:17:54 <pwhalen> welcome back pbrobinson!
15:18:10 <pwhalen> #topic 2) ==== Kernel Status ====
15:18:15 <coremodule> hi pbrobinson. hope your holiday was good down under.
15:18:21 <pwhalen> #info kernel-5.17.5-300.fc36
15:18:21 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1957441
15:18:32 <jforbes> I do have a question regarding dustymabe's request. I figured it worth turning those on for 5.17.6 when it ships. CONFIG_MOTORCOMM_PHY=y and CONFIG_MMC_SDHCI_OF_DWCMSHC=m unless anyone thinks I should hold off?
15:19:11 <pbrobinson> jlinton: right, that's about what expected with acpi, there's no graphics and a lot of other acpi stuff missing
15:19:25 <pbrobinson> jforbes: that was on my list to review this week
15:20:35 <pwhalen> #info kernel-5.18.0-0.rc5.40.fc37
15:20:35 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1960033
15:20:48 <jforbes> pbrobinson: okay, will hold off, 5.17.6 isn't even out for review yet, so probably Thursday or Friday before a real build
15:21:05 <pbrobinson> jforbes: that's what I figured
15:21:44 <pwhalen> Has anyone had a chance to test the latest kernels? Any issues?
15:22:14 <pbrobinson> I've updated a bunch of devices to 5.17.5 today without issues
15:22:27 <pbrobinson> not started testing 5.18 yet but it's on my todo
15:22:30 <jlinton> There was a report on IRC here, of the brcm clock driver being broken (and getting fixed IIRC) so there might be a rpi/DT issue
15:23:05 <pbrobinson> jlinton: I think one of the rpi people posted on that to the list, also on my todo for this week
15:23:37 <pwhalen> #info Please test and report any issues to #fedora-arm or the mailing list.
15:24:04 <pwhalen> #topic 3) ==== Bootloader Status ====
15:24:51 <pbrobinson> so 2022.07-rc1 is built, I suspect there may be some regressions but they should be fixed in rc2, need to look at it myself
15:25:04 <pwhalen> #info grub2-2.06-38.fc36 - https://bodhi.fedoraproject.org/updates/FEDORA-2022-0951a252b0
15:25:47 <pwhalen> #info uboot-tools-2022.07-0.1.rc1.fc37 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1956320
15:26:22 <pwhalen> Be great if people can test while testing the latest F36 RC, add karma to the grub2 update
15:27:21 <pwhalen> #topic 4) ==== Fedora 36 status ====
15:27:31 <pwhalen> #info Fedora 36 Candidate RC-1.3 Available Now!
15:27:31 <pwhalen> #link https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.3_Summary
15:28:09 <pwhalen> #info List of proposed and accepted blockers - https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist
15:30:00 <pwhalen> Any concerns?
15:30:55 <coremodule> nothing here, all my testing has been OK
15:30:59 <coremodule> actually
15:31:10 <pwhalen> doyou think those proposed blockers will be waived?
15:31:23 <pbrobinson> nothing from me but I'm a little behind and still catching up
15:31:44 <coremodule> there is one thing. if someone has a chance to run aarch64 workstation and attempt to open gnome-contacts, close it, then open it again
15:32:01 <coremodule> I was having trouble getting it to open the second time.
15:32:21 <dustymabe> jforbes++
15:32:23 <pwhalen> try again and file a bug?
15:32:25 <dustymabe> pbrobinson++
15:32:25 <zodbot> dustymabe: Karma for pbrobinson changed to 2 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:32:32 <coremodule> pwhalen, yeah, I know the gnome ones will be waived, the wpa-supplicant one won't though
15:32:58 <pwhalen> there are new gnome bugs too, Kamil seemed passionate about one
15:33:15 <coremodule> pwhalen, I will, just wondering if anyone else had seen it
15:33:42 <pwhalen> I havent been doing Workstation testing so I haven't
15:34:37 <pwhalen> Anything else for F36?
15:35:03 <pwhalen> #topic 5) ==== Open Floor ====
15:35:26 <pwhalen> Anything else for today?
15:35:32 <pbrobinson> I think I
15:35:52 <pbrobinson> I've seen the wpa one with a bunch of arm devices so it would be good to get that in TBH
15:37:04 <coremodule> it should be in rc1.3
15:38:14 <pbrobinson> anf I'm guessing updates-testing
15:38:30 <coremodule> yeah
15:38:30 <coremodule> https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c9603c2da
15:41:27 <pwhalen> #endmeeting