TheMusobjf: When you get a minute, could you possibly kick the alsa modules daily builds over to new ABIs?00:57
TheMusoThanks in advance.00:58
=== jjohansen is now known as jj-afk
bjfTheMuso: lucid daily is already at -24 could do -25 for proposed01:37
TheMusobjf: Ah ok, I don't think -25 matters for proposed at this point, but what is disturbing is that some users have filed audio bugs using the proposed 2.6.32-25 kernel.01:38
=== tm_ is now known as tm
=== jj-afk is now known as jjohansen
=== diwic is now known as diwic_afk
lagCan someone test this for me?09:30
smblag, this?09:31
lagcd to a git repo and issue: BRANCHES=$(git branch) && echo $BRANCHES09:31
smbmaybe BRANCHES="$(git branch)"?09:31
smband echo "$BRANCHES"09:32
smblag, The version with all "" works... now without09:33
lagI'm more interested to know where it's acquiring the directory listing from?09:33
smbTrying to find a logically sounding explanation but it has to do with shell expansion somewhat09:34
smblag, ah because you have a * in the result09:35
lagWell spotted09:36
lagBRANCH=`git branch | grep \*` && echo ${BRANCH#* }09:37
smblag or BRANCH=$(git branch | awk '/^*/{print $2}') ;-)09:40
lagI'd just typed up a similar line using sed :)09:40
lagBut I think yours is more readable, I'll use that09:40
smbAt least it helps me that awk can look very much like C09:41
jk-set -f; BRANCHES=$(git branch); echo $BRANCHES09:42
jk-i guess you don't want the * though..09:43
smbheh, a hundred ways to do it09:43
jk-BRANCHES=$(git branch | tr -d '*'); echo $BRANCHES09:43
smblag, Yeah, you could do a git branch | awk '/^*/{printf("%s\n", $2);}' as well09:43
lagI like smb's first one :)09:45
lagHave you all finished flexing your Bash muscles now? ;)09:45
jk-b=$(git branch); echo "${b/\*/}" <- one less fork09:45
lagClearly not :)09:46
smbThe winner of most unintuitive code today is .... jk-  ;-P09:46
jk-b=$(ls .git/refs/heads/)09:48
smbThat would mean we understand how git actually works...09:48
jk-so +1 for a layering violation too?09:49
smbhehe, yeah. unfortunately you cannot trust it even when using the commands as apw and me found out for git remote show -r09:50
=== amitk is now known as amitk-afk
lagI have a new favourite 09:53
lagBRANCH=`git branch | grep \* | cut -d ' ' -f 2`09:53
lagSimple, effective09:53
jk-lag: you only want the current branch?09:54
jk-i'd go for the awk then :)09:55
lagI like the awk version09:56
lagBut this one is easier to read: BRANCH=`git branch | grep \* | cut -d ' ' -f 2`09:56
smbIt probably has more every-day-use commands. And having a third fork unlikely will really matter 09:57
lagIt'll only be run once for every compile09:57
* apw starts his UHS prep ... with a haircut10:01
=== diwic_afk is now known as diwic
lagWhat do we have to wear for UHS?10:06
AceLan_lag: I think you'll get a new t-shirt for it10:11
lagT-shirt sounds good10:13
lagAceLan_: Is your lecture prep'ed?10:13
AceLan_lag: http://shop.canonical.com/index.php?cPath=14 # Ubuntu Polo Shirt (Black)10:13
lagCould be worse :)10:13
lagI'm assuming I don't have to pre-order it?10:14
AceLan_lag: don't worry, I'm pretty sure you'll get one for free10:14
lagI still haven't spent my joining voucher10:15
jjohansenha, I forgot all about the joining voucher, /me hasn't spent it either10:16
AceLan_me neither :p10:18
cooloneyCanoical shop doesn't ship goods to China, so me either10:19
diwicIn addition, the shipping cost takes half the voucher10:39
diwiclag, the dress code is actually listed as "Smart trousers, not jeans" and ubuntu t-shirt, which I assume Fanny will provide when we get there10:40
lagGreat, thanks David 10:44
lagcooloney: You can always send it to me :)10:44
ckingsmart trousers? Hrm.10:45
cooloneylag: haha, yeah, i will ship an new iphone4 and ipad to you10:45
jk-woot, free gear10:45
smbdiwic, I would treat the dress code with care. Its copied over regardless of occasion and you might look strange around the geeks. :)10:45
cooloneylag: and pls bring them to UDS for me10:45
ckingdoes it specify smart socks too? Can I wear multi-coloured ones?10:46
* smb does not want his clothing to be smarter than himself10:46
ckingdress code did not specify underwear10:48
=== diwic is now known as diwic_lunch
smbdiwic, Would you have an explanation on the feedback to bug 587546. It seems reported as the patch in proposed has no effect (must admit I have not looked really at details). 10:52
ubot2Launchpad bug 587546 in linux (Ubuntu Lucid) (and 3 other projects) "Pulseaudio fails after several seconds (affects: 1) (heat: 41)" [Low,Fix committed] https://launchpad.net/bugs/58754610:52
lagcooloney: I didn't mean the goods, I meant the voucher10:53
lagcooloney: But if you want to ship anything to me, I'd be happy to bring it over to UHS/UDS10:53
cooloneylag: np, you are so kind. heh10:54
cooloneylag: anything you need we bring from China, just tell us10:54
lagAll the tea10:56
lagActually I'd quite like a 'Naja atra'10:56
cooloneylag: what's 'Naja atra' is green tea?10:58
cooloneyyou know green tea is common in China10:58
lagThe first request was "All the tea", as in "All the tea in China"10:58
lagYou will have to Google Naja atra for yourself :)10:58
smblag, You have a big suitcase and know some people working for the airline and customs? ;-)11:04
lagFor which item?11:06
lagI don't think I have a big enough suitcase for all the tea in China11:06
lagFor a few Naja atra maybe :)11:07
smbLikely all of them. But especially the Naja atra I guess11:07
smbProbably cking and apw want a different plane than you back as well. :-P11:08
=== dmarkey_ is now known as dmarkey
=== ivoks-afk is now known as ivoks
=== smb is now known as smb-afk
=== diwic_lunch is now known as diwic
diwicbjf, guess what - it's ABI bumping time!11:35
=== ivoks is now known as ivoks-afk
apwsmb-afk, he'll be stuck in customs for the duration when they find out he is a purper12:13
apwdiwic, heh bad boy12:16
diwicapw, ?12:17
apwbumping the abi12:18
=== amitk-afk is now known as amitk
diwicapw, sounds like an inspiration for a rap song? 12:36
apwdiwic, so very true12:42
=== smb-afk is now known as smb
smbdiwic, Could it be inspirational enough to have a quick look into the question I asked before? :-P12:51
diwicsmb, what question? Do you want me to repost the patch with a changed commit message?12:53
smbapw, Or stuck there for long on his way back should they find a "present" like that.12:53
smbreplay: diwic, Would you have an explanation on the feedback to bug 587546. It seems reported as the patch in proposed has no effect (must admit I have not looked really at details). 12:53
ubot2Launchpad bug 587546 in linux (Ubuntu Lucid) (and 3 other projects) "Pulseaudio fails after several seconds (affects: 1) (heat: 41)" [Low,Fix committed] https://launchpad.net/bugs/58754612:53
diwicsmb, okay, I'll have a look as soon as I've done with another bug12:56
smbdiwic, Thanks a lot12:56
ckingapw,  https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=ath9k&orderby=-importance13:10
mapetCan anyone tell me how I can add a custom version string to my kernel build, if I compile the official kernel with "debian/rules binary-generics"? I don't want it to be overwritten on each apt-get upgrade...13:29
=== ivoks-afk is now known as ivoks
apwmapet, normally I exit the top of the debian.master/changelog and use my own version there13:43
mapetapw, iirc this didn't worked for me but I'll try it again. thank you13:46
=== cking is now known as cking-afk
diwicIn average, how many days does it take from I send a patch to stable@kernel.org to that the Lucid users can enjoy their fixed bug?14:50
smbdiwic, That depends on quite a lot of variables to be giving a good average. How long from Greg accepting it to releasing it, how long from that till we get it into the archive and from that depends when its possible to upload to proposed and then how long it take to go to updates14:52
tgardnerdiwic, it can sometimes take weeks, which is why we often have a (pre-stable) inclusion.14:52
smbi guess a minimum can be at least three weeks on good days...14:53
smb(to get into updates)14:54
diwictgardner, so how long is our own baking cycle compared do that? 7 - 14 days? 14:54
tgardnerdiwic, roughly14:54
smbdiwic, yes. as upstream stable updates usually are larger rather the 14 days in proposed14:54
diwicso waiting say 5 - 7 weeks in total is not unusual?14:55
smbHopefully we can improve that a bit but at least it was14:55
smbBut i'd say 3 to 4 weeks could be common14:56
diwicright, the long security-blocking-sru discussion14:57
diwicHow do I know on what waiting list a stable patch actually is? 14:58
smbYes, that has some impact at least to the in the proposed to updates time. People can get patches quicker when installing at least proposed but even better pre-proposed14:58
smbdiwic, When it has been released in an upstream stable release you can check when that gets applied to the master repo. When it is in there it moves on to proposed uploads (which you probably could check with git describe --contains on our master repo)15:00
diwicsmb, someone should write up a wiki page on how to know where an update is15:03
=== cking-afk is now known as cking
diwicsmb, so my patch is currently present in stable-queue.git, queue-2.6.35 but not queue-2.6.3215:04
diwicThat's not good odds I assume15:04
smbdiwic, Someone probably should15:05
* smb looks innocent15:05
smbdiwic, And yes, that does not seem good15:05
smbdiwic, Could it have failed to apply cleanly there?15:06
smbIn that case Greg accepts bribes in form of backported patches15:06
diwicsmb, I gave him a 2.6.32 backport but was perhaps too late15:06
smbIt might just be pending another batch of applies from his inbox. Its hard to say15:07
diwicso after it has been in queue-2.6.xx for x days, it moves to another tree and is there for x days15:07
smbdiwic, He may or may not move it into review-2.6.xx in that repo and sends out review mails, gives people about three days to reply or not and then takes the set that is there after that and imports it into the various 2.6.x.y trees15:10
=== ivoks is now known as ivoks-afk
diwicsmb, and then it moves into ubuntu-lucid (e g)15:14
diwicsmb, and then to pre-proposed, then to proposed, then released15:16
smbdiwic, Right, so when it is released in the 2.6.32.y tree we pick it up prepare a patchset with it and do the usual tracking bug and quick review, then apply it to the repo and from there an automatic script picks up the checkins and creates the pre-proposed. The proposed uploads are more manual as they need to take into account whether there is something in proposed we want to go to updates first, or whether a security update comes in soon an15:18
smbd such. But at some point it gets uploaded to proposed15:18
smband then after about 2 weeks (if trere have been no regressions detected) it will get moved on15:19
vanhoofdiwic: this has been helpful for me (if you've not seen it): http://people.canonical.com/~ubuntu-archive/pending-sru.html15:20
smbdiwic, The upload itself also can get delayed as each package uploaded to the proposed pocket needs to be accepted manually by an sru team archive admin15:20
smbvanhoof, right this shows what bug reports are claimed to be fixed by a proposed upload. And red is a bad verification and green a good one15:21
smbblue is nobody cared (yet)15:21
=== ivoks-afk is now known as ivoks
smbThe sru team tries at least to have a certain percentage  of the bugs successfully verified and no regressions before moving it to updates, even if it has been there for the two weeks15:22
diwichow often does greg do a "review round"?15:24
smbdepends, sometimes every two weeks, sometimes it takes longer. Probably depends on the queue and his workload15:25
diwicvanhoof, thanks, it just shows the stuff in proposed, which has it's purpose. I'm trying to understand the patch flow (flowchart, anyone)? 15:26
smbdiwic, You know its the "new guys" job to fix the crap documentation of the old guys. ;-P15:27
diwicsmb, oh, I just became much older ;-)15:27
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting15:36
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting15:36
vanhoofsconklin: nooooooooooo15:57
* smb curses under his breath. tgardner could you fix a nomination for me please? bug 63811515:59
ubot2Launchpad bug 638115 in linux-backports-modules-2.6.32 (Ubuntu) "linux-backports-modules-wwan-2.6.32 fails to upgrade properly (affects: 1) (heat: 6)" [Low,Triaged] https://launchpad.net/bugs/63811515:59
tgardnersmb, done15:59
smbtgardner, thanks15:59
apwvanhoof, heh, thats written by a friend of mine16:02
vanhoofapw: I was hoping it was all a dream16:02
vanhoofapparently its not :)16:02
tgardnerapw, ogasawara: did you notice that gcc was uploaded _again_ ?16:20
ogasawaratgardner: wtf, again?16:21
tgardnerabout 30 minutes ago16:21
apwtgardner, thats 4.5 which version do we use ?16:21
tgardnerI thought it was 4.5.16:21
ogasawaraI though it was 4.416:21
tgardnerhmm, don't have a maverick machine handy.16:21
tgardnerogasawara, you're right. it is 4.416:22
apwyeah looks like its 4.4. we are using by default, so i think we are ok 16:23
apwtgardner, ogasawara, EXCEPT, 4.4 just got uploaded too16:24
apw10 mins ago16:25
tgardnerapw, thats what Mathias was referring to in the other channel16:25
tgardnerlooks like we should be OK16:26
ogasawarawell, I was thinking of doing another upload today anyways to make sure the -virtual deb sizes shrink back down16:27
tgardnerogasawara, you have any other patches you'rethinking of taking?16:27
ogasawaratgardner: the others on the ml which are mainly pre-stable patches16:28
tgardnerI guess that was a dumb question, huh?16:28
ogasawaratgardner: I'm also still hoping for to land so we can sneak that in before kernel freeze too16:29
tgardnerogasawara, Thursday, right? thas gonna be tight.16:29
ogasawaratgardner: yah, we'll have to see.16:30
ckinghrm, got this error on my server:16:35
cking[ 4655.729368] fwts: Corrupted page table at address 7fd769f1e60616:35
cking[ 4655.729466] PGD 129845067 PUD 139e43067 PMD 12f527067 PTE bff6463abff6423516:35
cking[ 4655.729625] Bad pagetable: 000d [#1] SMP 16:35
cking[ 4655.729695] last sysfs file: /sys/devices/pnp0/00:05/rtc/rtc0/wakealarm16:35
cking[ 4655.729796] CPU 0 16:35
ogasawaramanjo: do you think you're going be throwing any last minute patches my way re WD?16:36
tgardnercking, is it fwts detected that the page table is corrupted?16:36
ckingtgardner, it trips that warning from the kernel16:36
apwheh no it was simply the victim16:36
ckingdunno why as yet. Ah, it's repeatable.16:37
tgardnercking, well, thats the first step16:37
apwprobabally you are looking somewhere nasty ... but ick16:37
ckinghrm, only disassembling the DSDT16:37
vanhoofogasawara: i have 20 patches I'm planning to submit tomorrow at 11pm ET16:38
* vanhoof *hides*16:38
smbogasawara, I may be trying to pre-stable a little update that fixes a (not sure how minor) problem with /proc/<pid>/maps for you to decide. 16:38
* ogasawara slaps vanhoof16:38
tgardnervanhoof _better_ hide.16:38
* vanhoof is done w/ patches for maverick16:38
ogasawarasmb: ack16:38
vanhoofim glad i've not been slapped yet ;)16:38
tgardnervanhoof, thats apw's trick.16:39
apwogasawara, i think that vanhoof just said you can ignore anything from him from now on :)16:39
ogasawaracking: I wanted to ask you about bug 612741 which is linked to your kernel-maverick-bios-test-automation blueprint...16:40
ubot2Launchpad bug 612741 in acpi (Ubuntu) "uncommanded shutdown (affects: 1) (heat: 100)" [Medium,Incomplete] https://launchpad.net/bugs/61274116:40
ogasawaracking: the bug isn't exactly about the fwts itself, but rather a bug where you had them run the fwts16:40
ogasawaracking: did you really want that linked to the blueprint?  as it shows up as an open work item for you16:41
ckingogasawara, it should be removed16:41
ogasawaracking: cool, I'll remove it.16:41
ckingogasawara, you are too kind16:41
=== BenC___ is now known as BenC
bjfcking, i think i've fixed the issue with the daily iso building and it's building them now16:47
ckingbjf, thanks!16:47
=== yofel_ is now known as yofel
tgardnerogasawara, I'm looking at these powertop patches. the first one (at least) appears to be a backport.16:53
tgardnerah, guess Yong says tha in the into email16:53
ogasawaratgardner: yah, the first is upstream.  not sure about the status of the 2nd patch w/ regards to upstream.16:54
tgardnerogasawara, well, I'm making sure he got the backport right. it looks a bit different.16:54
ogasawaratgardner: he bodged the first attempt that's for sure16:54
tgardnerwhich is why I'm looking at it a bit closer16:55
tgardnerogasawara, the 2nd patch has all of the SATA statistics gathering done within the interrupt handler. I'm not sure that''ll land upstream intact.16:59
vanhoofapw: hew now :)17:01
apwvanhoof, can't hear you :)17:01
vanhoof /mode +v vanhoof17:01
smbogasawara, apw Ok, pushed my little contribution. Though I am not completely sure about its importance or effect 17:07
ogasawarasmb: looks reasonable enough and seems you've tested it works17:11
smbMostly. I think I was bad and tested before that it does not work right now and the change itself just repeats or reuses the changes from Linus for the rest.17:13
JFovanhoof, what goodies do you want in my slide deck for UHS?17:13
smbogasawara, And well a very similar change was used to get Xen working again on Hardy17:14
JFoI am outlining the general versus the private bug/group concept17:14
apwogasawara, are you aware of the thread "Final Maverick i830, i845g, i855 support" ... they are likely to be asking us to revert some patches17:15
ogasawaraapw: yep, was going to ping RAOF to get his final recommendation to drop the KMS disablement patches17:15
ogasawaraapw: but I think he might be traveling today17:15
apwogasawara, cool as long as you are aware i can go back to sleep17:15
vanhoofJFo: what do you mean17:19
JFoI'm building my slide deck for UHS17:20
JFois there any OEM team/ HWE stuff you want me to add?17:20
vanhoofJFo: well what are you talking about17:20
JFoI'm writing about the bug process17:20
JFoshould have said17:20
vanhoof"vanhoof quit being dense?"17:20
vanhoofJFo: bug process is not something that the OEM has to deal with, they file as normal, and i've put together a linking concept to track distro bugs17:22
JFoI left that bit out as I don't think it would be useful to them17:23
JFobasically I am proposing that, unless they have NDA or pre-announced hardware, that they use the general process17:24
vanhoofyeah thats a fair statement17:25
* tgardner spams ogasawara with more patch mail17:37
=== jsalisbury_ is now known as jsalisbury
=== jsalisbury is now known as jsalisbury_brb
kstaileygood day (or whenever)18:32
apwgood 'now'18:32
JFohi kstailey :)18:32
kstaileyhi jFo18:32
apwbug #56348118:32
ubot2Launchpad bug 563481 in linux (Ubuntu) "BUG: Bad page state in process soffice.bin pfn:111e42 (affects: 4) (dups: 1) (heat: 45)" [Undecided,Incomplete] https://launchpad.net/bugs/56348118:32
kstaileyI'm sure there are others.18:32
* smb wonders whether he saw that mails on the stable list18:33
JFokstailey, is that patch in stable?18:33
* JFo hasn't had the chance to look18:33
* kstailey checking18:33
smbMe neither18:33
ogasawarait didn't look like it was upstream yet18:33
ogasawaraso I assume it's not in stable18:33
apwkstailey, so are you looking for a test kernel with this patch in, ie, is this patch well tested yet?18:33
smbThe description soehow sounds like I saw it somewhere, but as long as it is not upstrream it won't go stable18:34
kstaileynow I am peeking at drivers/char/hpet.c in lxr18:34
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Maverick Kernel Version: 2.6.35 || Ubuntu Kernel Team Meeting - September-28 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
smbSeems that mail went to linux-acpi a month ago. But I don't seem to see a response18:36
kstaileyit's not here http://lxr.linux.no/#linux+v2.6.35.4/drivers/char/hpet.c#L97218:36
kstaileybut maybe it should be18:38
kstaileyI may have some more HP Proliant DL145 G2 systems to test on18:39
JFoI apologize, but I need food :)18:40
kstaileyI'm going to look for a server to test the patch on.18:42
smbHm, it looks like this is a proposal to handle a bios bug. Might need some query upstream to get it moving probably18:42
kstaileyThe system we experienced this bug on is deployed by using the "nopat" kernel option in grub18:42
kstaileyas a work-around18:43
apwkstailey, you good to make a test kernel ?18:45
kstaileyI'm still looking for a machine to test on18:50
kstaileyIs it OK to test on Lucid or are you particular about me testing on Maverick? 18:50
kstaileyI'd rather test on Lucid myself18:50
smbWell it seems it would be the same upstream18:50
smbYou may try some of the more recent mainline kernels in lucid to compare against18:51
kstaileywell first thing's first let me get my server18:51
smbIts a bit latish here to get my head around it now. The patch itself looks at least reasonable to me but I wonder why there has been no response upstream to it18:52
kstaileyI'm also going to peek at RHEL6 to if Red Hat is workong on this18:55
vanhoofkstailey: http://rhkernel.org/RHEL618:58
sconklinthanks everyone for your support in the Developer Board meeting19:08
tgardnersconklin, like smb said, it'll be nice to not have to do your job :)19:10
ogasawarajjohansen: you'd mentioned you were planning to submit some Maverick patches?  any eta for those?19:12
jjohansenogasawara: yeah, sorry I'll post them today.  They are done.  I just need to get them pushed out19:13
ogasawarajjohansen: ack19:13
jjohansenthat and I have been testing the amazon one19:13
=== jsalisbury_brb is now known as jsalisbury
ogasawaratgardner: that first power top patch you re-did for yong, it doesn't look like the rtpm_status_show() originates from 8d4b9d1bfef117862a2889dec4dac227068544c919:47
tgardner oguh, lemme look19:50
tgardnerogasawara, ^^19:50
tgardnerogasawara, hmm, what was I smoking? Did I get confused because he added it?19:52
ogasawaratgardner: it actually looks like his patch removed it?19:52
tgardnerogasawara, ok, now I'm totally confused. lemma go back and repeat what I did.19:53
ogasawaratgardner: I have a feeling yong isn't using our maverick repo19:53
tgardnerogasawara, no, likely its the Linaro repo19:54
tgardnerogasawara, ok, you cherry-pick it and see if you get anything different.19:57
ogasawaratgardner: ack19:57
ogasawaratgardner: if we cherry-pick 0fcb4eef8294492c8f1de8236b1ed81f09e42922 first, then 8d4b9d1bfef117862a2889dec4dac227068544c9 cherry-picks cleanly20:05
tgardnerogasawara, I only had minor, seemingly innocuous conflicts. huh. I guess I missed the dependency.20:05
ogasawaratgardner: 0fcb4eef8294492c8f1de8236b1ed81f09e42922 seems to fix up rtpm_status_show that we currently have in Maverick20:06
tgardnerogasawara, ok, well lets go that route. clean cherry-picks...20:07
ogasawaratgardner: ack, will respond to the list that I've gone the clean cherry-pick route20:07
=== ivoks is now known as ivoks-afk
sconklinogasawara: I'm only aware of one open work item that I had, does that match your reality?21:21
ogasawarasconklin: yep21:21
sconklinok, I just postponed it.21:22
ogasawarasconklin: cool, thanks21:22
sconklinI'm not sure it's needed so much, Need to ask RAOF21:22
* ogasawara lunch21:41
* tgardner has brcm80211 working in natty. seems to connect OK, but borks on removal.21:42
=== mdeslaur_ is now known as mdeslaur
DoYouKnowHi. Anyone know if/when BCM4328 development support will be included in the kernel, or if it can be enabled in maverick?22:44
kstailey@DoYouKnow wrt Broadcom have you seen this http://thread.gmane.org/gmane.linux.kernel.wireless.general/5541823:11
ilmariI had a quick look a that and couldn't find anything about BCM4328 support there (I have that chip in my work laptop)23:12
kstaileyyou didn't read the entire thread23:12
ilmariI did23:15
ilmarinothing about 4328 there, only 4329 and some other chipsets23:15
ilmariwhen I said "at that" I meant the driver source itself23:17
=== emma_ is now known as emma

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