16:00:36 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
16:00:36 <pwhalen> #chair pwhalen pbrobinson coremodule jlinton
16:00:36 <zodbot> Meeting started Tue Feb 22 16:00:36 2022 UTC.
16:00:36 <zodbot> This meeting is logged and archived in a public location.
16:00:36 <zodbot> The chair is pwhalen. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:36 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
16:00:36 <zodbot> Current chairs: coremodule jlinton pbrobinson pwhalen
16:00:36 <pwhalen> #topic roll call
16:00:44 * jlinton waves
16:01:01 <pwhalen> Good morning jlinton
16:01:04 * coremodule is here
16:01:26 * nirik waves from the cheap seats in the back
16:02:04 * pwhalen gives it a minute for others to join
16:04:18 <pwhalen> #topic 1) ==== Userspace Status  ====
16:04:40 <pwhalen> Any new user space issues?
16:06:08 <pwhalen> #info No new issues reported.
16:06:14 <pwhalen> #topic 2) ==== Kernel Status ====
16:06:20 <pwhalen> https://www.irccloud.com/pastebin/cL2SYfg5/
16:06:28 <pwhalen> #info  	kernel-5.17.0-0.rc5.102.fc36
16:06:28 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1921436
16:06:48 <jlinton> Well I guess the good news is that the public dev builds of win11/arm now can boot fedora.
16:07:04 <pwhalen> Yesterday was a holiday here, so I have yet to start testing this
16:07:16 <pwhalen> nice :)
16:07:22 <jlinton> so that expands fedora support to a small selection of laptops if your willing to run it in a VM and maximize the window.
16:08:15 <pwhalen> certainly better than nothing at all
16:08:16 <jlinton> Although the net/disk perf isn't great on the machine i've been testing it on using the hyperv devices rather than pci passthrough/etc.
16:09:26 <pwhalen> jlinton: what device are you testing on?
16:09:54 <jlinton> Lenovo 5G
16:11:04 <pwhalen> cool
16:11:18 <pwhalen> has anyone had a chance to test 5.17rc5? any new issues?
16:11:24 <jlinton> Flex 5G, but that device is discontinued, but there are a couple others.
16:11:52 <jlinton> I'm still on Rc4, since I had yesterday off too.
16:12:21 <pwhalen> #info early kernel panic on aarch64 with kernel-5.17.0-0.rc2.20220202+
16:12:21 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=2053214
16:12:39 <jlinton> I got my seattle running rc4 though, there is a strange splat related to some i2c bus, but the machine seems to work otherwise.
16:12:54 <pwhalen> I'll check to see if there has been any change
16:14:01 <pwhalen> jlinton: yea? Interesting, I need to recheck then, it didnt boot for me at all. Acpi or dt?
16:14:09 <jlinton> ACPI, whats DT?
16:14:43 <pwhalen> device tree
16:15:02 <pwhalen> :)
16:15:03 <jlinton> I've hit a problem with an older kernel (5.12 IIRC), but a couple other people here chimed up they were running newer kernels on softiron1k's.
16:15:58 <pwhalen> hrm, ok.
16:16:06 <jlinton> so it sounds like both the AMI and the EDK2 firmware boots.
16:16:26 <jlinton> I don't have an xgene, other than maybe the m400's in beaker.
16:16:42 <pwhalen> #info RPi4 wired network fails - eth0 (bcmgenet): transmit queue 1 timed out
16:16:42 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=2053729
16:16:57 <walicki> For the past few days I've been running a RaspPi with the 5.17.0-0.rc4.96.fc36.aarch64 kernel without any issues
16:17:38 <pwhalen> walicki: using wifi?
16:18:28 <walicki> Yes, wifi is working.
16:18:34 <pwhalen> #info pbrobinson submitted a patch for the rpi4 ethernet issue
16:18:44 <coremodule> 5.17.0-0.rc4.96.fc36.aarch64 has worked for me on RPi4, minus ethernet
16:19:01 <walicki> I'm running it on a RaspPi 3b+
16:19:22 <jlinton> ah, yah, not a genet.
16:19:58 <pwhalen> walicki: cool, thanks
16:20:03 <pwhalen> any other kernel issues?
16:20:16 <coremodule> nothing else found here
16:20:38 <jlinton> Does WoL actually work on the rpi4? I thought there was a HW/firmware issue that kept it from working at all.
16:21:19 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
16:21:41 <pwhalen> jlinton: I dont think so based on what Peter said this morning
16:22:08 <jlinton> The mcbin nic fix was merged too.
16:22:34 <pwhalen> great
16:22:41 <pwhalen> #topic 3) ==== Bootloader Status ====
16:22:41 <pwhalen> #info uboot-tools-2022.04-0.2.rc2.fc36
16:22:41 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1918654
16:23:05 <pbrobinson> sorry, head in other things
16:23:13 <pwhalen> Has anyone hit any issues with the new uboot?
16:23:19 <pwhalen> no worries, thanks for joinin g
16:23:31 <pbrobinson> it's seems OK, still working on the nano bits
16:23:45 <pbrobinson> spent some time kernel wise on rpi
16:24:00 <pbrobinson> I think I know the issue with the rpi400 too
16:24:43 <pbrobinson> but the upstream DT for that is limited compared to firmware so IMO that's still the better option
16:25:44 <pwhalen> OK
16:27:15 <pwhalen> #topic 4) ==== Fedora 36 ====
16:27:19 <pbrobinson> jlinton: no the WOL doesn't work, it looks like the WOL IRQ isn't mapped, but the driver there in general is ugly, it reports it, and the crash was it was querying an IRQ that was optional
16:28:37 <pwhalen> #info Fedora 36 Schedule - https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
16:28:37 <pwhalen> #info Beta Freeze - 2022-02-22
16:29:05 <jlinton> Yah, which would imply it would hit ACPI as well, but somehow it seemed to dodge the problem. (since we don't have a WoL interrupt resource either).
16:29:13 <pwhalen> #info F36 Beta Bugs - https://qa.fedoraproject.org/blockerbugs/milestone/36/beta/buglist
16:30:36 <pbrobinson> jlinton: the driver was broken but still worked because two breaks makes a fix right? One thing was fixed which uncovered the other break
16:33:00 <walicki> One side note on my 5.17.0-0.rc4.96.fc36.aarch64 kernel testing on the RPi 3B+, I did have to jiggle the wifi.  I disabled IPv6 via /etc/sysctl.conf -  But the wifi interface IPv6 issues might have been around for a while.  Don't want to call it a bug.  Just my WiFi LAN configuration.
16:34:12 <pwhalen> #info OpenQA tetsing -  https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=36&build=Fedora-36-20220221.n.0&groupid=5
16:34:12 <pbrobinson> walicki: IPv6 works on my 10 odd RPi devices, I run a native dual stack on my network
16:35:01 <walicki> Yeah - I can walk back the config changes to see if I can reproduce the spurious wlan issue.
16:35:09 <pwhalen> initial-setup looks to have failed on the aarch64  Server/Minimal images
16:36:45 <pwhalen> #info GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available
16:36:45 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=2017043
16:37:34 <pwhalen> This is our only accepted blocker right now, looks to have stalled
16:38:23 <pwhalen> Anything else for f36?
16:38:28 <pbrobinson> anyone seen any actual movement on that?
16:39:05 <pwhalen> None, likely needs a nudge
16:40:38 <pwhalen> #topic 5)  == Open Floor ==
16:40:50 <pwhalen> nirik: did you have something?
16:41:20 <nirik> is that weird armv7 compressing corrupt thing still happening? I looked at it a little, but didn't see anything obvious. ;(
16:41:56 <pwhalen> I have yet to see it again, yesterdays compose looked ok
16:42:22 <nirik> ah ha, ok.
16:43:04 <pwhalen> I'll update the ticket if I see it again
16:45:12 <nirik> great.
16:45:41 <pwhalen> #endmeeting