20:00:17 #startmeeting Fedora ARM weekly status meeting 20:00:17 Meeting started Wed May 29 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 j_dulaney msalter ahs3 agreene jcapik ddd 20:00:17 Current chairs: agreene ahs3 bconoboy ctyler ddd dgilmore dmarlin j_dulaney jcapik jonmasters masta msalter pbrobinson pwhalen 20:00:29 .fas pwhalen 20:00:29 pwhalen: pwhalen 'Paul Whalen' 20:00:33 .fas dmarlin 20:00:34 dmarlin_away: dmarlin 'David A. Marlin' 20:00:36 .fas blc@ 20:00:38 bconoboy: blc '' 20:00:41 good afternoon all 20:00:52 * pbrobinson is here 20:01:43 #topic 0) Status of ACTION items from our previous meeting 20:01:43 #link http://meetbot.fedoraproject.org/fedora-meeting-1/2013-05-22/fedora-meeting-1.2013-05-22-20.00.html 20:02:06 * pbrobinson wonders if he had any action items 20:02:09 #info complete -pwhalen to post ks used for highbank F19 Beta RC2 Install, add to the vfad wiki page. Beta ks added to wiki. 20:02:17 .fas jonmasters 20:02:18 jonmasters: jcm 'Jon Masters' 20:02:28 #info complete -pwhalen to post new image/instructions to the wiki for aarch64 quickstart 20:02:28 #link https://fedoraproject.org/wiki/Architectures/ARM/AArch64/QuickStart 20:02:43 pbrobinson, none for you 20:02:49 woo! 20:02:53 pwhalen: do we have the image ks files ? 20:03:06 * masta is here 20:03:16 dmarlin_away, dgilmore posted them to the spins git 20:03:17 .fas jcapik 20:03:20 jcapik: jcapik 'Jaromír Cápík' 20:03:22 dmarlin_away: dgilmore pushed them all to the spins kickstarts 20:03:31 thanks 20:03:37 #info kickstarts used in f19 arm beta are in the spins git repo 20:03:45 #link https://git.fedorahosted.org/git/spin-kickstarts.git 20:03:53 excellent 20:04:24 * j_dulaney waves 20:04:49 anything else from last week? 20:05:33 #topic 1) Problem packages 20:06:09 mostly random side packages. A couple of R-* that previously built 20:06:49 eclipse should build but keeps hitting the 24hr limit 20:07:21 that's it 20:07:29 #info eclipse keeps hitting 24hr limit on builders 20:07:40 * j_dulaney may give eclipse a shot locally 20:07:54 The 24 hour limit should be extended- it was when infrastructure was at seneca 20:08:10 48 is more realistic 20:08:19 j_dulaney: local makes no difference 20:08:36 bconoboy: that needs to go upstream then rather than a random hack 20:08:46 dgilmore? 20:09:18 bconoboy: what I said is basically a quote from dgilmore 20:09:30 who is going to do it? 20:09:31 pbrobinson: I mean do a basic fedpkg on it, see if it does complete building 20:09:43 j_dulaney: it does 20:09:44 #info from last last week - systemd's kernel-install calls new-kernel-pkg with wrong parameters (CLOSED) BZ#965897 20:09:55 pbrobinson: Sure, but if we're all in agreement that is the change, who is going to make the change? 20:10:18 j_dulaney: the eclipse team has built it, it built on rawhide and will likely eventually build on f19.... we're right on the cusp 20:11:10 bconoboy: the change to make it a config option isn't upstream so its likely to get that upstream and then mainline to agree to change the default 20:11:53 Isn't Fedora Infra upstream for Koji, anyway? 20:12:08 j_dulaney: no, it's but one user of it 20:12:25 Ah 20:12:33 this is probably a post-f19 issue 20:12:42 j_dulaney: redhat, facebook, twitter, cern..... and dozens of others.... 20:12:57 are all public users of it 20:13:13 #info koji default timeout of 24 hours is too short for eclipse on current builders 20:13:33 let's move on- we can discuss how to handle it later 20:13:44 agreed 20:13:53 yes move on 20:14:25 #topic 2) Kernel Status Update 20:14:46 3.9 is pretty stable... awaiting stuff from jonmasters. 20:14:55 3.10 needs more work 20:15:10 has 3.10 booted on anything? 20:15:20 kylem_rht was going to poke 3.10 a little? 20:15:30 I tried rc3 today on Panda, no go 20:15:41 yeah, i'll try to sort it out when i'm in the office tomorrow 20:15:46 upstream 3.10 boots on arndale (arndale needs 3.10, minimum...) 20:15:54 we haven't had major config changes 20:16:10 from 3.9 -> 3.10 20:16:15 i've seen other issues on 3.10 on other architectures, so i'm not terribly surprised it's taking a while to shake things out 20:16:18 only the merge of tegra 20:16:26 * j_dulaney is building what will be rc4 right now 20:16:37 I can revert that for a scratch build to see if it has any impact 20:16:40 there's probably some new config value we need to turn on in 3.10 for multiplatform arm to work 20:17:21 well that's possible but from the conversations I've had with the linaro guys there shouldn't be 20:18:24 anything else? 20:18:37 #info 3.9 good. 3.10 bad. 20:18:44 I'd like to hear from jonmasters on his 3.9 kernel action items 20:18:56 he's had a couple for the last couple of weeks 20:19:50 I'm working on the omap dss module ordering/loading issue at the moment 20:20:27 hope to get an update out in the next couple hours 20:20:33 k 20:20:38 excellent 20:20:46 #topic 3) Aarch64 Status Update, problem packages 20:20:51 I walked kyle through the vexpress issues and he wanted to pick that up, so I think I have given him enough to do that 20:20:59 #undo 20:20:59 Removing item from minutes: 20:21:21 #info jonmasters working on panda graphics issue 20:21:30 the CLCD driver stuff is going to be just a dtb problem like I discussed previously but kyle has volunteered to steer it forward 20:21:34 #info kylem_rht working on versatile express graphics issue 20:21:44 OK 20:22:00 now beyond that I looked at the patches for trimslice and bconoboy is going to try something I suggested 20:22:03 (for the internal SSD) 20:22:17 I'm doing nothing of the sort- somebody with an ssd trimslice needs to do so 20:22:31 well, ok, but I thought you were going to try in the farm internally? 20:22:33 jonmasters: is that similar to the timeout issues we saw earlier in the 3.x kernels?? 20:22:58 it would be better if somebody with physical access to the device did so 20:23:04 pbrobinson: yea, the trimslice SSD controller is just busted :) 20:23:13 I have one with the SSD 20:23:20 can you reliably crash it? 20:23:21 it works fine if the SSD is the /home directory 20:23:37 but I had issues when I tried to use it for rootfs 20:23:53 * j_dulaney notes that 3.10 build just failed 20:23:54 pbrobinson: can you run "hdparm -a" on the SSD device? 20:23:55 We need a good reproducer 20:24:02 * masta too 20:24:04 but I prefer it as /home anyway as if root is running on the SD it makes it easy to swap them out 20:24:07 pbrobinson: I'm interested to know what that says 20:24:12 trimslice was crashing on ssd, was wondering why 20:24:13 jonmasters: sure 20:24:50 masta: Can you reliably crash yours? 20:25:44 .fas oatley 20:25:44 oatley: oatley 'Andrew Oatley-Willis' 20:26:03 #info If you have a trimslice pro, please test the proscribed hdparm workaround on arm@lists.fp.o 20:26:14 bconoboy: well I'm not activly trying but I suppose I can monitor the uptime 20:26:17 #info "Topic: Re: Issues to solve before F19 ARM GA" 20:26:29 #link http://lists.fedoraproject.org/pipermail/arm/2013-May/006083.html 20:26:37 tnx pwhalen 20:26:54 np, next? 20:27:00 y 20:27:04 #topic 3) Aarch64 Status Update, problem packages 20:27:21 According to the nightly reportinator we've built 10335 of 13421 packages 20:27:51 That's probably a little high- it's counting identical packages with different nvrs, or which there are quite a few 20:28:03 I'll probably fix that today, so if the count goes down in tomorrow's report, don't panic. 20:28:46 We could use a hand on failed aarch64 builds 20:29:03 dmarlin and pwhalen have put together an auto-updating wiki page 20:29:25 pwhalen: have a link handy? 20:29:27 bconoboy: it's not really auto-updating 20:29:33 semi-auto-updating :-) 20:29:38 #link https://fedoraproject.org/wiki/Architectures/ARM/AArch64/Stage4_Problem_Packages 20:29:53 * j_dulaney is still working on GHC 20:30:04 If you'd like to share in the glory and honor of conquering aarch64, grab a package and go 20:30:19 However, I suspect that we're going to need upstream help with it 20:30:24 (You do this by putting your fas name next to the failed build) 20:30:44 j_dulaney: jcapik looked into it and reached the same conclusion 20:30:59 I pushed fixes for a couple of packages today while I was waiting for my customer's storage morons to unfuck their problems 20:31:21 pbrobinson: for aarch64? 20:31:32 no.... for mips.... 20:31:36 :-/ 20:31:38 :-P 20:31:45 I've created a feature request upstream 20:31:55 lol pb 20:31:58 Right now we aren't auto-updating the f19 source rpm repository on arm-temp, so the pool of source rpms is a couple weeks old 20:32:00 the aarch64 is not supported by GHC yet 20:32:12 j_dulaney: have you spoken with juhp for GHC? 20:32:15 #info ghc requires upstream aarch64 support 20:32:23 dmarlin_away, pwhalen: btw that is a very nice page 20:32:46 my input was minimal, dmarlins work 20:33:09 j_dulaney: if not do so, he's usually around on the arm channel and he's the fedora maintainer and actively assists with problems I've had 20:33:18 and helped porting issues etc 20:34:04 pbrobinson: I have not 20:34:11 That's it unless msalter has something to add (He's doing all the hard stuff) 20:34:16 pbrobinson: I'll ping him 20:34:21 Hmm no msalter here today 20:34:37 jcapik: Ping in #fedora-arm after the meeting 20:34:45 j_dulaney: ok 20:35:08 please try the new image and instructions, let me know if you have issue 20:35:13 he might have gone home but he's around regularly 20:35:25 oh pointer, one sec.. 20:35:40 #link Join in, visit http://fedoraproject.org/wiki/Architectures/ARM/AArch64/QuickStart 20:36:04 ok, next? 20:36:12 #topic 4) Blockers for F19 GA 20:36:24 #link http://lists.fedoraproject.org/pipermail/arm/2013-May/006083.html 20:36:34 that link sums it up nicely, thanks bconoboy 20:36:41 * bconoboy bows 20:36:49 Looking for volunteers to help with these issues 20:37:03 * pbrobinson needs to reply to that 20:37:08 The lvm console spam is *really* annoying 20:37:21 #action pwhalen to look into LVM console spam on first boot, The initial-setup does not appear to run 20:37:27 is there a BZ for that? 20:37:34 agreed, but gone after a reboot 20:37:48 I'm not aware of a BZ for any of the issues mentioned in the email. 20:37:49 for TI boards I'd like to propose we do the same as OpenSUSE and use their patches to u-boot so we have ext2 /boot instead of vfat. 20:37:53 pbrobinson, I havent found one, will open 20:38:20 #info Restorecon runs on first boot- can we avoid this? 20:38:26 does it happen with selinux=0? IE is it related to the labelling issue? 20:38:38 the lvm isssue that is 20:38:57 pbrobinson: I wonder the same thing. Don't believe anybody has tested booting with selinux=0 20:39:14 pbrobinson, have yet to investigate, but bconoboy mentioned that earlier as well 20:39:17 can someone put a link to an fpaste of the lvm error for this meeting's logs if you have one handy? 20:39:27 masta: 1) does it work 2) can we use it for the other platforms that need vfat too 3) there's others 20:40:17 pbrobinson: I'm in the process of making it work, and it does work for the suse guys, and 2) yes it would work across all TI boards. It means we would ntohave to have a 2nd image for TI boards, one image for everything 20:40:31 jonmasters, I documented it here, - https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/2013-05-21-VFAD-Fedora_19_Beta_RC2 20:40:31 pwhalen: try a new image with selinux=0 and that will give you a answer quickly so you don't waste time on it 20:40:36 but no fpaste 20:40:42 masta: does it let you just read and write files (MLO, u-boot, etc) as before, but on ext2? 20:40:44 pbrobinson, sounds good 20:41:11 masta: we have more than just TI boards I believe that need vfat 20:41:22 dmarlin_away: the MLO would be writen to the raw disk at offset 128 KiB using dd 20:41:29 :-( 20:41:37 so the MLO goes in the raw space before the first partition 20:41:40 masta: like any of the cheap imx boards.... 20:41:50 If we were going to pursue anything I'd rather it be combining the omap and non-omap images. a 20MB vfat partition is not a big deal. 20:41:53 masta: sounds less than desirable 20:42:14 and there's others that I can't think off the top of my fried brain without dinner head 20:42:20 pwhalen: ah, that "activation generator" output is systemd related 20:42:39 dmarlin_away: I think it's a very good goal to eliminate the omap image... 20:42:48 jonmasters, yes 20:42:53 we build just one image, install all the kernels. 20:43:01 masta: the omap image is wrongly named. It's not just needed by omap devices 20:43:38 pwhalen: systemd has "activation generators" that it creates dynamically. In the case of LVM I suspect it's because there is no LVM volume and some kind of error logic is not working right. I suggest we ping agk and point him to some ARM hardware within RH that he can help reproduce this with 20:43:40 pbrobinson: I was not aware of the other boards, and I guess I dont' own any of them.... will grab a wandboard when we support i.MX6 20:43:48 masta: imx, and others I don't have the details to hand need a vfat partition. So while we might remove it for TI based devices we'd still likely need to ship one 20:44:40 Just a few other things... 20:44:45 =( 20:44:50 Nobody at Red Hat is looking at these issues: 20:44:57 OMAP3 kernel not booting 20:44:59 jonmasters, found a little about that initially but was sidetracked, will do 20:45:10 Tegra X is unstable 20:45:26 - if those don't get volunteers their current condition will be their long term condition 20:45:52 * j_dulaney doesn't have h/w to work on either 20:45:57 pwhalen: I've pinged agk internally and you can see that too, so I'll let you and Alasdair talk about it/figure out a plan 20:46:09 jonmasters, thanks 20:46:23 #info OMAP3 (beagle baord) needs a volunteer 20:46:34 #info Tegra X stability issue needs a volunteer 20:46:43 I don't consider either of these blockers for GA 20:46:58 bconoboy: Why not? 20:47:12 Because they didn't work in F18 either. 20:47:20 jonmasters: do you have time to help me debug omap3 with fly swatter at some point? 20:47:23 bconoboy: If we officially support something, and if it doesn't meat criteria, by definition it's a blocker 20:47:42 j_dulaney: Your if conditional returns false :-) 20:47:43 bconoboy: If it doesn't work, then drop official support 20:47:55 Heh 20:48:08 There is no official support to drop, beagleboard hasn't worked since f17. 20:48:11 j_dulaney: we don't block on specific HW really, do you tend to do that for every bit of x86 HW. 20:48:24 tegra graphics working at all is a brand new phenomenon 20:48:26 bconoboy: it has... just not well ;-) 20:48:30 pbrobinson: yes, let me finish the current outstanding stuff and then let's do omap3 20:48:47 pbrobinson: first I owe you a working omap4 dss and then an update on mvebu (have not forgotten) 20:48:56 We have basically 2 weeks to track down and resolve as many of these issues as possible. 20:48:57 jonmasters: mvebu is highest prio IMO 20:49:21 pbrobinson: If it is widespread enough, yes, we'll block for specific hardware 20:49:25 jonmasters: I might be able to give you some direction post dinner on omap display 20:49:28 so that might be next week for the omap3. Ok. Well right after I finish this omap debug which should be soon then I'll switch back to mvebu and then we can sync tomorrow on other plans 20:49:38 #info Clock is ticking: F19 Freeze is June 18 20:50:38 anything else? 20:51:14 dmarlin_away wrote up an excellent page on atomics 20:51:15 I think that covered it 20:51:34 #topic 5) Flock Planning 20:51:40 * dmarlin_away will send link to the list 20:51:47 http://fedoraproject.org/wiki/Architectures/ARM/GCCBuiltInAtomicOperations 20:51:49 jonmasters: is he going to be lwn published? 20:52:12 pbrobinson: I'm suggesting we all post links to that URL and let Jon/Jake know 20:52:15 If you're going to submit a presentation at Flock you have until Friday. Friday is the submission deadline. 20:52:17 * jonmasters is putting that link on G+ now 20:52:29 #link http://fedoraproject.org/wiki/Architectures/ARM/GCCBuiltInAtomicOperations 20:52:45 jonmasters: http://www.fpaste.org/15332/13698607/ that's hdparm, want anything else? 20:52:49 dmarlin: Will you be presenting on gcc atomics at flock? :-) 20:53:30 #undo 20:53:30 Removing item from minutes: 20:53:54 * j_dulaney submitted a talk on arm virt 20:53:58 #link Fedora FLOCK in August http://fedoraproject.org/wiki/Flock 20:54:13 * pbrobinson submitted a ARM state of the union 20:54:14 pbrobinson: one sec 20:54:16 #link Official event site is http://flocktofedora.com/ 20:54:36 #info You have until *this* Friday to submit talks 20:54:43 and I need to submit a couple more 20:54:46 * ahs3 needs to submit ideas for a fedora janitors group 20:54:57 #info pbrobinson to present ARM state of the union 20:55:07 #info j_dulaney to present on ARM virtualization 20:55:18 pbrobinson: can you try passing "32" to that hdparm -a" command and see if it takes by running it again without the optional value? 20:55:32 guys, take it to #fedora-arm 20:55:39 k 20:55:47 next? 20:55:48 So that's 2 ARM talks. Anybody else? 20:56:04 ahs3: fedora janitors? 20:56:05 I might reprise the demo I am doing at Red Hat Summit 20:56:16 that's roughly what I'll submit as a paper to Flock 20:56:22 #info jonmasters to reprise his rh summit arm demo or similar 20:56:45 (I've something shiny to show) 20:56:49 jonmasters: http://www.fpaste.org/15333/36986100/ 20:57:00 pwhalen: next 20:57:09 * j_dulaney wonders at jonmasters shiny 20:57:18 now boys... 20:57:19 #topic 6) Open Floor 20:57:32 #link David Marlin's guide to gcc atomics http://fedoraproject.org/wiki/Architectures/ARM/GCCBuiltInAtomicOperations 20:58:26 anything else? 20:58:48 going once.. 20:59:03 #endmeeting