15:00:33 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:33 <zodbot> Meeting started Tue Jan 22 15:00:33 2019 UTC.
15:00:33 <zodbot> This meeting is logged and archived in a public location.
15:00:33 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:33 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:33 <pwhalen> #chair pwhalen pbrobinson
15:00:33 <pwhalen> #topic roll call
15:00:33 <zodbot> Current chairs: pbrobinson pwhalen
15:00:41 <pwhalen> morning folks, who's here today?
15:01:14 * pbrobinson o/
15:06:58 * jlinton waves
15:08:33 <pwhalen> howdy jlinton
15:08:46 <pwhalen> lets get started
15:09:06 <pwhalen> #topic 1) ==== Userspace Status  ====
15:09:25 <pwhalen> is anyone aware of an userspace issues?
15:09:36 <pwhalen> s/an/any
15:11:11 <pbrobinson> firefox
15:11:15 <pbrobinson> on ARMv7
15:11:31 <pbrobinson> https://bugzilla.redhat.com/show_bug.cgi?id=1658940
15:11:59 <pwhalen> #info Firefox fails to build on arm - /usr/bin/ld: final link failed: memory exhausted
15:12:12 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=1658940
15:13:11 <pbrobinson> it was having memory build issues but now looks to be a cairo, or maybe neon issue, jlinton not sure if you;d have any cycles to poke by chance?
15:13:37 <jlinton> Yah, I can run a build, the messages in that bug look "odd"
15:14:06 <pwhalen> awesome, thanks jlinton
15:14:10 <jlinton> because they don't look arm specific, and its building on aarch64 right?
15:14:32 <pbrobinson> yep
15:14:48 <jlinton> I've been meaning to check the latest FF's on fedora, because I saw a report on another distro that was having issues with FF again
15:14:53 <pbrobinson> I'm not sure if it's partly to do with some of the changes made around LTO and related either
15:15:27 <pbrobinson> jlinton: a bunch of detail here https://mastransky.wordpress.com/2019/01/08/fedora-firefox-heads-to-updates-with-pgo-lto/
15:15:36 <pwhalen> latest ff on aarch64 was ok, tested gnome on my mustang
15:15:48 <pwhalen> ff in rawhide
15:15:59 <pbrobinson> there's a bunch of interesting stuff and various posts around opt bits and switch to clang vs gcc etc
15:17:08 <pwhalen> any other user space issues?
15:17:54 <pbrobinson> just a note that rawhide now has gcc9 builds in there and to be aware of any issues
15:18:49 <pwhalen> #info Rawhide now includes GCC9, some breakage may occur
15:19:01 <pwhalen> #topic 2) ==== Kernel Status ====
15:19:13 <pwhalen> #info F29: kernel-4.20.3-200.fc29
15:19:13 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1180452
15:19:31 <pbrobinson> yes, so 4.20 is on it's way to f29, it looks OK from my testing
15:19:44 <pwhalen> there was a test day last week for 4.20, all seemed ok on both arm/aarch64
15:20:18 <pwhalen> #info F30: kernel-5.0.0-0.rc3.git0.1.fc30
15:20:19 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1181002
15:20:23 <jlinton> It seems fine on my mcbin/thunderx2/etc, although its failing on my juno, likely a problem with the firmware though.
15:22:21 <pwhalen> there was an issue with nfs with 5.0rc2, but not reproduced.
15:22:27 <pwhalen> https://bugzilla.redhat.com/show_bug.cgi?id=1666868
15:22:52 <pwhalen> that was reported on x86
15:23:12 <pbrobinson> overall we seem OK with both 4.20 and 5.0 rcs to date
15:23:20 <pwhalen> agreed.
15:23:23 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:23:47 <jlinton> No, its been fine everywhere, the juno is running a hacky firmware of mine
15:24:18 <jlinton> (in acpi mode)
15:24:27 <pwhalen> boring is good :)
15:24:32 <pwhalen> #topic 3) ==== Bootloader Status ====
15:24:46 <pwhalen> #info uboot-tools-2019.01-1.fc30 available now
15:24:46 <pwhalen> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=1179800
15:24:58 <pwhalen> I've tested this on a number of devices, no issues so far
15:26:39 <pwhalen> #topic 4) == F30 ==
15:26:40 <pwhalen> #info Latest nominated nightly - https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
15:27:16 <pwhalen> I've not tested this yet, will do so today
15:27:36 <pwhalen> #info F30 Beta Blockers
15:27:43 <pwhalen> #link https://qa.fedoraproject.org/blockerbugs/milestone/30/beta/buglist
15:28:01 <pwhalen> we have one for the usual suspect- initial-setup
15:28:08 <pwhalen> #info initial-setup fails to run with recent anaconda (cannot import name 'initThreading' from 'pyanaconda.threading')
15:28:08 <pwhalen> #link https://bugzilla.redhat.com/show_bug.cgi?id=1666849
15:28:44 <pwhalen> its been fixed and should appear in a compose soon
15:29:12 <jlinton> I'm behind on this too... I will run the clean install on my mcbin & seattle soon.
15:29:20 <pwhalen> thanks jlinton
15:29:29 <pwhalen> any other issues?
15:29:42 <jlinton> and the hikey
15:29:55 <jlinton> Is the mmc patch still in f30?
15:30:03 <pbrobinson> not sure off hand
15:30:23 <pbrobinson> I'm back in the UK next week so I've got a bunch of updates to do
15:31:08 <pwhalen> we also have the armv7 uefi change.
15:31:49 <pwhalen> installs work in qemu with edk2-arm, but the resulting system doesnt boot past the initial efi messages
15:32:04 <pbrobinson> yes, I need to get a few things done and cleaned up there to make it easier to test
15:33:03 <pwhalen> I've not been able to get any additional output when adding debug to the kargs, looks like a possible grub issue
15:34:29 <pwhalen> anything else for f30?
15:34:47 <pbrobinson> nothing for me
15:35:27 <pwhalen> #topic 5)  == Open Floor ==
15:36:45 <pwhalen> anything else for today?
15:38:53 <pwhalen> thanks all!
15:38:55 <pwhalen> #endmeeting