fedora_arm_and_aarch64_status_meeting
LOGS
15:00:50 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:50 <zodbot> Meeting started Tue Jan 14 15:00:50 2020 UTC.
15:00:50 <zodbot> This meeting is logged and archived in a public location.
15:00:50 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:50 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:50 <pwhalen> #chair pwhalen pbrobinson
15:00:50 <zodbot> Current chairs: pbrobinson pwhalen
15:00:58 <pwhalen> Good morning folks, who's here today?
15:02:01 * jlinton waves
15:02:13 * tdawson is here, though just lurking again today.
15:02:47 <pwhalen> good morning jlinton, tdawson
15:04:04 <pwhalen> looks like just the three of us, perhaps others will join but lets get started
15:04:16 <pwhalen> #topic 1) ==== Userspace Status  ====
15:04:26 <pwhalen> any user space issues?
15:05:22 <pwhalen> #info virt-install unable to find any master var store for loader
15:05:29 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=1782778
15:05:59 <pwhalen> affects aarch64 virt-installs
15:06:41 <pwhalen> #info Should be fixed when libvirt 6.0.0 is released
15:06:42 <jlinton> there is another bug# for the same problem too.
15:07:14 <pwhalen> I believe so
15:09:16 <pwhalen> jlinton, I think it was for another product, but I cant find it offhand
15:09:39 <pwhalen> any other user space issues?
15:09:45 <jlinton> Oh yes your right, I was looking at the RHEL one, and its linked in that bug
15:11:01 <pwhalen> #topic 2) ==== Kernel Status ====
15:11:09 <pwhalen> #info F31: kernel-5.4.11-202.fc31
15:11:10 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1428939
15:11:33 <pwhalen> not aware of any 5.4 issues
15:12:23 <pwhalen> #info F32: kernel-5.5.0-0.rc6.git0.1.fc32
15:12:23 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1428886
15:13:04 <pwhalen> 5.5 is moving along, has anyone seen any issues with various RC's?
15:13:50 * tdawson hasn't tested any yet, so no :)
15:13:52 <pwhalen> I need to test some more of the enterprise hardware.
15:14:00 <jlinton> No, I've been running both those kernels on the honeycomb and I haven't seen any kernel specific problems
15:14:51 <pwhalen> I did see an issue testing on aws, will revisit. Failed to boot but didnt really see why
15:15:06 <pwhalen> on a1.metal
15:15:33 <pwhalen> #info No known issues.
15:15:43 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:16:13 <pwhalen> #topic 3) ==== Bootloader Status ====
15:16:23 <pwhalen> #info uboot-tools-2020.01-1.fc32
15:16:23 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1426659
15:17:07 <pwhalen> some issues with garbled text in uboot on the rpi3, anyone else seen that? Or on other hardware?
15:17:43 <jlinton> miniuart or pl011?
15:18:09 <pwhalen> this was on display
15:18:46 <pwhalen> it booted ok, and I think its only on the aarch64
15:18:51 <pwhalen> saw this last night
15:20:52 <pwhalen> #topic 4) ==== Fedora 32 ====
15:21:02 <pwhalen> #info Latest nominated nightly
15:21:03 <pwhalen> #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
15:22:01 <pwhalen> #info OpenQA testing
15:22:08 <pwhalen> #link https://openqa.stg.fedoraproject.org/tests/overview?distri=fedora&version=Rawhide&build=Fedora-Rawhide-20200112.n.0&groupid=6
15:22:49 <pwhalen> looking much better now, there were lots of tests failures due to some AVC's but those are now fixed
15:23:36 <pwhalen> I'll take a look at the remaining failures
15:24:49 <pwhalen> any f32 issues?
15:25:23 <pwhalen> #info Fedora 32 Schedule
15:25:40 <pwhalen> #info 2020-01-21 - Proposal submission deadline (Self Contained Changes)
15:25:52 <pwhalen> info 2020-01-22 - Mass rebuild
15:26:06 <pwhalen> #info 2020-01-22 - Mass rebuild
15:26:12 <jlinton> I will spin it up on hardware that has more functionality/drivers than the rpi4/honeycomb I've been running on recently.
15:26:48 <pwhalen> jlinton, you running rpi4 with uefi?
15:26:52 <jlinton> Both of them are basically usb only machines
15:27:07 <jlinton> yes, i've been running it for a month or so
15:27:18 <jlinton> (ACPI mode)
15:27:26 <pwhalen> nice, was going to look for that too, if you have alink please share
15:27:33 <jlinton> but its quite restricted at the moment
15:27:56 <pwhalen> and thanks for the testing, very appreciated
15:28:20 <jlinton> I have a set of patches for the nic, which I should probably post publicly soon as I don't appear to be getting the time to finish the edk2 nic driver
15:29:27 <jlinton> https://github.com/pftf
15:29:49 <pwhalen> cool, thanks
15:29:49 <jlinton> There aren't any binary artifacts at the moment, and its a work in progress
15:30:18 <pwhalen> right, understood
15:31:46 <pwhalen> any other issues, concerns for f32?
15:33:02 <pwhalen> #topic 5)  == Open Floor ==
15:34:48 <pwhalen> #endmeeting