16:01:04 #startmeeting Fedora ARM and AArch64 Status Meeting 16:01:04 Meeting started Tue Feb 15 16:01:04 2022 UTC. 16:01:04 This meeting is logged and archived in a public location. 16:01:04 The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:01:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:04 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 16:01:04 #chair pwhalen pbrobinson coremodule jlinton 16:01:04 Current chairs: coremodule jlinton pbrobinson pwhalen 16:01:04 #topic roll call 16:01:14 * pbrobinson o/ 16:01:21 Good morning folks, who's here today? 16:01:27 good morning pwhalen 16:01:28 * coremodule is here 16:01:39 hi pbrobinson 16:01:59 hey 16:02:28 ok, lets get started 16:02:32 #topic 1) ==== Userspace Status ==== 16:02:41 Any new user space issues? 16:03:00 nothing here 16:03:13 nothing specific. I think there's still some fall out from the gcc 12 landing 16:03:35 there was an ARMv7 bug there, but that's fixed 16:05:46 #info Some issues after gcc12 landed, including an ARMv7 bug that is now fixed. 16:05:56 #topic 2) ==== Kernel Status ==== 16:06:04 #info kernel-5.17.0-0.rc4.96.fc36 16:06:04 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1917827 16:06:22 A couple of bugs in 5.17 16:06:33 #info early kernel panic on aarch64 with kernel-5.17.0-0.rc2.20220202+ 16:06:33 #link https://bugzilla.redhat.com/show_bug.cgi?id=2053214 16:07:13 There is a mcbin nic failure with older edk2 firmwares 16:07:16 I've only seen that one on the Mustang and Seattle so far. Need to test more enterprise hardware 16:07:26 The patch is posted. 16:07:41 Yah, my seattle stopped booting too, but with an older kernel. 16:08:02 jlinton, nice. Are you able to look at the above? 16:08:58 jlinton: my macbin firmware is their SystemReady 1.0 rev firmware, last I looked it was the latest one. Is there a later one, or what changed? 16:09:15 older working firmware regressed with the new kernel. 16:09:33 you mean the newer kernel regressed ;-) 16:09:43 its a fairly simple fix, to avoid a null pointer. 16:10:00 yah, 4.17 regressed what was working with 4.16 16:10:16 I had an issue with 5.16 I think 16:10:31 I will have to reboot to recheck, it's currently on 5.15.18 16:11:17 #info RPi4 wired network fails - eth0 (bcmgenet): transmit queue 1 timed out 16:11:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=2053729 16:11:21 I found my second mcbin, maybe I should run it with the latest firmware and verify that. 16:15:22 While testing 5.17 RC4, I didnt see the RPi4 lockup in Gnome. coremodule if you test Workstation, can let me know if you do? 16:15:44 wilco, I'll be looking at it later today on RPi4 and will let you know 16:16:14 thx! 16:17:34 And the Jetson NX has some issues with 5.17 as well 16:17:40 I'm not sure if any of my rpi4 are on wired network 16:17:53 I will be doing that shortly and testing the PoE pieces 16:18:05 pbrobinson: that was why I didnt notice initially as well 16:18:36 Any other kernel issues? 16:18:54 #info Please test and report any issues to the list or #fedora-arm. 16:19:26 PoE "just works" unless you trying to test the fan on the official poe board 16:19:43 I need to retest clearfog-lx2 as it wasn't working but it's had issues with 5.15+ 16:20:15 jlinton: yes, I meant all of the HAT, I'm aware the PoE side is PnP 16:21:04 I want to see whether RPi downstream went to their upstream driver with their 5.15 rebase for the overlays or whether they still are using the non upstream variant 16:22:19 #topic 3) ==== Bootloader Status ==== 16:23:24 #info uboot-tools-2022.04-0.1.rc1.fc36 16:23:24 #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1911839 16:23:40 Looking ok so far. Has anyone hit any issues? 16:23:56 #info Please test and report any issues to the list or #fedora-arm. 16:23:57 has been good for me 16:25:57 #topic 4) ==== Fedora 36 ==== 16:25:57 there's an RC2 out upstream 16:25:58 I 16:26:05 #undo 16:26:05 Removing item from minutes: 16:26:35 I've been working to get Jetson Nano booting using FW DT, it's not quite there yet but I'm hoping I'll have support there before beta freeze 16:26:42 #info uboot-tools-2022.04-0.1.rc2.fc36 expected RSN. 16:27:17 That would be nice for iot and server. 16:27:27 #topic 4) ==== Fedora 36 ==== 16:28:15 #info F36 Beta Freeze - 2022-02-22 16:28:24 #info Fedora 36 Schedule - https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html 16:29:20 I think overall we're looking OK 16:29:21 #info Bug list - https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist 16:29:33 anyone tested Pinebook Pro, I need to power mine back up 16:29:58 pbrobinson: yes, tested with rc4 yesterday. I do need to update uboot for it, still using an older version 16:31:00 There are some general issues with workstation, but it seemed to be working pretty good 16:31:12 so I noticed ffmpeg landed into main Fedora in some weird lobotomised state but in theory it should be able to use the HW offload, anyone want to play? 16:31:37 HW offload of rk3399 and allwinner a64 16:32:43 so maybe we could look at a big bucks bunny reference test for generally testing these things to work out how it all works 16:32:54 I think Jetson Nano will have it soon too 16:33:16 I can look as I test 16:35:10 #info OpenQA testing - https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20220215.n.0&groupid=5 16:37:10 Anything else for F36? Concerns or issues not reported? 16:38:48 #topic 5) == Open Floor == 16:39:41 #info ARMv7 now disabled in Rawhide (Fedora 37). 16:41:04 * pwhalen leaves it open for a couple more minutes. 16:43:08 #endmeeting