15:00:22 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:22 <zodbot> Meeting started Tue Aug 23 15:00:22 2016 UTC.  The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:22 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:22 <pwhalen> #chair pwhalen pbrobinson dgilmore hrw dmarlin yselkowitz jonmasters ahs3 msalter
15:00:22 <zodbot> Current chairs: ahs3 dgilmore dmarlin hrw jonmasters msalter pbrobinson pwhalen yselkowitz
15:00:29 <pwhalen> good morning folks, whos here today?
15:01:03 * pbrobinson o/
15:02:47 <cov> hi
15:03:04 <pwhalen> good morning cov, welcome
15:03:32 <pbrobinson> right let's get this show on the road
15:03:40 <pwhalen> #topic 1) ==== Package Status & Issues  ====
15:04:42 <pbrobinson> not problem packages
15:05:05 <pbrobinson> #info f26 stats: statistics: {'older': 44, 'local_only': 1, 'remote_only': 279, 'same': 18098, 'newer': 0, 'total_missing_builds': 51}
15:05:31 <pbrobinson> #info f25 stats: statistics: {'older': 50, 'local_only': 1, 'remote_only': 277, 'same': 18094, 'newer': 0, 'total_missing_builds': 57}
15:05:40 <pwhalen> #info No current build issues.
15:05:43 <pwhalen> very nice.
15:06:05 <pbrobinson> I spent some time over the last week going through all of the "older" and "remote_only" to see what was missing etc
15:06:24 <pbrobinson> #info wine stack now bootstrapped info F-25+
15:07:07 <pwhalen> anything of interest for us in remote or older?
15:07:28 <pbrobinson> #info looking for people interested in helping bootstrap fpc (pascal), D lang, sbcl (lisp) and chromium on aarch64
15:07:50 <pbrobinson> there's the above bits plus mono and a few randoms
15:08:09 <pbrobinson> I've been checking Exclude/Exclusive arches etc in preparation for merging
15:08:44 <pbrobinson> overall it's the best we've looked ever (as it should be)
15:09:08 <pbrobinson> we should have mono shortly, I've engaged with the maintainer and we'll have support with mono 4.6
15:09:30 <pbrobinson> that should land when mono 4.6 gets to beta phase
15:10:20 <pwhalen> #info Mono to be supported with 4.6, to land when it gets to the Beta phase.
15:10:47 <pwhalen> anyone have anything else to add?
15:11:24 <pwhalen> #topic 2) ==== Kernel Status ====
15:12:06 <pwhalen> armv7, i think we're looking pretty good thanks to a bunch of fixes from pbrobinson.
15:12:48 <pbrobinson> #info 4.7.2 on it's way to Fedora 24 and 23 updates-testing very soon. Please test and report issues. Looks OK in my testing
15:13:01 <pwhalen> #info Latest kernel - kernel-4.8.0-0.rc3.git0.1.fc25
15:13:24 <pbrobinson> latest rawhide/25 kernel is now 4.8 RC3, it's by no means perfect
15:13:32 <pbrobinson> some known issues with BBone MMC
15:13:35 <pwhalen> #info Adds fix for RTC crash on ARMv7 am33xx devices
15:13:41 <pbrobinson> quite probably other issues.
15:15:07 <pbrobinson> #info test lastest 4.8 kernels and report issues
15:15:34 <pwhalen> for aarch64. Im looking at a crash when booting the installer with 4.8.0-0.rc2.git3.1.fc25.aarch64
15:15:41 <pwhalen> on the mustang, seattle is ok
15:15:54 <pwhalen> might be firmware as this is quite old
15:16:01 <pbrobinson> #info 4.8 rc2 git snapshot 3 is now in Fedora 25 GA. It has support on aarch64 for ACPI PCI-e, NUMA and Cavium Thunder X so please test this platform if you have access
15:16:54 <pbrobinson> anyone else have any questions/queries about either the 4.7.x stable kernels or 4.8 devel kernels?
15:17:02 <pwhalen> any other kernel testing, news?
15:17:19 <cov> are folks booting ACPI or devicetree on the Thunder?
15:17:46 <pbrobinson> cov: TBH I don't have access to test, no reports but I believe ThunderX should use ACPI
15:18:01 <pbrobinson> so no idea really :)
15:18:05 * pwhalen tests with Mustang, Seattle and QEMU
15:18:55 <cov> I can't boot on QDF2432 because http://codeaurora.org/cgit/quic/server/kernel/commit/?h=cov/4.8-rc2-testing&id=edc7986d4d405daebaf2f66269b353da579fce5f is missing
15:19:07 <cov> it's a CPU erratum that's been nacked upstream
15:19:49 <cov> I've started testing on an emulation platform that doesn't suffer from that erratum, but it's slow and I don't have results yet
15:20:03 <pbrobinson> cov: OK, do we need to enable other options in the kernel configs?
15:20:32 <cov> no, the patch isn't in Fedora and I've been unsure of whether to ask for it to be included or find some other way to deal with it
15:21:23 <cov> for example applying the patch and building locally or using a JTAG script to work around the issue
15:21:34 <pbrobinson> cov: well depending on impact on other platforms I can look at pulling it in, but I don't want to have it extended time so ultimately we need a proper upstreamable fix
15:21:43 <cov> it's been nacked upstream
15:22:05 <pbrobinson> cov; sure, I get that, but presumably nacked in favour of another solution
15:22:34 <pbrobinson> cov: I've not seen the upstream discussion etc, there must have been a reason for the nack, was there suggestion for a different solution
15:22:40 <cov> probinson: the solution is to replace the hardware, which won't happen now
15:23:53 <cov> but eventually
15:23:57 <pbrobinson> cov: so for example what is the impact on ARMv8.1+
15:24:21 <pbrobinson> cov: is that HW due to go to mass production or is it a bringup batch and it'll be fixed in a later silicon rev?
15:25:05 <cov> it isn't mass production hardware
15:25:14 <pbrobinson> cov: happy to take this off line if there's NDA or other issues that come into play
15:26:13 <cov> the fix will be in the form of newer hardware
15:26:36 <cov> so this particular erratum workaround is only temporarily useful
15:27:47 <pbrobinson> cov: so what's the expected lifespan remaining on this HW? Is there possible impact in that time on ARMv8.1+ HW
15:28:18 <pbrobinson> we've shipped non upstream drivers for other devices in the past until the rev of silicon was replaced with newer to make it useful
15:28:41 <cov> the QDF2432 hardware was announced last october or november
15:29:05 <pbrobinson> so if we have a reasonable window I'm not opposed to adding this patch as a means of making it useful
15:29:27 <pbrobinson> cov: more worried about the end game for the hardware
15:30:02 <cov> the issue will be fixed in the next hardware
15:30:38 <cov> I don't know what will happen to the old hardware. presumably it will be recycled
15:30:49 <pbrobinson> cov: when is that expected roughlt, next month, next quarter, next decade. millenium?
15:31:02 <cov> I don't think there have been any announcements
15:31:43 <pbrobinson> cov: basically I want to know 1) can this impact other hardware in any way (looks like it's explicitly only enabled for that HW rev) 2) how long will I have pain of OOT patch
15:32:39 <pbrobinson> 3) actual guarantees that if we ship it that people will actually use/test Fedora for us (otherwise there is no point)
15:34:10 <jonmasters> sorry I am late - appointment went long
15:34:12 <jonmasters> catching up
15:34:23 <pwhalen> good morning jonmasters
15:35:43 <pbrobinson> cov: so maybe even answer Q 1 and 3
15:36:08 <jonmasters> pbrobinson: that QDF errata patch is trivial and happy to help maintain it (or get someone inside RH to do so) - you and I can take offline also
15:36:33 <pbrobinson> jonmasters: OK, still want answers to 1 and 3 though
15:37:01 <pbrobinson> jonmasters: also ThunderX Q above: who's committing to test the support and report to the list on status etc
15:37:07 <cov> 1) it won't impact other hardware. we can double-check this by dumping info->reg_id_aa64mmfr2 on other hardware 2) what if we arbitrarily plan to drop it by f26? 3) these being pre-production there aren't a lot of systems and users, but I'll be testing at least
15:37:41 * jonmasters answered pbrobinson 's Qs privately - can take the NDA stuff elsewhere
15:38:07 <jonmasters> cov: dropping by F26 sounds like a great plan
15:38:32 * jonmasters can test. I'll also test the ThunderX stuff. Haven't had chance yet, as I needed to GTFO over the weekend
15:38:37 <pbrobinson> cov: perfect, happy to have it for that window, will try getting it pulled in over the next few days
15:38:47 <pbrobinson> cov: will ping on channel when it's there
15:38:55 <cov> pbrobinson: much appreciated
15:39:10 <pbrobinson> cov: no problems
15:39:31 <pwhalen> anything else for the kernel? not sure if you had anything jonmasters
15:39:44 <pbrobinson> jonmasters: would like some others testing ThunderX as you can be a blocker at times, would be nice to see Cavium involved ;-)
15:39:50 <jonmasters> well I still need to help pbrobinson with some testing
15:39:58 <cov> robert richter tried to show up to one of these meetings a while ago
15:40:08 <jonmasters> pbrobinson: I reminded Cavium last week that a certain other partner has someone who bothers to turn up regularly
15:40:24 <jonmasters> pbrobinson: I will begin public shaming soon
15:40:39 <cov> but there was some weird scheduling, I think some other Fedora group was using this channel at what appeared to be the ARM timeslot
15:40:46 <pbrobinson> jonmasters: so the F-25 nightly compose as of today has all the ThunderX all there for installer etc
15:40:50 <jonmasters> ok
15:41:06 <jonmasters> I'll make sure it's tested this week, and also request in our internal meeting today that somoene else look too :D
15:41:22 <pbrobinson> jonmasters: thanks!
15:41:29 <pbrobinson> pwhalen: lets move on from kernel :)
15:41:46 <cov> how about replacing http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/tree/arm64-avoid-needing-console-to-enable-serial-console.patch with SPCR patches?
15:41:47 <jonmasters> oh one more
15:42:07 <pbrobinson> jonmasters: hurry up!
15:42:08 <jonmasters> cov: that makes perfect sense
15:42:18 <cov> http://patchwork.kernel.org/patch/9276727/
15:42:18 <cov> http://patchwork.kernel.org/patch/9275443/
15:42:18 <cov> http://patchwork.kernel.org/patch/9275457/
15:42:19 <cov> http://patchwork.kernel.org/patch/9280971/
15:42:21 <pbrobinson> cov: I have that on my todo list
15:42:35 <pbrobinson> cov: just need a few more round-tuits
15:42:58 <jonmasters> on kernel...this hasn't officially bitten Fedora yet BUT we've seen various random XFS corruption on kernels eslewhere and I want to ask folks to keep a look out
15:42:59 <cov> okay, I mind be able to find a couple
15:43:05 <pbrobinson> cov++ thanks for those links, saves me time digging them out :)
15:43:05 <zodbot> pbrobinson: Karma for cov changed to 1 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:43:06 * pwhalen takes some blame for Peters round-tuit shortage
15:43:28 <cov> pbrobinson: in case it's useful, here's my big long list of stuff in flight
15:43:31 <cov> https://wiki.codeaurora.org/xwiki/bin/Linux+Kernel/WebHome
15:43:31 <pbrobinson> jonmasters: does it happen on x-gene1 on 7.2?
15:43:39 <cov> also stuff merged in case it needs backporting
15:43:50 <pbrobinson> cov: will look later post meeting, might ping you on #fedora-arm
15:43:51 <jonmasters> pbrobinson: not on 7.2
15:44:13 <pwhalen> yikes, quite long that list
15:44:13 <jonmasters> pbrobinson: but I'm a bit worried that there's a genuine XFS bug upstream that's just being masked in some contexts, so keep a look out
15:44:24 <jonmasters> seems to be toolchain related - we're digging
15:44:34 <jonmasters> so just an FYI and we can move on
15:44:37 <cov> PCI IORT is another patchset that's not yet merged upstream
15:44:39 <pbrobinson> OK
15:44:44 <pwhalen> #topic 3) ==== Bootloader Status ====
15:45:02 <pbrobinson> cov: OK, I've seen that, not sure the impact or what it brings to the table
15:45:15 <pbrobinson> so on bootloaders
15:45:28 <pbrobinson> 2016.09 rc2 building on Fedora 26
15:45:49 <pwhalen> #info U-Boot 2016.09 rc2 building on Fedora 26
15:45:51 <pbrobinson> #info plan to push 2016.09 rc2 to F-25 once built on F-26
15:46:14 <pwhalen> and tested of course
15:46:16 <cov> pbrobinson: PCI Message Signaled Interrupts (MSIs) are needed to make some PCI card drivers work and the IORT describes some of the necessary setup in ACPI
15:46:51 <pbrobinson> cov: OK, any particular range of cards need it or don't work without it?
15:46:55 <jonmasters> cov: also we need the SMMUv3 part of IORT for device assignment so it's definitely being tracked
15:46:59 <pbrobinson> or random collection?
15:47:08 <jonmasters> pbrobinson: anything PCIe that's very modern and doesn't do legacy interrupts
15:47:41 <pbrobinson> so SRV-IO stuff? Mellonox?
15:47:44 <jonmasters> on that issue, RH is beating folks up on upstreaming it
15:47:54 <jonmasters> pbrobinson: needed for SR-IOV BUT also for just interrupts on some cards
15:48:04 <jonmasters> pbrobinson: we're harassing to get the basics in the next kernel cycle
15:48:18 <jonmasters> pbrobinson: then the SR-IOV type stuff via SMMUv3 which is also plumbed in via IORt
15:48:19 <jonmasters> IORT
15:48:31 <jonmasters> (IO Redirection Table) - includes things like MSIs but much more
15:48:42 <pbrobinson> OK, not sure I really want another big set of patches
15:48:50 <pbrobinson> I'd much sooner them get upstream
15:49:02 <pbrobinson> but can we take this to any other business or the other channel
15:49:10 <pbrobinson> we have 10 mins to finish up
15:49:13 <jonmasters> once I get done doing post-7.3 planning internally I'll help pwhalen and others go through and file some trackers in Fedora for these pieces if that helps
15:49:20 <jonmasters> ok, let's do bootloaders
15:49:34 <pbrobinson> so u-boot will need some testing, it looks OK
15:50:23 <pbrobinson> we had to move images back to ext3 to fix an issue with changes in ext4 defaults regarding some features (64bit - inodes I think) and some other meta data option I don't remember
15:50:31 <pbrobinson> so something to be aware of
15:51:05 <pbrobinson> need to look at a better fix (like anaconda filesystem default option settings or similar) but ext3 was the quick workaround
15:51:35 <pwhalen> something to fix for Beta
15:51:48 <pwhalen> anything else for bootloader?
15:51:51 <pwhalen> s
15:52:07 <pwhalen> #topic 4) ==== F25 Alpha ====
15:52:21 <pbrobinson> so we're very close to alpha
15:52:26 <pbrobinson> there's a few issues outstanding
15:52:39 <pbrobinson> I'm looking at an  issue with graphics/X on some devices
15:52:44 <pwhalen> #info Alpha was delayed a week. go, no-go decision will be Thursday.
15:52:49 <pbrobinson> beaglebone had an issue with MMC
15:53:04 <pbrobinson> and probably lots that pwhalen will remind me of
15:53:22 <jlinton> pbrobinson: The graphics problem is the failure of xorg -config ?
15:53:36 <jlinton> or something else?
15:54:08 <pbrobinson> jlinton: not 100% sure yet, I'm thinking maybe around some of the changes in the fbdev unbundling stuff and we've lost a config option they want
15:54:43 <pbrobinson> also looking at an option of a driver (tiny something other another I don't remember offhand) from staging
15:54:46 <jlinton> Just trying to clarify if its a configuration problem, or the graphics is broken
15:55:05 <jlinton> because i've had to hand write all my xorg.conf files on arm64 so far
15:55:09 <pbrobinson> jlinton: well we don't generally use configs, expect autogen to work, so something has changed
15:55:26 <pbrobinson> jlinton: this is mostly ARMv7
15:55:38 <jlinton> the pci card ids are missing for PCI cards, and the drm stanza isn't in place correctly either
15:55:59 <pbrobinson> jlinton: got details/patch somewhere?
15:56:08 <jlinton> no, not yet..
15:56:52 <jlinton> no, i'm only on arm64
15:57:16 <pwhalen> issues with alpha on aarch64 include a vnc segfault (bz#1368569)
15:57:26 <pbrobinson> jlinton: OK, so it's likely a different problem, ping me details or cc: me when you do have it for arm64
15:57:40 <pbrobinson> pwhalen: that looks like a libjpeg crash btw
15:57:41 <pwhalen> and mustang crash when booting the installer, no bz yet, will have one shortly
15:58:03 <pbrobinson> which might be awaiting the infamous firmware from APM \o/
15:58:49 <pwhalen> hopefully
15:58:52 <pbrobinson> aarch64 is great.... it's now exactly like x86_64 just like jonmasters wanted.... it has all the really really shit firmware!
15:59:02 <jonmasters> :P
15:59:21 <jonmasters> there's a new firmware coming soon from APM that's AMI based
15:59:24 <pbrobinson> jonmasters: there's not enough whiskey and not enough livers for me to cope!
15:59:30 <pwhalen> #info Help testing Alpha would be greatly appreciated, aarch64 and armv7.
15:59:52 <jonmasters> they claim in testing it boots the latest Fedora alpha bits
15:59:56 <pbrobinson> jonmasters: so it'll fix the one bug I need fixed, and introduce a billion+ more! BOOOOO!!!!!
16:00:02 <jonmasters> which is great, but it's needs to be released
16:00:07 <jonmasters> :)
16:00:17 <jonmasters> pbrobinson: just for you, there's a non-AMI one too
16:00:33 <pbrobinson> jonmasters: I _REALLY_ just want the current generation firmware with the GICv2 fix I need
16:00:34 <pwhalen> ok, we're at the hour
16:00:36 <jonmasters> pbrobinson: that also apparently fixes said problems in their tests, but it's still in QE cycle
16:00:51 <jonmasters> pbrobinson: I'll slip you a copy of the test one
16:00:54 <pwhalen> #topic 5) == Open Floor ==
16:01:17 * jonmasters will poke vendors to send people to this meeting
16:01:58 <pwhalen> ok, lets take this to #fedora-arm for anythign else, i think we have another meeting now (patiently waiting, thanks!)
16:02:07 <jonmasters> ok
16:02:10 <pbrobinson> yep, pwhalen++
16:02:10 <zodbot> pbrobinson: Karma for pwhalen changed to 2 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:02:16 <jonmasters> pwhalen: ++
16:02:21 <jonmasters> pwhalen++
16:02:21 <zodbot> jonmasters: Karma for pwhalen changed to 3 (for the f24 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:02:22 <pwhalen> #endmeeting