15:02:46 <pwhalen> #startmeeting Fedora ARM and AArch64 Status Meeting
15:02:46 <zodbot> Meeting started Tue May 14 15:02:46 2019 UTC.
15:02:46 <zodbot> This meeting is logged and archived in a public location.
15:02:46 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:46 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:46 <zodbot> The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting'
15:02:47 <pwhalen> #chair pwhalen pbrobinson jlinton
15:02:47 <zodbot> Current chairs: jlinton pbrobinson pwhalen
15:02:59 <pwhalen> good morning folks, sorry I'm late
15:03:13 * pwhalen thinks we may not have a quorum today
15:04:05 * jlinton waves
15:05:16 <pwhalen> howdy jlinton
15:05:27 <pwhalen> did you have anything you wanted to talk about this week?
15:05:40 <jlinton> Nothing new, had a few good discussions at RH summit
15:06:15 <pwhalen> did you see - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90273
15:06:27 <pwhalen> wondering if that helps us with arm at all
15:06:49 <jlinton> Yes, it might help... Not sure though since its a link problem with armv7
15:07:22 <jlinton> and it was failing with gcc8 too
15:07:40 <pwhalen> ah, right. boo, I had some hope
15:08:30 <jlinton> I have a ld.gold patch, thats partially done (the code is there, but it has bugs due to the way the request region/write/done sequences are called in existing code)
15:09:14 <jlinton> so I have to track down the users that are problematic and make them more specific about the way they are using the file api
15:09:32 <pwhalen> sounds like good progress
15:09:54 <jlinton> It seems everyone just assumed it was a mmap..
15:10:21 <pwhalen> The only thing I really had for this week is requesting 5.1 testing, f30 should rebase next week
15:10:50 <jlinton> I think the largest problem i've seen is that something has gone wrong with nouveau in F30
15:11:10 <jlinton> not sure if its mesa or a gcc9'ism showing up
15:11:45 <jlinton> but i'm getting OOPs that werent happening with 5.0 in F29 on two different machines
15:12:03 <pwhalen> :( which hardware?
15:12:27 <jlinton> TX2 and the N1, both with a GT710
15:14:30 <pwhalen> by chance have you filed a bug?
15:14:38 <jlinton> No...
15:14:53 <jlinton> I want to try and track it down a bit first
15:14:54 <pwhalen> I dont suspect we have many using those
15:15:15 <pwhalen> ok, sounds good. then we can discuss further next week
15:15:15 <jlinton> It seems to be the default card in a lot of arm machines because zotac makes a x1 version of it
15:16:08 <jlinton> So it plugs into machines that don't have a full x16 slot, like the mcbin
15:18:33 <pwhalen> right. something I wanted to ask you about - https://bugzilla.redhat.com/show_bug.cgi?id=1691430
15:18:40 <pwhalen> did you also hit that on a seattle?
15:18:56 <jlinton> Yes, I saw that, wierd..
15:19:08 <jlinton> (yes, i was on a seattle too)
15:19:09 <pwhalen> ok, just wanted to confirm it was a seattle.
15:19:12 <pwhalen> thanks.
15:19:31 <pwhalen> affects rhel8 as well
15:20:02 <pwhalen> ok, lets reconvene next week
15:20:25 <jlinton> I assumed it was guest related.
15:20:33 <jlinton> since it appeared when I upgraded the guest
15:21:02 <pwhalen> I havent seen it on updated guests on mustang or m400.. just the seattle
15:21:04 <jlinton> I should try it on a mcbin, but I have to convince mine to work again
15:21:17 <pwhalen> heh, that would great
15:22:07 <pwhalen> I've been doing various testing trying to track down breakage on the armv7 builder issue.
15:23:05 <jlinton> Did you try bisection the 4.18->4.19 change? (or has that been found not to be a key point?)
15:23:34 <pwhalen> 4.19/4.20 seem to be working ok on f29 GA userspace
15:24:59 <pwhalen> I'll keep poking at it this week and we can discuss some more at next weeks meeting
15:25:15 <jlinton> Sounds good
15:26:07 <pwhalen> #info Meeting adjourned, lack of quorum.
15:26:11 <pwhalen> #endmeeting