/srv/irclogs.ubuntu.com/2012/05/15/#ubuntu-kernel.txt

=== jmp_ is now known as _jmp_
snadgejerusalem01:05
=== jmp_ is now known as _jmp_
=== smb` is now known as smb
* smb mornings07:21
* apw yawns07:52
smbapw, sync;sync;sync07:52
apwreboot07:53
apwoops07:53
smbheh07:53
ppisatibloody jetlag...08:13
* dileks thinks if there where a hwclock.service for internal human clock08:17
ppisatibug 98535408:52
ubot2Launchpad bug 985354 in ubiquity "Lubuntu 12.04 20120418 install fail" [Undecided,Confirmed] https://launchpad.net/bugs/98535408:52
apwcking_, did we decide to enable ALPM for Q ?08:56
cking_apw, it was not discussed, but it probably should be to see what fall out we hit08:57
=== cking_ is now known as cking
apwBryan Wu (1):09:05
apw      MAINTAINERS: add maintainer for LED subsystem09:05
apwcooloney, congrats09:05
* cking notes that there is only so much coffee the brain can handle to try to overcome jetlag10:50
* ppisati -> goes looking for food11:57
tgardnerapw, hows it coming on collapsing generic and virtual ?12:00
apwjust looking at those patches now12:01
tgardnerapw, I promised the preempt guy that we'd add his flavour only if we could collapse virt and generic12:02
apwtgardner, yeah ... we should add an item for that, then i can follow through when this is done12:02
tgardnerapw, to the blueprint ?12:03
apwyeah12:03
tgardnerapw, I started the lts-backport-quantal branch in precise yesterday. still a bit of messing around to do.12:04
apwtgardner, ok cool.  do we have a PPA for that yet?12:04
tgardnerapw, not yet, thought I'd get the kernel building first.12:04
apwi more meant have they decided where the combo ppa will land12:05
tgardnerapw, I think we can just use an existing PPA, can't we ?12:05
apwwe probabally want another team which holds it12:05
apwas its gonna be for us and X12:05
tgardneroh, right, forgot about X12:05
apwwe need to poke bryceh about what might work12:06
tgardnerapw, I'll hassle byrce when I've got it building12:06
Guphi, issue with networking/suspend since kernel update.  details: http://pastebin.com/VdMVRWQb  anyone recognise the symptoms, or have an idea what to try next?12:11
apwGup, sounds like you have a known working and known not working kernel version, so get a bug filed and let us know the number, we would want to then to a bisect between the two to work out whats bust things12:13
apwGup, there is a page on doing bisects if you want to attempt it yourself12:13
apwjsalisbury, can you point us to the bisect guide ?12:13
Gupi'll certainly file a bug.  i'll have a look at the bisect guide and see what it involves12:14
Gupi tried to find a changelog to get an idea but it looked like it contained lots of changes that might have been the cause12:15
apwGup, probabally a stable update or similar12:15
Gupi'm not overly familiar with the kernel and its workings, i did compile one a couple of times, but thats been a few years12:17
apwsmb, ok you'll be pleased to know all of the patches in that intel-idle branch you pointed me to are now in mainline12:24
apwsmb, is this something we can test works ?12:24
apwsmb, with the quantal kernel, before i commit removing this thing :)12:29
Gupthe link to the bisect guide on here is broken :s https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies12:37
apwjsalisbury, you have been doing a number of these, would you be able to fix the docs :)12:42
apwhttps://wiki.ubuntu.com/Kernel/KernelBisection12:43
apwGup, have you seend the above one ??12:43
Gupahha thanks apw, i hadn't found that yet, i will have a go12:44
tgardnerapw, I see that the hv folks are getting traction with the Debian kernel community12:47
* tgardner bounces for quantal kernel backport to precise12:58
ogasawarahrmph, https://launchpadlibrarian.net/105081769/buildlog_ubuntu-quantal-amd64.linux_3.4.0-2.4_BUILDING.txt.gz13:01
ogasawarabah, https://launchpadlibrarian.net/105086088/buildlog_ubuntu-quantal-i386.linux_3.4.0-2.4_FAILEDTOBUILD.txt.gz13:02
tgardnerogasawara, puny little buildds13:02
tgardnerogasawara, I have a patch in master-next to fix the perf build problem13:04
* ogasawara fetches13:05
tgardnerogasawara, I thought the erro you were pointing at was because the buildd ran out of disk, but I see that its really a packaging error13:05
ogasawaratgardner: I was confused as why it would fail on i386 and not amd64, but seeing your patch explains it13:06
tgardnerogasawara, it seems its a change from precise13:06
tgardnerogasawara, I had at least one build trace that failed within the perf makefile, so I can only assume its a concurrency level issue.13:07
smbapw, About those patches, I can confirm on intel and on my amd that it enables the cpufreq in xen. There were no bad effects. 13:26
apwsmb, ok cool.  so as all of them are in quantal things should be good.  i'll clean up and get this merger in13:27
smbTo see whether it gains something, one needs to check performance13:27
apwyeah not expecting it to be better, just not worse13:27
smbIn theory it should be better at least on intel as it should allow usage of turbo mode.13:28
jsalisburyapw, I'll review and fix up the kernel bisection docs.13:32
apwjsalisbury, thank13:32
jsalisburytgardner, ogasawara, Do you still want to have the top ten meeting today, since all the top ten bugs are currently precise bugs?13:34
ogasawarajsalisbury: anything new for precise on the list?13:34
jsalisburyogasawara, nothing yet, but I'm still catching up from pre-uds.13:34
ogasawarajsalisbury: if there's nothing new atm, we can probably skip it.  just ping us if anything does pop up that need discussing13:35
jsalisburyogasawara, sounds good.  Thanks.13:35
tgardnerjsalisbury, yeah, what she said.13:41
jsalisburytgardner, ack13:42
cooloneyapw: sorry for missing your msg13:47
* cooloney is still in jetlag,13:48
apwcooloney, heh, when i heard you had fun with a bird in SFO i assumed you would be off13:48
cooloneyapw: yeah, it's really fun. hah, we heard a very loud crashing noise in the air. 13:50
apwcooloney, man that must have been a fright and no mistake13:50
ogasawaracooloney: heh,  I wouldn't call hearing a crashing noise while in flight "fun"13:50
cooloneyapw: after a while, pilot said our engine was hit by a bird. OMG, I just sat close to the engine13:50
tgardnercooloney, shit, thats just the kind of noise you _never_ want to hear on a plane.13:51
* apw bets that the engine does not enjoy eating birds13:51
cooloneyso we flew back to SFO. 13:52
cooloneyi saw some dirty liquid in the engine when I was getting off the aircraft13:53
cooloneyso we had to stayed in SFO for one more night13:53
apwcooloney, sounds awful.  especially staying another night13:56
cooloneyapw: actually i was upgraded to economic comfort classed in first flight13:57
cooloneyapw: after a bird hitting, i had no chance to upgrade 13:58
apwdouble buggeration13:58
smb... another ass hurting...13:59
cooloneysmb: heh, any wiki or lp link for lxc stuff? i intend to try the testcase on my pandaboard.14:01
smbcooloney, test cases, we do have test cases? ;-P14:02
smbcooloney, But joke aside. I am not sure...14:04
apw cooloney, hallyn is probabally the right person to talk to about how we are using it and so what to test14:04
smbHe and stgraber 14:05
smbFor a quick test, I just installed the package, made sure the cgroup fs is mounted (which should be automatic now) and tried running some of the quick examples from the man page14:06
hallyncooloney: I'm in the middle of an update that i haven't tested yet, but lp:~serge-hallyn/+junk/lxc-test has my testcases14:07
hallyn(high-level ones mostly, besides the reboot ones)14:07
smbcooloney, There is also a chapter in the server guide https://help.ubuntu.com/12.04/serverguide/lxc.html14:08
cooloneysmb: yeah, i heard hallyn mentioned that during that lxc session.14:09
cooloneyhallyn: thanks for pointing out this. i will try that14:09
cooloneyand i believe arm server folks already run them on arm server14:10
hallyncooloney: yup, that's what ahs3 said.  But thanks, the more people running it the better14:12
hallyni guess this means i better go test my changes :)14:12
apwhallyn, cooloney soon will :)14:13
hallynheh, good point, on to my next work item :)14:13
cooloneyhallyn: sure, 14:14
* cooloney setting up pandaboard14:14
hallynj/k.  i couldn't test at end of uds bc of bandwidth.  need to try it out14:14
=== yofel_ is now known as yofel
hallynjsalisbury: did we pick kernel-kvm as the tag for fwded bugs?  or kvm-kernel?  :)14:36
gematyhicks: ping14:38
gematyhicks: can you please fix the work items for the ecryptfs blueprint?14:38
gematyhicks: it seems not to want to take my changes and it is messing up the work items ... sorry14:38
apwherton, does shank-bot make bugs for linux-lowlatency ?14:38
hertonapw, no, just for our kernels at the moment14:39
apwherton, are we doing linux-amardaxp ?14:39
bjfapw, yes14:39
hertonapw, we should be on next cycle, bjf added the code there14:39
* apw notes lowlatency is lagging severely already ...14:40
apwherton, bjf, cool stuff14:40
bjfapw, that's a "community" kernel is it not?14:40
apwbjf, yes currently so, wondered if it would make sense to make bugs for them14:40
bjfapw, we don't for ports kernels either14:41
apwbjf, there are no ports kernels which arn't in master are there?14:41
bjfapw, ah, true14:41
apwso we may be being lucky there more than anything14:42
tyhicksgema: Hey - what changes would you like me to make?14:42
* apw will chat to abogani about it, and maybe ask you again14:42
bjfapw, ack14:42
hertonbjf, btw, armadaxp lacks a entry for the meta-package on ubuntu.py. I was wondering also if we should make Ike the owner of prepare-package on workflow.py14:42
apwabogani, your lowlatency kernel is lagging, who am i meant to poke about that, you ?14:42
apwherton, for now ike is on the hook for everything armada related14:43
bjfapw, wasn't tgardner considering us picking up lowlatency (uds session)14:43
tgardnerbjf, preempt in Quantal14:43
apwbjf, it may become portlike in Q yes14:43
bjfherton, yes, we should hadd the meta package. i thought there was a LP "team" that got assigned, that should be used14:44
bjftgardner: you are correct as always14:44
smbbjf, herton Just happened to notice that the vcs-git line of precise linux-meta refers to Karmic... Wonder whether  fixing this should require a bug report and all the fun...14:44
bjfsmb, lol14:44
apwsmb, you might file 'one bug' and use it for all the releases, cause i bet its wrong in all of them14:44
hertonbjf, I think the team thing never flied, I'm not sure Ike is on ubuntu-armel-kernel and watches it14:44
* apw says stike ike on, he'll soon ask you to change it to a team once he starts drowning14:45
smbapw, Likely at least between karmic and now... :)14:45
bjfherton, lets coordinate with ike. i want it to be a team and not a person14:45
hertonbjf, ok14:45
vanhoofbjf: +1 14:46
bjfherton, even if it's a team of one right now14:46
* apw suggests we make a team with just vanhoof on it14:46
vanhoofbjf: we have a few teams now, would you like something trimmed down in size?14:46
* vanhoof *hides*14:46
hertonyes, it's better being a team14:46
* ogasawara back in 2014:47
smbbjf, herton opened bug 999726 for tracking14:51
ubot2Launchpad bug 999726 in linux-meta "Fix Vcs-Git in linux-meta" [Undecided,New] https://launchpad.net/bugs/99972614:51
bjfsmb, ack and thanks14:51
bjfhenrix: ^14:51
henrixbjf: ack14:52
smbbjf, Was just about to ask whether I should do something about it ... :) But this wfm214:52
bjfsmb, nah, we'll take it14:53
kirklandtyhicks: I reckon I probably didn't take notes in the modern work-item manner14:53
kirklandtyhicks: apologies14:53
kirklandtyhicks: behind on the times14:53
* bjf will brb14:53
jsalisburyhallyn, yes, kernel-kvm is the tag14:53
* tgardner biab14:54
hallynthanks, written down :)14:54
jsalisburyogasawara, whould you like me to change "[TOPIC] Status: Precise Development Kernel (ogasawara)" to Quantal?15:02
apwjsalisbury, makes sense15:02
jsalisburyapw, sounds like a plan then15:03
apwtell me we don't already have a meeting today ... yawn15:03
jsalisburyapw, yup.  Top Ten is canceled, but the IRC meeting is still on, for 17:00 UTC15:04
apwgood grief do we get no time off15:04
jsalisburyheh15:05
=== BenC__ is now known as BenC
* bjf is back15:15
tyhicksgema: I *think* that I fixed the work items according to the comment you left. Let me know if it still isn't right.15:16
ogasawaratgardner: was reviewing https://wiki.ubuntu.com/Kernel/Release/Rolling, the 14.04 section, should that be linux-image-<flavor> will reference the current supported kernel, not linux-image-<version>-<flavor> ?15:18
tgardnerogasawara, prolly15:18
tgardnerogasawara, feel free to correct that15:19
ogasawaratgardner: ack15:19
gematyhicks: looks good to me, as long as you are sure you haven't lost any other task, I am happy15:43
tyhicksgema: I'll take a second look at the notification emails to ensure that nothing was lost. Thanks!15:43
gematyhicks: ack15:49
tyhicks(everything looks good)15:49
* cking punches fwts json logging into submission15:49
=== BenC__ is now known as BenC
smbO_o lucid pointing at karmic16:20
henrixsmb: yeah, a couple of branches had that problem too :)16:22
smbSomehow I would have understood them pointing at something earlier but forward is confusion16:25
* henrix is confused... isn't karmic earlier than lucid?16:27
smberr yes16:28
* smb needs to get his letters right...16:29
henrixsmb: btw, i tried to add lucid to the bug you filled... but couldn't figure out how to do that :-/16:38
smbhenrix, No you cannot by bad design16:40
henrixsmb: ah, cool!16:40
smbhenrix, its approved now16:40
henrixsmb: thanks16:41
smbhm, and to make this small thing really big, I probably should add the topic branch packages, too..16:42
smbhenrix, Oh, but fsl-imx51 and mvl-dove not relevant anymore...16:44
henrixsmb: yeah, i was not sure if all of them were relevant... so you can just NACK those two16:44
smbhenrix, yup, oh seems natty/ti-omap4 is pointing at maverick16:46
apwogasawara, i just did a test build and it failed with the same (i think) perf thing even with the top of master-next (inc tims fix)16:50
apwinstall: cannot stat `/home/apw/build/ubuntu-quantal/ubuntu-quantal/debian/build/tools/tools/perf/perf': No such file or directory16:51
ogasawaraapw: bah, my test build passed.16:51
* ogasawara holds off on the upload16:51
ogasawaraapw: that was indeed the same failure.  were you using one of out build machines or something local?16:52
apwogasawara, that was a gomeisa build, doing a 'full_build=true' build to test dropping -virtual16:52
smbhenrix, Ok, I hope I have added all the tasks you would need for that bug16:52
ogasawaraapw: I'll try to reproduce16:53
tgardnerapw, so wtf is going on with perf ?16:53
henrixsmb: ok, cool. i missed the natty/ti-omap4, as i just grep'ed for karmic. i should have manually checked everything16:53
apwwell the base error says perf wasn't built, or it got removed before we made the package i guess16:53
henrixsmb: will check them all again16:53
tgardnerapw, thats different then the intermediate failure16:53
tgardnerapw, how could it get removed?16:54
apwtgardner, yeah and i think its what leann saw16:54
smbhenrix, topic-branch madness. Looks like all ti-omaps like maverick16:54
apwtgardner, reading the logs now, hopefully i can see where it broke16:54
henrixsmb: ok, i'll edit the bug description so that it's a little bit more generic16:55
smbhenrix, Cool, thanks16:55
henrixsmb: i'll replace the "karmic" in the desc by something else16:56
apwtgardner, ogasawara, ok it looks like when we build the indep version the manual build is now wacking it16:56
apwrm -rf /home/apw/build/ubuntu-quantal/ubuntu-quantal/debian/build/tools16:57
apw...16:57
smbYeah, can now be Vcs-Git is wrong just about anywhere in linux-meta... :-P16:57
apwmake[1]: Leaving directory `/home/apw/build/ubuntu-quantal/ubuntu-quanta16:57
apwl/debian/build/tools/tools/perf'16:57
tgardnerapw, hmm, wonder why ?16:57
hertonsmb, you know, copy & paste everywhere :)16:57
apwrm /home/apw/build/ubuntu-quantal/ubuntu-quantal/debian/build/tools/tools16:57
apwinstall -s -m755 /home/apw/build/ubuntu-quantal/ubuntu-quantal/debian/build/tools/tools/perf/perf \16:57
apwso i think we build and prep the mans and the tools binaries in the same directory16:58
apwso depending which order we do them depends on which we have to package16:58
tgardnerapw, that seemsl ike a bad thing16:58
jsalisbury**16:58
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting16:58
jsalisbury**16:58
smbherton, sure. :)16:58
apwtgardner, indeed it does16:58
* apw pokes ...16:58
apwtgardner, this has almost cirtainly come out of our paralellisation work, and likely in P we were just lucky17:00
tgardnerapw, it has been bugging me for awhile17:00
tgardnerit  just hasn't happened enough to got to the top of my list17:01
apwtgardner, its just wrong, we do two things which can be done in parallel on i386 on the same tmp dir... just working out which is easier to move17:01
ogasawaraI'm surprised we were lucky all of Precise to not get hit by this17:01
tgardnerapw, seems simple in retrospect17:01
tgardnerogasawara, -j1 on the buildds17:01
apwogasawara, i think we do more parallelism now that we did17:01
tgardnerapw, we could just serialize tools packaging. its not like it takes that long17:02
apwtgardner, its not tools which need serializing, they need serialising wrt 'indep' in general, which isn't reasonable.  they should be in differnet places17:04
tgardnerapw, which is gonna be a bit of churn. I think Leann is OK to upload given the buildds are at most -j2, don't you think ?17:05
apwtgardner, it looks trivial to move the perarch indep, so i'd say give me an hour to work it and decide after17:06
tgardnerapw, ack17:06
apwtgardner, the bid buildds are -j16 arn't they ?17:06
tgardnerapw, whats a bid buildd?17:06
apwtgardner, big ... there are two which are monsters relativly speaking17:06
tgardnerapw, ah, didn't realize we had anything other then the -j1 xen instances17:07
apwtgardner, oh is this going to a PPA, then yes17:07
apwtgardner, in that case shove it in17:07
tgardnerapw, no, she's gonna upload it to the quantal archive17:07
ogasawaraapw: I'm not uploading to a PPA17:07
apwso it all depends on the buildd then that it hits17:08
tgardnerapw, we could clamp it to -j1 just for the buildds, but thats kind of a hack.17:08
ogasawaraapw:  I think we want the patch rather than rolling the dice on buildd's17:09
ogasawaraapw: or we could have infinity or someone retry the current i386 build on a more susceptible buildd17:10
apwyeah you could just put it back and see what happens17:11
apwi think i have a fix so will go test build it to confir17:11
apwtgardner, ogasawara, we may be simply hitting it more on quantal cause of a make change for instance17:15
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues May 22nd, 2012 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
tgardnerapw, its certainly been annoying me more of late17:15
apwtgardner, we have be going more and more parallel and releasing the bits which stop it going fast, so we should be hitting it more really17:18
tgardnerapw, indeed, that is my empiracal experience17:18
apwtgardner, and possibly depending how you build it you could make it happen, i think the act of building it with dpkg-build package, the make build-foo; fakeroot make foo; ought to near guarentee it happens i think17:19
apwwell i suspect we either lose the binaries or the manuals, but the manuals we don't install by name we just take * so we'lll only notice one way round perhaps17:19
tgardnerbjf, just pushed some cruft onto ubuntu-precise-meta master. please review prior to uploading.17:20
bjftgardner, ack17:23
bjfhenrix, herton ^17:23
hertonack17:23
henrixbjf: ack17:24
LightScryHi, I'm trying to implement "syscall" and having trouble.  My code looks like this: http://cl.ly/3Q2n12113a2X3737191R17:24
LightScryIt always returns -1.17:25
apwtgardner, that seems to only refer to generic and server, but we have generic-pae on i386 and only that right ?17:25
* henrix will be back in ~30mins17:25
tgardnerapw, since its a meta package its abstracted by one level. it should refer to -pae in i38617:26
bjfcking: https://chrome.google.com/webstore/detail/bcjindcccaagfpapjjmafapmmgkkhgoa17:26
apwtgardner, plus there are only linux-image ... shouldn't there be linux-headers-* as well17:26
tgardnerapw, not sure if we wanna propogate that level of complexity, do we ? do we need the headers ?17:27
ckingbjf, I'm using: http://jsoneditor.net/17:27
apwtgardner, anyone needing dkms needs a meta package for their headers17:27
apwtgardner, so either make them linux-hwe-<flavour> and dep on both headers and image, or you need both me thinks17:28
tgardnerapw, they can always reference the header meta-package directly. I don't think we should support automatic dkms upgrades from release to release.17:28
apwtgardner, but then they update their kernel automatically and any dkms they have just stops building even if its compatible17:29
tgardnerI think dkms is guaranteed to break. look at nVidia.17:29
apwtgardner, well we should be testing those before we inject the new kernels if they are supported if thats going to be the only kernel in a while17:30
apwtgardner, especially for binary drivers for graphics17:30
apwas those are no longer opting in really are they, they are getting updated17:30
tgardnerapw, well, I guess I'm OK with depending on the headers from the -hwe- and -current- meta packages. I just didn't want the combinatorial explosion.17:32
apwwe might want to take out 'image' to make it clear if we do that17:32
tgardnerapw, yeah, I'll update it in a bit. need fuud first17:33
=== tgardner is now known as tgardner-lunch
=== tgardner-lunch is now known as tgardner
apwtgardner-lunch, i can see why my builds never see this normally as i build the indep and dep parts separatly always17:54
apwogasawara, have you been able to reproduce the perf thing locally, you would have to build 'binary' to see it i think ... as it requires a perarch and an indep run to be in parallel17:57
apwogasawara, anyhow if you are, i have a patch which seems to resolve it ... shall i shove it17:57
ogasawaraapw: go ahead and shove it.  I have not been able to reproduce yet17:57
tgardneryeah, its kind of tweaky17:58
apwbuilding binary-gneeric will never show it, nor will indep, but for me a binary always tiggers it at -j256 17:58
ogasawaraapw: lemme try that.  In the mean time I did kick off a re-build for i386.  It landed on aatxe.17:59
apwogasawara, ok pushed.17:59
ogasawaraapw: I'll clean up the tree since I never did officially upload 3.4.0-2.518:00
apwogasawara, i also have an overlayfs.v13 update pending, but don't want to throw that in if you are struggling to build18:00
ogasawaraapw: ack18:01
tgardnerapw, repushed ubuntu-precise-meta18:11
apwtgardner, so i wonder if the package is going to bring image and headers should it be just linux-hwe-generic18:13
apwas 1) its different and 2) if we ever do need them separate for some reason, like for the CDs we have space to put them18:13
tgardnerapw, ah, forgot that. will fix.18:13
tgardnerapw, fixed18:14
tgardnernow I need to fix the descriptons as well18:15
apwtgardner, i wonder if the linux-generic references should be linux-image-generic18:16
tgardnerapw, why?18:16
apwtgardner, we were talking aboue making linux-gneeric be both perhaps, or removing them, so it might be nice to miss the double indirect18:16
apwtgardner, either way right now they are just a double indirect, do we want that18:16
tgardnerit seems simpler form a conceptual viewpoint, but its really 6 of one, half dozen of another18:17
apwie we'd have linux-hwe-generic -> linux-generic -> linux-image-generic -> linux-image-xxxx-generic18:17
apwand linux-hew-generic seems same as linux-generic in the hierachy, so perhaps we should point to l-i-generic18:18
apwmatters not much at this point as its not affecting any new names or anything18:18
tgardnerapw, ok, repushed again18:28
apwtgardner, so the only thing i find confusing now is that we have -generic and not -generic-pae at the top level for i38618:29
tgardnerapw, you mean linux-hwe-generic ?18:29
apwyeah i'd expect that to be amd64 specific i think, and have a -pae i386 specific18:30
tgardnerapw, I think -pae will disappear on our way to 14.04. this is supposed to be an abstract meta-package name18:31
tgardnerapw, frankly, I;d like to change Quantal so that -pae disappears18:32
apwtgardner, i almost want to it be -desktop and -server or something, but thats probabally reaching bikeshedding18:32
tgardnerapw, quantal should have _just_ a generic flavour (that also happens to be the PAE kernel)18:33
tgardnerthen we've homogonized across i386 and amd6418:33
apwyeah makes sense, and we should do that rsn18:33
tgardnerapw, I can make that happen :)18:33
apwtgardner, it will conflict heavily with my -virtual work, so perhaps i should do it on top of that18:34
tgardneras soon as ogasawara is done faffing about18:34
tgardnerapw, when you do that, remember to go back and fix ubuntu-precise-meta lts-backport-quantal18:35
apwACK18:35
tgardnerand ubuntu-precise lts-backport-quantal18:36
apwtgardner, *cough* lts-hwe-12.10 surely18:36
tgardnerapw, its a branch name18:36
tgardnerwho cares18:36
apw:)18:37
tgardnerapw, am wondering, given your builddirpa patch, if perf build really is parallel safe.18:50
apwtgardner, it may well be, i have not tested it reverting your change to -j1 yet18:58
apwi figured you'd probabally re-test once this upload was up and we could revert18:58
tgardnerapw, yep. I'm backporting it to older releases, so it'll get some good testing. tangerine is gonna get worked18:59
apwtgardner, i assume the issue is somewhere back to O in theory, not really sure why we've never noticed before19:02
apwtgardner, so you are doing the backport for the tools build bit yes ?19:02
tgardnerapw, dunno, but it is pretty racy19:02
tgardnerapw, yep19:02
apwthen i can crack a beer and let these virtuals build19:03
tgardnerthats common all the way back to lucid19:03
apwla la la ...19:03
tgardnerapw, I'm also thinking this is bogus: install-tools: install-source $(stampdir)/stamp-build-perarch19:03
apwthere are two linkages there, install-source to get source done at all, and stamp-* to build the perarch tools19:04
apwi think its odd but right, the build-arch (ish) which has install-tools on it, should have install-source i think, but i'd be less keen to fix that back to L19:05
tgardnerapw, its the stamp-build-perarch dependency that is unorthogonal19:05
apwahh ... we wen't through that phase of getting rid of the direct build-xxx things forgetting that they were used to allow make build-foo; fakeroot make foo19:06
apwtgardner, so it should be build-tools and build-tools: stamp-* with the @; to make make happy thing we see elsewhere ... probabally19:07
apwbut we optimised a number out, that was inserted after that optimisaiton19:07
tgardnerapw, yeah, lemme noodle on it for awhile. you go have a beer.19:08
apwogasawara, i've done two test builds with that perf fix 'full_build=true' stylee on gomeisa and no problems, i was 2/2 bad before19:08
ogasawaraapw: I just reproduced here as well w/o the patch, am going to redo with it.  assuming it's successful I'm going to upload.19:08
ogasawaraapw: I've pushed the proposed upload to master-next19:09
apwogasawara, nice ... fingers crossed, its pretty blatently wrong19:09
ogasawaraapw: the re-build for i386 on the buildd failed with the same error19:10
* tgardner -> EOD19:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!