15:02:09 #startmeeting Fedora ARM and AArch64 Status Meeting 15:02:09 Meeting started Tue Mar 22 15:02:09 2016 UTC. The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:09 The meeting name has been set to 'fedora_arm_and_aarch64_status_meeting' 15:02:09 #chair pwhalen bconoboy pbrobinson dgilmore hrw jsmith dmarlin 15:02:09 Current chairs: bconoboy dgilmore dmarlin hrw jsmith pbrobinson pwhalen 15:02:29 dst... 15:02:32 good morning folks, sorry a bit of confusion over the start time.. 15:02:56 hrw, right.. i think we might have a conflict if we dont keep our original slot 15:03:06 whos here today? 15:03:16 * pbrobinson waves 15:03:25 hrw, hopefully its ok with you? 15:03:29 yes 15:03:34 cool, thanks 15:03:51 ok, well lets get started.. 15:04:05 #topic 1) ==== Package Status & Issues ==== 15:04:22 pbrobinson, hrw how does aarch64 look? 15:04:32 nothing major here, the big ones I think are firefox/xulrunner/thunderbird. Probably all the same issue 15:04:58 I pushed out f24 updates-testing and other updates yesterday and it all seems OK 15:05:17 pbrobinson: yes, all the same 15:05:43 #info f24 updates-testing and other updates yesterday 15:05:53 hrw: do we have bz for tracking this? I think power was seeing failures too, not looked to see if there were overlaps 15:06:03 I'll find some time this week to go through any failures and see what else might need attention 15:06:03 will check 15:06:30 hrw: could you also look at the ada/gnat email on the list to see if that makes sense for me? 15:06:39 ok 15:06:59 #info No major issues to report. 15:07:31 anything else? 15:07:41 not that I can think of 15:07:48 cool, thanks 15:07:54 #topic 2) ==== Kernel Status ==== 15:08:10 so, i think the major one here is aarch64 15:08:25 #info f24 candidate kernel boot fails 15:08:26 #link https://bugzilla.redhat.com/show_bug.cgi?id=1309147 15:08:48 I don't think that's a kernel issue 15:08:52 the same unpack issue we've been discussing.. 15:09:40 but ultimately we need someone like msalter or mlangsdorf to give an opinion 15:10:09 due to it's intermittent style I don't really see it as a blocker TBH 15:10:17 pbrobinson, ok, i will bring it to their attention in our meeting 15:10:42 no? only way i get it to boot is using the grubaa64.efi.. that works on mustang, not seattle for me 15:10:53 or regen 15:11:05 pwhalen: seattle is known broken with 4.5 is it not? 15:11:24 pbrobinson, 4.5 final is better than that rc7 15:11:32 still awaiting the promised fix for that, from memory from msalter 15:11:49 pbrobinson, seattle - https://bugzilla.redhat.com/attachment.cgi?id=1138813 15:12:49 pwhalen: great, it can't boot it's own CPUs, does it boot with smp off? 15:14:18 i havent tried, but it panics at the unpacking initrd as well 15:15:28 what ever, can't be fixed here, just track it, there's more than one issue there. Looks like issues with DT too 15:15:46 i find it odd that mustang unpacks fine when i use the grubaa64.efi to boot 15:15:48 ok. 15:16:18 any other kernel related news to discuss? 15:16:18 Boot0000 Fedora rawhide PciRoot(0x7)/Pci(0x0,0x0)/Sata(1,0,0)/HD(21,GPT,ea22d0e2-179c-48c3-8e72-a952370f4b75,0x7480800,0x4000)/File(\efi\fedora\grubaa64.efi).. 15:16:27 and it fails too 15:16:29 pwhalen: well there's known issues with shim too 15:17:01 pwhalen: so it can also be not related to shim 15:17:08 * pbrobinson actually wants u-boot+DTB back, this is just shit 15:17:53 shim boots to grub, then onwards, it's not the problem. Itself might have an issue, it's not invovled with unpacking issues 15:17:54 sure.. im reporting it as i see it.. with an f24 install, shim.efi is the default, fails.. change it to grubaa64.efi and it boots 15:18:25 pwhalen: we have a shim BZ right? please info it 15:18:27 hi all 15:18:33 and any other related issues in the notes 15:18:37 #info https://bugzilla.redhat.com/show_bug.cgi?id=1319083 15:18:45 by issues I mean rhbz 15:19:27 morning dgilmore 15:21:28 ok, anything to add here, or shall we move on? 15:21:40 there's an approved Free Exception to pull in a new u-boot which should fix issues on some AllWinner devices 15:21:50 so please test that and provide karma on the bodhi update 15:21:52 next 15:21:58 #topic 3) ==== U-Boot Status ==== 15:22:22 https://bodhi.fedoraproject.org/updates/FEDORA-2016-bdd2592ee5 15:22:28 even I started using u-boot 15:22:39 hrw++ :-D 15:22:39 pbrobinson: Karma for hrw changed to 3 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:22:47 ;D 15:23:04 surely zodbot needs to get with the times and do f24 release cycle.... 15:23:30 this uboot fixed some data abort issues on some allwinner for me, sadly it doesn boot on the Bananapi.. loads the spl, but not uboot 15:23:56 pbrobinson: can u-boot prompt somehow show release too? 15:24:03 U-Boot 2016.03 (Mar 14 2016 - 22:51:09 +0000) 15:24:25 hrw: I'll have a look, not sure 15:24:29 pbrobinson: thanks 15:24:36 easier to track which image it is 15:25:01 ill try the banana pi pro with it today 15:25:02 hrw: sure, not sure if it's something I'd have to manually update for each build or whether I can pass it as a variable 15:26:28 thx 15:26:31 #info Latest uboot-tools-2016.03-3.fc24 . Please test and provide karma 15:26:38 #link https://bodhi.fedoraproject.org/updates/FEDORA-2016-bdd2592ee5 15:26:57 anythign else for uboot? 15:27:20 dgilmore++ for u-boot distro stuff 15:27:20 hrw: Karma for ausil changed to 23 (for the f23 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:27:50 I have own partitioning scheme on card and it just works 15:27:50 #topic 4) ==== F24 Alpha Status ==== 15:28:02 #link https://fedoraproject.org/wiki/Test_Results:Fedora_24_Alpha_1.6_Summary 15:28:23 arm testing looks pretty good. we do have an initial-setup bug 15:28:29 I believe upstream has a 1.7 being spun, dgilmore can confirm, I'll be spinning an Alpha off that once it completes for aarch64 (and power) 15:28:33 #info (Initial-setup) Only uses upper left part of the display 15:28:34 #link https://bugzilla.redhat.com/show_bug.cgi?id=1160891 15:29:06 its not just arm for initial-setup, and you can still complete everything, just a little difficult 15:29:25 initially anyways, once you select something, its better.. 15:30:57 so being a general bug is it a blocker? 15:31:25 nope, was rejected 15:31:32 why? 15:32:04 its still usable 15:32:35 blocker for final 15:32:45 I am working on Alpha-1.7 15:33:02 from the BZ - AcceptedFreezeException (Alpha) - this definitely impairs use of initial-setup, but it is possible to do what you need to; we agreed it makes sense to make it a Final blocker, Alpha users can be expected to cope. If not fixed it will be documented in Common Bugs. 15:33:13 I hit it on x86_64 on the weekend 15:33:23 and initial-setup was not at all usable 15:34:01 pwhalen: as I commented I couldnt do anything, thankfull I only needed to say finish as I was not adding a user 15:34:45 dgilmore, if you select something, the window gets larger.. you sorta have to scroll down in the area... 15:34:50 OK, anything else for aarch64 15:34:53 not ideal 15:35:38 aarch64, those two bugs i linked early. think thats about it.. anyone else hit anything? 15:37:16 I have to talk with msalter about boot_vga stuff again. To get gfx mode in anaconda 15:37:27 pwhalen: I could not see anything at all. but its offtopic 15:39:08 dgilmore, i was out with the flu during that meeting.. i agree its not ideal, but you can complete it. Ill write it up in common bugs, hopefully that helps 15:39:29 #topic 5) == Open Floor == 15:39:38 anything else for today folks? 15:42:02 thanks for coming folks! happy testing! 15:42:07 #endmeeting