15:00:14 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:00:14 <zodbot> Meeting started Tue Oct 25 15:00:14 2016 UTC.  The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:14 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:00:15 <pwhalen> #chair pwhalen pbrobinson dgilmore hrw dmarlin yselkowitz jonmasters ahs3 msalter
15:00:15 <zodbot> Current chairs: ahs3 dgilmore dmarlin hrw jonmasters msalter pbrobinson pwhalen yselkowitz
15:00:22 <pwhalen> morning folks, whos here today?
15:01:21 <ahs3> o/
15:01:56 * pwhalen high fives ahs3 :)
15:02:34 <ahs3> mornin', dude :)
15:03:11 <pwhalen> we'll give it a couple of minutes to see if others join
15:04:14 * pbrobinson o/
15:04:29 <pwhalen> \o/
15:04:34 <pwhalen> ok, lets get started
15:04:40 <pwhalen> #topic 1) ==== Userspace Status  ====
15:05:31 <pwhalen> any issues here? testing, build failures?
15:05:34 <pbrobinson> nothing here to report of note
15:05:49 <pwhalen> #info No current issues.
15:05:52 <cov_> hi
15:06:02 <pwhalen> morning cov_ thanks for joining
15:06:17 <jlinton> I opened a bunch of browser defects
15:06:25 <jlinton> because none of them work
15:06:40 <pbrobinson> jlinton: OK, can you link them to ARMTracker as a blocker bug so they're easy to track
15:06:53 <jlinton> yah sure
15:07:59 * jwb waves
15:08:00 <jlinton> Also, along the same lines, xorg configuration now works correctly, but setting the default runlevel to graphical doesn't
15:08:03 * pwhalen also opened some against otter-browser and midori
15:08:11 <pbrobinson> jlinton: did you see the mozjs31 upstream BZ stuff
15:08:33 <jlinton> pbrobinson: ?
15:08:47 <jlinton> thats probably a no, since i'm not sure what your talking about
15:09:10 <pbrobinson> jlinton: the gnome bug I think they've now landed all the bits to support mozjs31 so might be time to poke about moving to something higher
15:09:17 <jlinton> oh
15:09:38 <jlinton> Ok, sounds good
15:09:51 <jlinton> except they pretty much ignored my request to use mozjs38
15:10:25 <jlinton> and I need to push all the other projects to start taking my patches.
15:10:43 <pbrobinson> jlinton:  https://bugzilla.gnome.org/show_bug.cgi?id=742249
15:10:49 <jlinton> The older ones seem resistant for reasons I cannot imagine (although moving ones project from C->C++ probably isn't modivating for some of them)
15:11:10 <pbrobinson> jlinton: I think they said they would go to 31 and get that working and then move from there
15:11:46 <jlinton> Yah, which makes sense, but how long is that going to take? Maybe I should post the patches... 31-38 not a big move
15:12:57 <pbrobinson> jlinton: they're already at 31 so if you're interested now might be the time to revisit it if you have the cycles/interest :)
15:14:43 <pwhalen> #topic 2) ==== Kernel Status ====
15:15:00 <pwhalen> #info Latest Rawhide - kernel-4.9.0-0.rc2.git0.2.fc26
15:15:01 <pwhalen> #link http://koji.fedoraproject.org/koji/buildinfo?buildID=812344
15:15:16 <jlinton> (still on "userspace") https://bugzilla.redhat.com/show_bug.cgi?id=1387764
15:15:32 <jlinton> which is BDB2053 Freeing read locks for locker 0x14: 2280/4395568132608
15:15:35 <pwhalen> sorry jlinton, thoguht we were done there
15:15:37 <jlinton> during the install
15:16:13 <jlinton> Everything seems to work, but the error message is listed in a number of older fed/rh defects indicating that the rpmdb isn't being
15:16:16 <jlinton> locked correctly
15:16:45 <jlinton> (more on topic) https://bugzilla.redhat.com/show_bug.cgi?id=1387793
15:17:03 <jlinton> which is "alloc_contig_range: [c254, c255) PFNs busy"
15:17:22 <jlinton> showing up a few dozen a second, when X/radeon is running
15:18:15 <pbrobinson> jlinton: is that on the RPi or which device?
15:18:24 * rric o/
15:18:27 <jlinton> Juno (because it has pcie slots)
15:18:33 <pbrobinson> jlinton: OK
15:19:07 <pbrobinson> jlinton: is alloc_contig_range: a CMA issue do you you know
15:19:08 <jlinton> I suspect that I can get it to happen on anything else that has a functional PCIe slot (not seattle at the moment because there is still something wrong with the PIO)
15:19:25 <jlinton> yah, Laura posted a note about it.
15:19:27 <rric> pbrobinson, have you had the chance to look into the mm fix?
15:19:59 <pbrobinson> rric: the one that you sent a second one to yesterday? No, it's high on my list for probably tomorrow morning
15:20:18 <rric> pbrobinson, ok, many thanks
15:22:22 <pbrobinson> jlinton: can you attach inst.txt to that BZ?
15:23:02 <jlinton> pbrobinson: sure, I looked at the logs but nothing jumped out, I can probably just attach them all.
15:24:02 <pbrobinson> jlinton: yea, I've not seen that but I've also not had a bunch of time of late to do installs, I need to fix my seattle and install the new mustang
15:24:09 <jlinton> The suggested thing to check was ausearch, to determine who had the lock, but it didn't work
15:24:26 <rric> jlinton, pbrobinson, this seems to be the same mm problem I have
15:24:48 <rric> it's the same, not all pages are in the same zone
15:25:07 <pbrobinson> rric: ah, so once I apply that patch jlinton's problem will be solved?
15:25:08 <rric> I suggest to test my fix
15:25:20 <rric> probably
15:25:54 <rric> some pages are not initialized (that in the nomap range)
15:26:09 <pbrobinson> OK
15:26:51 <jlinton> rric: Interresting, didn't expect that, I will try it with your patch (when i'm setup to reproduce it again, which might be a couple days)
15:26:51 <rric> jlinton, I suspect a nomap range in the c254-c250 phys mem area
15:27:29 <jlinton> rric: I can check that as soon as I get a firmware back on the machine that can boot :)
15:27:52 <pbrobinson> jlinton: minor details ;-)
15:28:03 <rric> there are some kernel parameters to be verbose on the ranges:
15:28:22 <rric> memblock=debug efi=debug loglevel=8 mminit_loglevel=4
15:28:45 <jlinton> rric: Can you add that to the defect?
15:28:56 <rric> sure
15:29:17 <jlinton> although memblock=debug is a neverending message dump
15:29:55 <rric> it ends at some time :)
15:34:49 <pwhalen> #info Latest F25 - kernel-4.8.4-301.fc25
15:34:49 <pwhalen> #link http://koji.fedoraproject.org/koji/buildinfo?buildID=812331
15:35:26 <pwhalen> #info Includes patches that may help with display detection on the Raspberry Pi 2/3.
15:35:33 <pwhalen> #info Please test and report any issues to the list or #fedora-arm.
15:36:06 <pwhalen> anything other kernel issues, news?
15:36:43 <pbrobinson> the 4.8.4-301.fc25 kernel should have a bunch of Raspberry Pi display stabilisation enhancements
15:39:47 <pwhalen> #topic 3) ==== Bootloader Status ====
15:39:47 <pwhalen> #info Latest - uboot-tools-2016.11-0.2.rc2
15:39:47 <pwhalen> #link http://koji.fedoraproject.org/koji/buildinfo?buildID=810695
15:40:14 <pwhalen> #info Latest in F25 - uboot-tools-2016.09.01-2.fc25
15:40:22 <pwhalen> #link http://koji.fedoraproject.org/koji/buildinfo?buildID=811236
15:40:50 <pwhalen> #info Includes upstream ext4 patches to fix 64 bit feature issues with u-boot and /boot
15:41:27 <pwhalen> #info Disk images reverted back to ext4. Please test and report any issues to the list or #fedora-arm.
15:41:43 <pwhalen> anything else here?
15:42:48 <pwhalen> #topic 4) ==== F25 Final ====
15:42:48 <pwhalen> #info Testing so far:
15:42:48 <pwhalen> #info ARMhfp - https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20161017.n.0_Summary
15:42:48 <pwhalen> #info AArch64 - https://fedoraproject.org/wiki/Architectures/AArch64/QA/Fedora-25-20161021.n.0
15:43:24 <pwhalen> looking ok so far. armhfp i-s graphical issues are now resolved on the nightly images.
15:43:29 <pbrobinson> cool
15:43:37 <jlinton> So, stupid question, is there an automated way to update some of those test results?
15:43:42 <pwhalen> is anyone aware of any issues? concerns for final?
15:43:53 <pbrobinson> I think a bunch of the RPi display issues should settle down so we don't get inundated there
15:44:11 <pbrobinson> I'm not aware of anything  that is blocking but I'm very interested in people's nice to have
15:44:40 <pwhalen> jlinton, its been done for Primary results table, the bot results are done by openqa. something we need to look at
15:47:46 <pwhalen> #info Fedora 25 Schedule:
15:47:47 <pwhalen> #info 2016-11-01 - Final Freeze
15:47:47 <pwhalen> #info 2016-11-15 - Final Release
15:47:58 <jlinton> pwhalen: Some of the test cases say alpha, some say beta, should that be updated?
15:48:30 <jlinton> some say final too, I'm assuming they all should say beta?
15:48:45 <pwhalen> jlinton, yes, for final all alpha and beta testing should be completed as well
15:49:44 <jlinton> I was just about to update the VNC install case (because I run that one regularly) but it says "alpha" should I update it to beta, since that is what im using?
15:50:08 <jlinton> or does that indicate it should have been tested during the alpha?
15:50:36 <pwhalen> jlinton, for alpha, we do all the alpha tests.. then beta we do alpha and beta tests. final we do 'em all
15:50:57 <jlinton> ok, clear...
15:52:18 <pwhalen> #topic 5) == Open Floor ==
15:52:22 <jlinton> Of course, the graphical install doesn't work on my machine (HDLCD or HD5450) Is that enough to fail the case (cause it could be my machine)
15:53:21 <pwhalen> sure, if it fails, marks as such with a note about the hw used so we know
15:53:57 <pwhalen> sounds like you might be the only one testing graphical installs as well
15:56:01 <pwhalen> last call for open floor
15:57:02 <pwhalen> #endmeeting