14:00:15 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
14:00:15 <zodbot> Meeting started Tue Mar 10 14:00:15 2020 UTC.
14:00:15 <zodbot> This meeting is logged and archived in a public location.
14:00:15 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:15 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:15 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
14:00:15 <pwhalen> #chair pwhalen pbrobinson jlinton
14:00:15 <zodbot> Current chairs: jlinton pbrobinson pwhalen
14:00:24 <pwhalen> Good morning folks, who's here today?
14:00:26 * pbrobinson is here
14:02:50 <pwhalen> ok, lets get started
14:02:59 <pwhalen> #topic 1) ==== Userspace Status  ====
14:03:16 <pwhalen> any user space issues?
14:04:05 <pbrobinson> the qemu graphics issue is userspace or kernel?
14:04:54 <pwhalen> seems to be the kernel, installing 5.4 on the guest 'fixes' it
14:05:10 <pwhalen> 5.5 has a slight issue, and 5.6 is completely broken
14:05:45 <pwhalen> there's a few issues that overlap with the 32 bugs, so I'll save them for that topic
14:05:52 <pbrobinson> OK
14:05:54 <pwhalen> s/32/f32
14:06:07 <pwhalen> #info No issues reported.
14:06:13 <pwhalen> #topic 2) ==== Kernel Status ====
14:06:26 <pwhalen> #info F32: kernel-5.6.0-0.rc5.git0.1.fc32
14:06:26 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1473120
14:06:38 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1473120
14:06:50 <pbrobinson> I've tested 5.6-rc5 across about 20 different devices, mostly just boot testing and it's looking mostly OK
14:07:23 <pwhalen> very nice! :) thanks. Was just getting into testing it all over
14:08:29 <pwhalen> I'll check the virt display issue, but not holding my breath. Easily reproduced if anyone wants to - boot a disk image with vnc or spice graphics and you'll see the corruption
14:09:52 <pwhalen> any other kernel news?
14:10:08 <pbrobinson> nothing of real note
14:11:13 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
14:11:25 <pwhalen> #topic 3) ==== Bootloader Status ====
14:11:37 <pwhalen> #info uboot-tools-2020.04-0.4.rc3.fc32
14:11:37 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1471595
14:11:37 <pwhalen> #link https://bodhi.fedoraproject.org/updates/FEDORA-2020-927900c9a3
14:12:03 <pbrobinson> I would expect us to have rc4 today if memory serves
14:12:11 <pwhalen> #info Please test and provide karma.
14:12:18 <pbrobinson> If it happens I'll aim to get a build by the end of the week
14:12:34 <pwhalen> cool, no issues so far for me. Will provide karma in a few
14:12:46 <pbrobinson> but yes, please test and add karma to this one
14:13:57 <pwhalen> anything else for bootloader?
14:14:41 <pwhalen> #topic 4) ==== Fedora 32 ====
14:14:59 <pwhalen> #info Latest nominated nightly
14:15:00 <pwhalen> #link https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
14:15:19 <pwhalen> #link https://qa.fedoraproject.org/blockerbugs/milestone/32/beta/buglist
14:15:43 <pwhalen> for us, we have:
14:15:51 <pwhalen> #info Display corruption on aarch64 virtual machines
14:15:59 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=1807661
14:16:46 <pwhalen> this one needs attention. Seems to be the kernel as I mentioned, installing 5.4 on the guest and it looks fine. 5.5 shows some issues but it gets 'repaired' on screen
14:17:24 <pbrobinson> jlinton_: do you have some cycles to take a look at that?
14:17:28 <pwhalen> the other arm/aarch64 issue should be fixed, pending testing. Now flagged as a FE but not in todays compose to test it
14:18:12 <pbrobinson> there was some reworks of some of the virt gpu stuff upstream around TTM and memory manager bits I wonder if that had an effect
14:18:16 <pwhalen> other being - bootloader entry missing after installation on armhfp
14:19:43 <pbrobinson> right, that's fixed in the next anaconda something build right?
14:19:59 <pwhalen> right, built now just needs to be pulled in
14:20:10 <pwhalen> which I had hoped would happen today, alas.
14:21:12 <pwhalen> #info Fedora 32 Beta Go/NoGo - 2020-03-12
14:21:42 <pwhalen> unlikely to be a go, we have unresolved blockers and no RC's but I've been wrong before
14:23:01 <pwhalen> anything else for F32? Concerns? Issues not mentioned?
14:23:58 <pbrobinson> nothing i can think of or anything I've found
14:24:07 <pbrobinson> there's the usual rpi4 bits
14:24:36 <pbrobinson> it works in the "supported" use cases and I'm trying to get more polish on it for GA
14:25:08 <pwhalen> right, the latest disk images hit that gpio issue which drops us to dracut. Minimal boots to initial-setup
14:25:57 <pwhalen> #topic 5)  == Open Floor ==
14:26:27 <pwhalen> Anything else?
14:26:51 <pbrobinson> I'd just ask for people to test Workstation on various aarch64 devices and report to the mailing list or IRC
14:27:55 <pwhalen> agreed! thanks. Workstation should look good on any device with 2GB of RAM and accelerated graphics. I've been using it on the Pine64 Plus
14:28:33 * pwhalen leaves it open for another minute or two
14:30:27 <pwhalen> #endmeeting