20:00:17 #startmeeting Fedora ARM weekly status meeting 20:00:17 Meeting started Wed Aug 28 20:00:17 2013 UTC. The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:17 #chair pwhalen jonmasters bconoboy ctyler pbrobinson dgilmore dmarlin masta handsome_pirate msalter ahs3 agreene jcapik 20:00:17 Current chairs: agreene ahs3 bconoboy ctyler dgilmore dmarlin handsome_pirate jcapik jonmasters masta msalter pbrobinson pwhalen 20:00:24 .fas pwhalen 20:00:24 pwhalen: pwhalen 'Paul Whalen' 20:00:32 afternoon all 20:00:35 * handsome_pirate waves from the Crow's Nest 20:00:45 * masta is here 20:00:47 howdy folks 20:01:37 .fas jcapik 20:01:38 jcapik: jcapik 'Jaromír Cápík' 20:02:04 * pbrobinson is here 20:03:54 pwhalen: let's do it 20:03:56 .fas jonmasters 20:03:56 jonmasters: jcm 'Jon Masters' 20:03:58 alright, shall we get started 20:04:10 #topic 1) Problem packages 20:04:27 so the glibc issue on tegra is resolved thanks to kylem 20:04:57 jonmasters: do you have a status update on the glibc stack protector issue? 20:05:04 I installed on an f19 trimslice, got some off output kyles been looking at 20:05:31 http://ur1.ca/f9nys 20:05:42 pbrobinson: you mean on getting the support updated? 20:05:52 pbrobinson: so Linaro/ARM are still working on it last I heard 20:06:07 jonmasters: yes, so can you organise to get an update on where we are on that 20:06:08 pbrobinson: they're not likely to change the global canary though 20:06:26 pbrobinson: sure, we'll circle back with Matthew 20:06:34 (toolchain lead) 20:06:49 and llvm is the other one on my list 20:06:55 for problem packages 20:06:58 pbrobinson: the v8 side gets more exciting, but that's not an issue here. Anyway, I'll get an update sent out about glibc 20:07:19 v8? 20:07:29 ah armv8 20:07:37 sorry was thinking of the other one 20:07:53 on AArch64 the stack frames are more excitingly optimized and will make that implementation harder for stack protector 20:08:07 sure yea, v8 (the google one) is something we're following up with ARM on for AArch64 20:08:42 so for the glibc and llvm I'm concentrating on v7 20:08:46 but that's all a tangent, anything other than llvm broken on 32-bit? 20:09:01 IE things that might well cause us issues coming into alpha 20:09:36 pbrobinson: I'll upload what I've got on llvm to my fedorapeople space 20:09:56 tested the new version of initial-setup, initial-setup-text is displayed on console for trimslice, vexpress, omap 20:10:00 pbrobinson: I just have been pulled in too many directions at once to get as much work done as I'd like 20:10:13 pwhalen: great 20:10:24 handsome_pirate: are you talking about llvmpipe or the triplet issue 20:10:37 pbrobinson: Triplet issue 20:10:59 kylem: do you have an update on the llvmpipe issue? 20:11:19 pwhalen: great news about initial-setup... I'll test that on some remixes too 20:11:37 masta, please do 20:12:49 initial-setup-graphical also does not run, complains about a missing hostname. there are several bugs revolving around this as well 20:13:28 root cause seems to be missing '/etc/hostname' 20:13:30 pwhalen: I'd reccomend you go ahead and file a bug just for that, since it seems like spstarr doesn't have a clue what he's doing 20:13:35 and there are open BZs as pwhalen has mentioned 20:13:46 handsome_pirate, agreed on opening a bug 20:14:10 pwhalen: is there BZ for the hostname issues? 20:14:24 pbrobinson: Sort of, but it got hijacked 20:14:25 there were several, all pointing to this root cause, but non explicitly for ours 20:14:35 https://bugzilla.redhat.com/show_bug.cgi?id=1000715 20:14:42 thats the last open one iiuc 20:15:06 pwhalen: It got turned into an internationalization bug 20:15:21 right 20:15:23 pwhalen: It looks like two issues are causing the same error output 20:15:29 pbrobinson, nah, same as last time, works with mcjit + llvm 3.2, fails with 3.3 20:15:41 kylem: thx 20:15:54 pbrobinson, i'll look at it when i finish fixing trimslice. and beaglebone black. and all the other things in the world. 8) 20:16:11 pwhalen: I note that there has been at least one instance of x86 hitting the bug 20:16:11 kylem: :-P 20:16:48 pwhalen: But, the dude is clueless when it comes to properly testing and not screwing up repeatability 20:16:50 I doubt it's arm specific, it's probably just not triggered in the std x86 use case 20:17:18 I tried on x86 in a vm, but initial-setup ran okay 20:17:24 pbrobinson: Aye, because generally initial setup isn't run on x86 any more, it's been replaced by bits in Anaconda 20:17:43 pwhalen: It also seems to be a bit of a hysenbug 20:18:00 during install just dont create a user, initial-setup will run 20:18:24 pwhalen: But, if /etc/hostname is missing, anaconda will bork 20:18:29 With the same error message 20:18:30 I will file a new bug on this 20:18:42 anything else for problem packages? 20:18:59 alright.. 20:19:02 #topic 2) Kernel Status Update 20:19:40 kylem: I'll leave that to you 20:20:03 * handsome_pirate notes that lpae seems to be broken in 3.11-rcx 20:20:11 heh. there's really no updates since last time. trimslice has busted pci which results in r8169 not working (so no ethernet) and i'm not having any luck fixing omap. 20:20:24 wcohen and I have both hit that 20:21:12 in our discussion earlier we agreed that upstream omap isn't exactly in good shape 20:21:24 so the suggestion was of any of those targets, focus on BBB 20:21:35 then OMAP4/3 are nice to haves 20:21:39 so this segues nicely into talking about supported boards. i think we're going to focus on BBB for F20 and if omap gets fixed, good on it. otherwise people can stay on f19 or remix the f19 kernel + f20. 20:21:50 +1 20:21:56 (or do a remix) 20:22:01 kylem: pwhalen and I had a discussion about that earlier 20:22:04 I'm got some bandwidth (for once) so I can poke at omap over the next couple of days 20:22:06 re supported stuff 20:22:24 pwhalen: You want to sumarize? 20:22:35 jonmasters: I believe if we get BBB we'll get most of OMAP anyway but agreed the BB is the core focus 20:22:49 Well 20:23:03 * jsmith bought a BBB in anticipation :-) 20:23:13 Anyway, with x86, we don't list 'supported h/w' 20:23:35 sorry back 20:23:35 We do have a *short* listing of *unsupported* h/w 20:23:42 handsome_pirate pwhalen: I think that conversation would be good summarised to the list 20:23:42 handsome_pirate: We do -- on the DVD sleeves 20:23:48 pbrobinson: +1 20:23:58 pbrobinson: (on the BBB/OMAP tradeoffs) 20:24:00 pbrobinson: It is relevant 20:24:11 we discussed earlier that we should perhaps not have a supported list, but an enabled list of hw, with some being tested 20:24:19 pwhalen: +1 20:24:24 handsome_pirate: I don't disagree but I would like it also discussed on the list 20:24:27 BBB would be realyl ncie to have 20:24:33 nice to have even 20:24:35 with alpha, and rc's kernels, its not easy to have everything working at the alpha stage 20:24:50 pwhalen: that sounds good... I like "enabled HW" as a term :-P 20:25:14 I agree.. 20:25:16 It's a better wording, and also eases QA tension 20:25:22 part of the problem is we can't leverage other distros, since most of them don't build -rc kernels for general consumption like we do. 20:25:45 yea "enabled" is nice sounding 20:25:53 kylem: Aye, they leverage us :) 20:25:59 kylem: a lot of the other distros don't even use upstream kernels but use vendor kernel branches/forks 20:26:31 sure. so we have an uphill battle where things may or may not work upstream, and very little interest in bashing things into working order. 20:26:44 masta: It also fixes the problem of "Oh, crap, it's Freeze and our supported h/w doesn't work" 20:26:59 kylem: now you know the shit I've been dealing with over the last couple of years ;-) 20:27:01 masta: Doesn't mean it entirely goes away, but it effectively does 20:27:17 so we pave the way forward 20:27:24 masta: Indeed 20:27:29 pbrobinson, yeah, i don't know how you still have a full head of hair 20:27:35 dgilmore? 20:27:40 it's just all grey :-D 20:27:53 so what are we going to enable? 20:28:04 right so from a kernel PoV tegra is good but has PCI issue 20:28:11 drink more caffeine. It'll be like mine 20:28:13 masta: Whatever works is what works, that's the beauty of it 20:28:15 but kylem is dealing 20:28:25 masta: Without blocking the distro 20:28:26 I'll have a look at TI over the next couple of day 20:28:36 masta: That's something we don't want to do 20:28:51 I believe Calxeda is looking good but we're awaiting a patchset for midway for lpae 20:28:59 i may just revert the removal of omap4-panda.c from 3.11 and we can try again for 3.12 20:29:02 anyone know the state of vexpress 20:29:07 pbrobinson: Is lpae busted on Calxeda, too? 20:29:13 vexpress is working with graphics in tc1 20:29:29 handsome_pirate: no but it needs some patches to make it bette 20:29:30 kylem: wow! the nuke from orbit way 20:29:32 pbrobinson, vexpress is fine without dtb use, and works with serial with dtb use, so no changes since f19 20:29:40 pbrobinson: On exynos, lpae is busted 20:29:54 has anyone tested any of the virtio-mmio stuff? 20:30:13 pbrobinson: It's on my todo list 20:30:31 ctyler: have you tried the latest lpae kernel on yoru arndale board yet? 20:30:54 sadly my arndale board has not arrive, had hoped it would be here by branching, but not yet.... 20:30:56 does anyone disagree with the suggestion of enabled hw versus supported hw list? 20:31:36 pwhalen: do not disagree, enabled > * 20:31:44 you should make it clear, what enabled means, then 20:31:51 enabled == tested? 20:32:03 mrunge: Aye, that's the general idea 20:32:03 or enabled == should run in theory 20:32:12 enabled == tested 20:32:23 enabled meaning soc's that should work, and a list of hw thats been tested 20:32:28 so: why don't you say supported 20:32:40 mrunge: It's a QA thing 20:32:48 I agree 20:32:54 mrunge: In QA, we have a specific definition of Supported 20:33:02 still, someone should make that clear ;-) 20:33:12 mrunge: It is, if you look at the QA docs 20:33:41 will do so, thanks for the pointer 20:34:04 mrunge: so it would be OMAP3 is enabled and testing on Beagle xM, so it might work on others but it depends 20:34:13 masta: wcohen and I are both hitting the lpae on exynos issue, so, yes, someone testing with another board would help 20:34:18 ctyler: ^^ 20:35:04 pbrobinson, right.. 20:35:47 so I think we're OK with kernel... what's next? 20:36:10 #topic 3a) Aarch64 - Status Update 20:37:17 hi 20:37:19 not sure if anyone is able to give us an update here 20:37:23 there he is! 20:37:28 right on target 20:37:30 :) 20:37:41 we're 2 package short of 12000 20:37:50 11998 of 13606 done 20:37:56 noice 20:37:59 current rate is about 5 packages per day 20:38:28 next week Marcin Juszkiewicz is joining Red Hat and that rate should improve 20:38:46 You've probably already seen him in #fedora-arm as user 'hrw' 20:39:00 seems slow. I've been noticing builders tend to be unproductive for - out of memory, the build just hangs, and some just seem to go out to lunch.. no clear reason 20:39:01 His primary task will be getting packages built/ported 20:39:28 We've long since run out of packages to build from F19-GA 20:39:42 As we pull in F19-Updates there are some aarch64 fixes here and there, so those succeed 20:39:50 ... and they fulfill dependencies for others to succeed 20:40:00 But we're basically at the point where every build is hard-won 20:40:20 Getting qt sorted should unlock quite a few (order of several hundred) 20:40:30 Everything else will just unlock little dependency pockets 20:40:48 #info 11998/13606 packages built 20:40:59 yep 20:41:14 bconoboy: I note that my project is still blocking on upstream 20:41:21 ghc upstream is dragging their heals 20:41:43 The next big step is going to be moving to F20 where more aarch64 fixes will be coming in. We'll also be reminded of anywhere we had to write a patch and didn't get that patch back upstream because we'll have to do it again. 20:41:58 #info It's time to move to F20 20:42:23 pwhalen: I'd guess most of the packages that are hanging are using qt. It's built but multithreaded code that uses it is hanging 20:42:35 #info ghc upstream is unresponsive so ghc-using packages aren't built 20:43:14 Any questions? 20:43:16 so on the builder/koji/f20 side of things... 20:43:25 ;) 20:43:45 #topic 3b) Aarch64 - Koji 20:44:19 any recent news on getting a koji instance up to host aarch64? 20:44:27 I haven't heard anything lately 20:44:41 I've had no time to work on it... I asked dgilmore and he said he would try and find time to set things up... 20:44:42 jonmasters: dgilmore is likely busy with building TCs and the like 20:45:00 jonmasters: Considering we just branched last week ... 20:45:05 handsome_pirate: indeed, hence I asked that it be on today's agenda so that we could figure out if nirik or anyone else had time 20:45:18 dgilmore: any update or eta? 20:45:19 nirik: ^^ 20:45:33 * jonmasters wonders if there might be anyone else with cycles. Dennis is awfully busy 20:45:47 see above? ;) I've not had time... hopefully dgilmore can. If someone else can I can see about helping them. 20:46:04 is there anyone else who might beyond the two of you? 20:46:18 * handsome_pirate *might* be able to help out in a couple of weeks 20:46:37 Likely not, though 20:46:45 I'll be up to my eyeballs in QA 20:46:48 jonmasters: not sure. Might be some internal folks who work with koji that could help? 20:47:17 I'd be interested to give it a whirl 20:47:41 * masta has been considering to setup koji here at the house anyhoo 20:47:49 nirik: if you can think of names, would be awesome, otherwise we could ask John? 20:48:02 ok, maybe the action here is 20:48:12 I can ask around 20:48:16 Gotta go 20:48:19 Peace, y'all 20:48:28 #action Wait for update from Dennis on Koji for AArch64, possibly ask around inside RH for assistance 20:48:33 handsome_pirate, thanks for joining 20:49:14 #topic 4) F20 Hardware Blockers - Should we define hw blockers at all? 20:49:36 this was already covered.. anything left here? 20:50:13 #topic 5) Should we reschedule the weekly ARM meeting? 20:50:32 I know the meeting doesnt seem to work for a number of people 20:50:34 what's the proposed reschedule purpose and time? 20:51:03 that, I dont know.. I just know it doesnt work for many folks 20:51:03 pwhalen: We probably need to hear from those we would be rescheduling it for, when works for them 20:51:08 * jsmith thinks the current time works OK for him 20:51:48 bconoboy, right.. 20:51:56 My guess is some of our european colleagues would prefer an earlier time slot 20:52:20 alright, I'll do a mailing list item to see 20:52:24 +1 20:52:25 #topic 6) Open Floor 20:53:07 it's no better or worse than any other time for me but it varies week to week 20:54:12 nothing for open floor?! 20:54:14 Zach Oglesby (zoglesby) and I have been working on the formal ARM guide as part of the docs SIG 20:54:42 (mostly based on the outline we looked at during Flock and the Secret Decoder Ring wiki page) 20:54:52 It's still pretty rough, but slowly coming together 20:55:07 #info F20 Alpha TC2 has been requested and should be out soon, testing appreciated! 20:56:04 jsmith, any link or too early yet? 20:57:07 pwhalen: It's just a git repo at the moment -- we haven't published it anywhere yet 20:57:13 pwhalen: I'll send more info to the mailing list 20:57:25 ok, thanks.. let us know if we can help! 20:57:39 last call for open floor... 20:57:59 Of course -- anyone can help that wants to! 20:58:24 #endmeeting