/srv/irclogs.ubuntu.com/2010/05/25/#ubuntu-kernel.txt

keesogasawara: is aufs supposed to work in the .34 kernels?00:03
ogasawarakees: I'd assume it should, we haven't touched it00:03
keesogasawara: hrm, it is misbehaving.  I will dig further and file an actual bug report.  :)00:04
ogasawarakees: thanks. can you ping me or JFo with the bug # once you have it.00:05
* kees has to figure out how to use it in a non-schroot context first. :)00:05
* bjf taking off for a bit00:06
keesjjohansen: (from the other channel) yeah, aufs is in there, and it seems that manual usage works.  schroot doing it results in weird states... /me tries some more00:17
jjohansenkees: yeah I know aufs is there, /me just wasn't sure if it needed updating to have it work properly on .3400:18
kees# umount /var/lib/schroot/mount/maverick-i386-58acab8c-28d3-4044-994a-403cc650acc000:18
keesumount: /var/lib/schroot/mount/maverick-i386-58acab8c-28d3-4044-994a-403cc650acc0: device is busy.00:18
keesfuser says:00:18
kees                     USER        PID ACCESS COMMAND00:18
kees/var/lib/schroot/mount/maverick-i386-58acab8c-28d3-4044-994a-403cc650acc0:00:18
kees                     root     kernel mount /var/lib/schroot/mount/maverick-i386-58acab8c-28d3-4044-994a-403cc650acc000:19
keesno clue what that's about.00:19
vanhoofJFo: yo00:19
vanhoofback now00:19
vanhoofJFo: on that bug, you looking for a home for it?00:19
keesOH... getting kernel Oops.  hah.00:20
kees[  360.979217] kernel BUG at /build/buildd/linux-2.6.34/ubuntu/aufs/f_op.c:84!00:20
jjohansenkees: sadly not surprising00:23
keesjjohansen: and aufs isn't upstream, right?00:23
jjohansencorrect00:23
jjohansenand it never will be00:23
jjohansenkees: that is one of the reasons we are reevaluating union mounts this cycle00:25
jjohansenthey look like they might finally go upstream soon00:25
keesright, cool.  in the meantime, I've filed bug 58517500:26
ubot2Launchpad bug 585175 in linux (Ubuntu) "kernel BUG at /build/buildd/linux-2.6.34/ubuntu/aufs/f_op.c:84! (affects: 1)" [Undecided,New] https://launchpad.net/bugs/58517500:26
=== kamal is now known as kamal-away
lagMorning :)07:03
cooloneylag: good morning07:20
lagcooloney: Hi ya07:20
* apw waves08:31
apwsmb, morning08:33
amitkmorning gentemen08:33
smbapw, Morning08:33
smbamitk, dito08:34
apwmoin amitk 08:34
ckingmorning08:34
ikepanhcgood morning .eu08:34
smbcking, Youare required to log in to mumble08:34
apwmoin .ap08:34
ckingsmb, ok - firing up08:35
lagMorning everyone08:35
jk-hey peeps08:35
jk-cnd: how come your mumble icons (muted & deafened) have blue crosses instead of red ones?08:44
jk-oh, muted & deafened by the server?08:45
apwjk-, muted by me instead08:48
jk-ah08:48
ikepanhceh, is there any update on mumble server?08:55
apwikepanhc, shoul 08:55
apws08:55
apwikepanhc, should be working08:55
ikepanhcapw: server tells me wrong password..08:56
apwikepanhc, the username is changed to be your launchpad accounts email address08:56
apwnote i said email address08:56
ikepanhcapw: trying, thanks08:56
cooloneysmb: just sent you an email for omap4 branch in lucid09:00
smbcooloney, No, actually you sent ogasawara that mail. I am not looking at things without a release in the topic that I care09:01
smbcooloney, Darn09:01
smbYou had it at the end. I am not reading that far at that time of the day09:02
cooloneysmb: i did not send git pull email to ogasawara 09:03
cooloneysmb: i think amitk sent that for adding omap flavor in Maverick09:03
cooloneysmb: but mine is for adding omap4 branch in Lucid09:03
smbcooloney, I was just bitching about not having a [Lucid][pull request]09:04
smbcooloney, Is that a new topic branch or should replace the current ti-omap?09:04
cooloneysmb: ok, next time i will take care of that.09:04
cooloneysmb: oh, it is a new branch 09:04
cooloneysmb: won't replace ti-omap09:05
* apw watches smb cry09:05
* smb looks for something to strangle cooloney 09:05
apwcooloney, whats its base version ?09:05
smb.33 it seems09:05
cooloneysince ti-omap for omap3 machine09:05
cooloneyyeah, .3309:05
cooloneyapw: ^^09:05
amitkcooloney: call it ti-omap4 (or something)09:05
smbamitk, he has09:05
cooloneyyeah, it is ti-omap409:06
apwwas ti-omap a .33 kernel too ?09:06
amitkyes09:06
smbamitk, Just that I am so very happy to take in yet another topic branch that needs care09:06
cooloneyrihgt.09:06
apwsmb, you can't take it till someone handles the MIR09:06
amitksmb: I'm sure you are (Father Hen counting his chickens)09:06
apwand the FFE, and all the other paperwork09:06
smbcooloney, amitk Can't you guys get one tree per manufacturer09:06
amitksmb: someday (hopefully before I lose all my hair)09:07
cooloneysmb: it is difficult. so we created 2 branches09:07
cooloneyeven ti has 2 different git tree09:08
smbcooloney, It is difficult to manage so maybe I just not take it...09:08
apwjust because they cannot maintain a tree doesn't make it right09:08
amitkapw: they're working on it, we expect to have a single tree for M+1 for TI09:09
amitkand with luck, it will all be in 'master'09:09
cooloneyright.09:09
cooloneyas amitk said, we are going to make M has omap flavor in master branch09:10
cooloneyand omap4 branch for those patches from ti but not in mainlien09:10
cooloneybut for lucid, i do think we can put them together easily09:11
cooloneyi don't think, sorry09:11
cooloneysmb: this lucid omap4 branch is for TI 10.07 release.09:11
amitksmb: it only has to be supported until Jan09:12
cooloneybecause of the time frame, i picked up our lucid code base for that release09:12
smbcooloney, amitk I am _very_ reluctant about adding anything to the official repo just based on a pull request09:13
* apw wonders if amitk knows quite how far away january is09:13
cooloneyapw: yeah, it is july09:14
amitksmb: apw: Perhaps, this isn't very clear, but cooloney doesn't want you to spin new kernels, the binary packages will be done in a PPA. He just wants the git tree in a single place.09:14
amitk(in a branch)09:14
cooloneyamitk: right, that's point09:15
smbamitk, Well it will be in the repo. And we were given trees like that before and suddenly there is need to put in security fixes and other generic fixes. And so it is suddenly a bunch of additional work09:15
smbamitk, cooloney So I want something more official than just "here, pull it"09:16
amitkok09:16
amitkcooloney: ask davidm to send email to u-k mailing list outlining the support requirements for this tree (which should be none)09:17
cooloneyamitk: ok, looks like i don't have any other choice, -:|09:18
apwamitk, what is the support requirement on ti-omap itself ?09:26
amitkapw: I'd like to say "standard release - 18months", but you should confirm with davidm09:30
amitk10.07 is a special release for TI, so they can ship ubuntu on their new HW. And we throw it away once omap4 is a first class citizen in maverick.09:31
smbamitk, I hope you are aware that ti-omap currently will receive no stable updates. I have no common base for that and I do not apply .33 patches09:35
cooloneyapw and smb, i have to say the ti-omap4 is very special, so I would talk to guys eariler about that.09:35
smbcooloney, That would have been a good idea09:36
amitksmb: understood09:40
lagWho is responsible for the filesystem in Ubuntu? 10:16
cooloneylag: i guess it surhbi's area? but she is sick today.10:20
lagcooloney: Thanks. 10:20
=== permalac is now known as marcriera
apwsmb that is the range right: 332d90de3fa1254dd49c71882e407a169efddb9e..8eb93181b49f13e241970c358be254d4df9c241910:42
apwLinux-2.6.32.11+drm33.2 -> Linux 2.6.32.12+drm33.310:44
smbc4176d0557f28a68846aa7de10197aed3d5f78a2..8eb93181b49f13e241970c358be254d4df9c241910:44
smbapw, You want to start were I branched10:44
smbapw, That stable branch is based on last released lucid and has other things since then10:45
apw183, phew that sounds better <- smb10:45
smbapw, Right, given that there are quite a few patches skipped compared to upstream (or replaced)10:47
smbapw, Note, that I currently skipped the EC changes as we still have a slightly different approach there10:48
apwok10:48
=== smb is now known as smb-afk
lagWhat are the different numbers called in linux version? I.e. 2.6.32-21.1 11:00
lagSomething like this perhaps? "version.series.release-abi-minor-flavour"11:09
ikepanhccooloney: do you know we shall use -march=armv7a or -march=armv7-a on lucid fsl-imx51 kernel?11:18
ikepanhcseems cross compiler use v7-a...11:19
ikepanhcbut I dont know how about the native compiler11:19
cooloney-march=armv7-a when i'm doing cross compiling11:21
ikepanhcand armv7a for native compiler?11:21
cooloneyi never try on native compiler11:22
ikepanhcI mean build server11:22
cooloneyright, i think it is the same11:23
cooloneyarch/arm/Makefile11:23
cooloneyarch-$(CONFIG_CPU_32v7)         :=-D__LINUX_ARM_ARCH__=7 $(call cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)11:23
cooloneythe CFLAGS is set in kernel Makefile11:23
ikepanhcso, we shall use v7-a, not v7a?11:24
cooloneyyeah, v7-a not v7a11:24
ikepanhcoh, I saw that, a freescale patch modify it. so I need to revert it, thanks11:25
cooloneycool. i almost remember that patch, they wanna compile the kernel with old toolchain. 11:26
cooloneyso they modified that, 11:26
ikepanhcya, that's it11:27
lagamitk: Is there a better way to push local/branch -> remote/branch than "git push <remote> HEAD" when the remote branch is currently checked out?12:07
amitklag: is the remote tree on zinc?12:08
lagNo, it's on a build-server12:08
lagAnd has a working tree12:08
amitklag: I assume you have ssh access to that machine12:09
lagWhen I do "git push <remote> HEAD", I receive a warning about the branch being checked out and I have to do a reset followed by a checkout on each of the remote branches12:09
lagYes12:09
amitkin which case, have you setup you .git/config to push using ssh?12:10
lagIf that's the way to do it, then fine. I just thought there may be a better way12:10
amitk[remote "zinc"] url = ssh://amitk@zinc.ubuntu.com/srv/kernel.ubuntu.com/git/amitk/maverick.git12:10
lagYes, I've done that12:10
lagThat's how my push works12:10
amitkok12:10
amitkgit push <branch name> should work12:10
lagIt's happy to do it, but because the branch is checked out on the remote server (as that's where I'm building), it complains 12:11
lagOkay, I'll give it a go12:11
lagSounds simple enough12:11
amitkperhaps I haven't understood the real problem, re-reading...12:12
lagSame warning12:14
lagwarning: updating the current branch12:14
lagwarning: Updating the currently checked out branch may cause confusion,12:14
lagwarning: as the index and work tree do not reflect changes that are in HEAD.12:14
lagwarning: As a result, you may see the changes you just pushed into it12:14
lagwarning: reverted when you run 'git diff' over there, and you may want12:14
lagwarning: to run 'git reset --hard' before starting to work to recover.12:14
hrwhi12:14
ograjust use bzr 12:14
* ogra hides12:14
hrwogra: ;d12:15
ograhmm, was possibly not the best idea to make a bad joke right before asking the kernel team for a favour :P12:15
ograso hrw and me are here to make a feature request ... 12:16
amitklag: hmm, never see that12:16
ograwe would like to autospawn a getty on serial consoles if console=ttyS,... is set12:16
amitkogra: Denied!12:16
ografor that hrw created an upstrat script we showed Keybuk for possible upstart upstream inclusion12:16
* abogani waves12:17
aboganiPlease don't forget me https://lists.ubuntu.com/archives/kernel-team/2010-May/010707.html :-)12:17
hrwogra forgot to mention that enabling of autogetty has to be done by user first12:17
lagamitk: Do you use build servers?12:17
* amitk points ogra, hrw to apw, ogasawara 12:17
amitklag: on occassion12:17
lagI edit on my local machine, then push to my remote one (on the build server)12:18
ograduring discussion Keybuk pointed out that the script would better operate on a kernel event i.e. in a way that you can use "start on" if the actual device is existent 12:18
amitkogra: possibly best to write email to the mail list12:18
ogracurrently the kernel doesnt expose such an event and we would need it to be added12:18
ograamitk, hmm, yeah, probably better12:18
amitklag: I only use bare repos to push stuff to12:20
amitklag: never done it with a 'checked-out' repo on the remote side12:20
lagOkay12:21
lagI think here lies my problem :)12:21
amitklag: you could setup a bare repo to push to and then clone it and checkout12:21
apwlag, whats the issue?  i use non-bare upstreams commonly to build in12:22
Keybukogra: not expose an event so much, as expose the value of console= ;-)12:22
ograKeybuk, indeed 12:22
Keybukwe have the events anyway, we just don't know whether or not ttyS0 is the console12:22
ograbut you wanted an even too for "start on", no ? 12:22
Keybukwe have the event12:22
ograah, k12:22
Keybukwe want the "is ttyS0 the console" test in a form that is useful12:22
Keybukeither as a payload to the event12:23
lagapw: Look up12:23
Keybukor $console as environment variables or command-line arguments to init12:23
ograKeybuk, note that a serial console can have pleanty of names :)12:23
ograthe only indicator we have is that its not tty[0-9]12:23
apwlag, all it says is you push and build ... what am i to make from that, other than good12:23
ograeverything with a letter is serial12:23
persiaBut not everything that is serial is a console12:25
hrwyep12:25
ograpersia, i think we can safely assume that everything added to the console= cmdline option is a console ;)12:25
persiaFair :)12:26
lagapw: When I push it complains12:26
apwdid you read the complaint ?12:26
apwand take the action it proscribed ?12:26
ograso we want both, the event (as Keybuk says that already exists) and handing over console= to upstart12:27
apwif you set the thing it whines about to ignore, then you can do it12:27
ograthe prob here is that you will likely have multiple console= args 12:27
lagapw: It says that as the remote branch is checked out there will be issues12:28
apwlag, as we discussed you have to push, then git checkout -f branch on the remote side before building12:28
apwthe 'issue' is the head and the working tree will not match12:28
lagapw: When I do the push, I have to do a 'git reset' and 'git checkout <file>' for it to act sane again12:28
apwthe fix is to check it out12:28
apwyou should just have to git checkout -f <branch>12:29
lagEvery time?12:29
apwevery single time you push yes12:29
lagThat's annoying!12:29
apwremember the push stuff is repository level12:29
apwthe working directory is not there12:29
apwand not synced, hence the whine12:29
apwbut as you have to go to the copy to compile it you can simply make it part of your tooling12:29
lagOkay12:29
apwboth smb and my tooling do that12:29
amitkkteam-tools?12:30
lagThey do, but I'm not building just yet12:30
=== smb-afk is now known as smb
lagAs long as that's the definitive answer, I'm happy12:31
* smb sees a lot of stuff in the srollback12:31
smblag, apw I am not sure I could catch the problem and the answer exactly when skipping through the scrollback12:34
smblag, Is it the complaint about pushing to a checked out branch?12:34
lagsmb: Correct12:34
apwyep12:34
lagsmb: I've been educated by apw to do a 'git checkout -f' on the remote to solve12:35
apwyou need a new variable set.  once set you already do the right thing by checking out -f 12:35
smblag, Ah yeah, so at the moment its a warning. Or you do what it tells you and set the variable12:35
smbLong term the scripts should do that12:35
smbOh, it changed to an error with lucids version of git?12:35
lagIt's just a warning with mine12:37
smbI believe the rune on the remote side was "git config receive.denyCurrentbranch ignore"12:37
lag[receive]12:38
lagdenyCurrentbranch = ignore12:38
smbSo that is now set12:39
lagYup :)12:39
amitkapw: was there a W-I for the omap-mainline kernel for maverick?12:52
apwnot that i've seen though there should be12:52
amitkapw: it should probably be 2-3 W-I (given it wasn't a 2hr job)12:53
apwa work item is meant to be a 2-3 day effort, but if you need one thats smaller then you need it, if it bigger then it should be split a bit12:55
amitkapw: aah, for some reason i thought it was a 2-4hr effort12:57
amitkwhere should it be added?12:58
amitkwhat spec, I mean12:58
apwits a new flavour right?  we discussed those on config-review i think, the remove -preempt should be on it12:59
amitknew flavour, yes13:00
persiaRemove -preempt?  I thought the plan was only to split out -preempt into a separate package.13:14
cndsmb: care to unmute and undeafen me?13:27
* ogra wonders why his touchbook kernel has a mailbox13:52
ograis that an addition to the in kernel httpd ? :)13:52
ograoh, hm, "interrupt driven messaging"13:55
amitkogra: are you referring to omap mailbox?13:58
ograyeah, never heard of it 13:59
ograi just saw the module in lsmod :)13:59
amitkamong other things it is used by the dspbridge13:59
aboganiDo you have some thought about https://lists.ubuntu.com/archives/kernel-team/2010-May/010707.html ?14:01
apwabogani, not had a chance to look at it yet.  doing stable reviews first14:10
aboganiapw: Ok. Thanks in advance.14:10
* JFo yawns14:10
pgranerJFo: yea keep yawning while you blow up my imap server... dude seriously?14:19
JFo:-D14:19
* JFo has more mail for you today oh captain, my captain!14:19
pgranerJFo: good thing this ain't like the the postoffice where you get charged by the piece....14:20
JFoindeed :-/14:20
JFoi can't imagine what the bill would be for all of this14:20
JFobut I know i wouldn't want to pay it14:20
JFo:014:20
tgardnerJFo, are you filling my bug box? I haven't checked this AM yet14:21
JFotgardner, I am14:21
JFoi am spreading the love to all with my bug expiration mails14:21
pgranertgardner: hope you have a fast connection to your mail server, he hit me with over 1k messages in bug spam14:21
JFoand that is just for the expiring ones :)14:21
tgardnermaybe thats why it felt so slow earlier this morning. it took forever to get my inbox stuff.14:22
pgranerJFo: you have my fetchmail process breathing hard, its never done that much work14:22
JFoheh14:22
JFoso pgraner, looks like I had the wrong objectives but alice has fixed them.14:24
JFothey need your sign off so I can fix them up14:24
pgranerJFo: ok give me 514:26
JFok, thanks14:27
JFoapw, in the grand tagging scheme, where would bug 324894 fit14:37
ubot2Launchpad bug 324894 in linux (Ubuntu) ""Corrupted low memory at" kernel warning on resume (affects: 25) (dups: 6) (heat: 188)" [Medium,Triaged] https://launchpad.net/bugs/32489414:37
JFojust wondering whenever you have time to look14:38
JFomy money is on acpi maybe14:38
manjoJFo, that bug can be quirked, but they need to send me the dmidecode info14:38
manjothe quirk is in the core kernel 14:38
JFowhich manjo ?14:38
JFothe one here or some other?14:38
manjojfo Corrupted low memory at14:38
JFoah14:38
manjoJFo,  Corrupted low memory at14:38
=== permalac is now known as marcriera
=== marcriera is now known as permalac_
apwJFo, i would put it in kernel-core .. its biosy ick14:40
=== permalac_ is now known as permalac
apwwhat manjo said14:40
manjoJFo, this one is a diff one from what I was looking at, but basically the same bug, like apw said bios issues, quirk is in the kernel 14:41
smbapw, Dude, I wonder who is madder of the two of us. You doing all the 180 plus writing or me. But thanks! :)14:41
JFoapw, k14:41
apwsmb, you made the t-shirt, who looked madder there ... i think its a draw14:41
apwsmb, i need a lie down i thkink14:42
smbapw, It surely is. And yes I think you would have earned it14:42
JFovanhoof, yeah, I need a home for it14:47
amitkmpoirier: you have new booogs assigned to you14:52
mpoirieryes, just saw - thanks14:52
amitkmpoirier: were you able to run my kernel?14:54
mpoirierindeed but your .deb died in userspace.14:54
mpoirierit could find the sd card.14:54
mpoirierI check-out your tree14:54
mpoirierrecompiled and it all worked properly.14:54
mpoirieri did not look for specific bugs/error14:55
amitkok14:57
JFolook out for all the boogs!!!14:58
* JFo goes for coffee to escape the boogs14:58
* cking wrestles with evolutions junk filters15:26
amitkogasawara: will there be any more uploads before alpha-1, or just the one?15:40
tgardneramitk, I was gonna ask her why she hasn't already uploaded. there are a pile of changes in  the pipe15:42
smbapw, Hm I guess you have done ti-omap and qcm-msm uploads sort of recently. Should ti-omap have a orig.tar.gz?15:43
amitktgardner: I see that you'll press her to do it. My job here is done :)15:44
tgardneramitk, yeah, I'll annoy her when she shows up this morning.15:45
smbapw, Probably could only be a raw linus-2.6.33 tarball15:45
apwsmb, it should have had one, though i have the feeling i was remis in providing that one15:45
smbapw, There is nothing on archive.ubuntu.com, but so I try whether it works with one15:46
bjfmoin all15:48
apwsmb, you can inject one at any time15:50
apwbjf, moin15:50
smbapw, Yeah, just sometimes the build explodes when you do it cause they need executable things or ...15:51
smbbut I will try15:51
* smb grows several new gray hairs over the lucid rebase mess15:54
apwsmb, i see, i think ti-omap is mostly upstream so the risk is lower than normal for an ARM nightmare branch15:57
smbapw, Its mostly keeping 3 kernel versions and 6 topic branches somehow in memory without getting too confused15:58
ogasawaraamitk: was planning to upload this morning, just had one extra question for you before I do15:58
apwyeah i have a checklist15:58
ogasawaraamitk: you mentioned you purposely didn't run updateconfigs after doing the -omap flavour15:59
ogasawaraamitk: I'm gonna have to run updateconfigs for other bits when I rebase, do you prefer that -omap config not be touched?16:00
tgardnerogasawara, what I think he meant is that it will be easier for you to do it at the time of integration16:00
smbapw, Mine is still brain based. That sort of worked before Lucid but I think this needs some external list now...16:00
apwsmb, ogasawara, the checklist i used for lucid development is on chinstrap in ~apw/CHECKLIST16:01
apwyou can see the form i used16:01
ogasawaraapw: thanks16:02
apwsmb, though if you put that together with all the releases on it you may kill self16:02
smbapw, thanks. I will try anyway. Better that than try to keep all in mind16:03
bjf##16:05
bjf## Kernel team meeting today @ 17:00 UTC16:05
bjf##16:05
bjfJFo, didn't see as many expired emails as I was expecting16:06
JFoyeah, the script fell over on one16:07
JFobut I am running it again so I can see what happens16:07
JFomore expring now16:07
=== permalac is now known as marcriera
bjfogasawara, do you have a list of active blueprints that we should be reviewing in the irc meeting?16:10
ogasawarabjf: primarily this is what I'm using for Alpha1 https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone maverick-alpha-116:10
bjfogasawara, that's quite the list, i'll work on getting it into the meeting16:12
ogasawarabjf: I was gonna mention it during the Maverick Release Status16:13
ogasawarabjf: and remind those who still have open items16:13
bjfogasawara, so you want to do them all as a single meeting topic or do you want me to break them out as one blueprint per topic like before?16:14
ogasawarabjf: actually, one blueprint topic like before might be good for accountability16:15
bjfogasawara, i'll work on that now16:15
ogasawarabjf: thanks16:15
ogasawarasmb: just a heads up, the security-m-kernel-hardening blueprint had a work item of "review and consider security hardening patches for Stable Releases" but it was assigned to canonical-kernel-team16:29
ogasawarasmb: so I reassigned to you specifically else it'd likely get ignored16:29
smbogasawara, Ok, thanks. I saw it in the mail lp sent out when you changed it16:30
ogasawarasmb: it's currently an Alpha1 work item, but feel free to bump to Alpha2 if you haven't time to review before Alpha116:30
ogasawarasmb: I realize I sorta dumped it to you last minute16:30
smbogasawara, Remind me when is alpha1? something june?16:31
ogasawarasmb: next Thurs, june 116:31
smbogasawara, joy. :-P16:31
JFowhat the heck is pwmconfig? bug 47564116:31
ubot2Launchpad bug 475641 in linux (Ubuntu) "pwmconfig does not work after upgrade to 9.10 on TYAN server (affects: 2) (heat: 12)" [Undecided,Triaged] https://launchpad.net/bugs/47564116:31
tgardnerogasawara, I'm currently looking at the ptrace hack from kees16:32
ogasawarasmb: make that June 3, not june 116:32
bjfJFo, power management config16:32
JFoah hah16:32
ogasawaratgardner: any thoughts yet?16:32
JFoI was hoping it was that16:32
smbogasawara, two more day then :)16:32
tgardnernah, still have to noodle around with it. I'll get to it this afternoon16:32
JFothat the bug from last night tgardner?16:33
tgardnerJFo, dunno. what bug?16:33
smbtgardner, let me know what you think, too. Somehow I remember two were sort of ok'ish and one was scary16:33
JFobug 58517516:33
ubot2Launchpad bug 585175 in linux (Ubuntu) "kernel BUG at /build/buildd/linux-2.6.34/ubuntu/aufs/f_op.c:84! (affects: 1) (heat: 6)" [Undecided,Triaged] https://launchpad.net/bugs/58517516:33
tgardnersmb, I've already reviewd and ack'd the first 216:33
JFoogasawara, ^^ that is the one kees filed last night16:33
smbtgardner, Cannot remember which one was which. But I think the hardlink thing was something scary16:34
tgardnersmb, hardlink/softlink was straightforward and testable16:34
smbtgardner, Hm from my memory hardlink might have some side effects. But testable could be16:35
tgardnerJFo, different bug16:35
ogasawaraJFo: can I add that to our 50 to review/discuss?  I know there is a new aufs we can update to but we're holding off on it till we finish the union mounts evaluation as an alternative to aufs16:35
JFoogasawara, you may indeed16:35
* JFo makes a note16:35
ogasawaraJFo: not that I'm sure the newer aufs would resolve it...16:35
tgardnerit'll just add new and different bugs16:36
JFoogasawara, it is on my paper list to add16:36
ogasawaraJFo: I'm still cleaning up the KernelBuglist script, I keep getting side tracked16:36
JFok, no sweat16:36
JFotoo much to do16:36
bjf##16:37
bjf## Kernel team meeting in 25 minutes16:37
bjf##16:37
* tgardner wonders what timezone in which bjf exists16:38
tgardnerbjf, never mind. can't read16:38
smbHm 17UTC is a bit more than 25 mins away in my world16:39
bjfsmb, according to my 'puter it will be 5:00 p.m. in london in 22 minutes, is that not 17:00 utc?16:40
smbbjf, no london has daylight savings too16:41
bjfsmb, they switched to BST didn't they16:41
bjfso that would be in 1 hr and 20 minutes then16:41
smbyep I think so16:41
smbcking, apw ?16:41
ogasawara$ date --utc16:42
ogasawaraTue May 25 15:40:32 UTC 201016:42
ogasawaraI'm seeing 1hr 20min16:42
bjf##16:42
bjf## Kernel team meeting in 1 hour and 20 minutes  (time correction)16:42
bjf##16:42
apwbjf, do you have the list of blueprints you will be asking about yet as the agenda just has the 'NEEDS LIST' in it16:42
bjfapw, working on it, will update in 3 minutes16:43
JFoI have a list of them bjf16:44
bjfJFo, me too, i'll put mine on the meeting page and we can compare notes16:45
JFoah16:45
JFojust blasted them to you in pw :-/16:45
JFowill check the meeting page16:45
amitkogasawara: what tgardner said (regarding updateconfigs). Run it now that the patch is integrated.16:46
ogasawaraamitk: ack16:46
tgardnerapw, what was the reasoning for creating a new PPA for the LTS backports? Whats wrong with just using the well known kernel-ppa ?16:50
apwtgardner, none if that PPA is not being used for anything16:51
bjfapw, ogasawara, JFo, blueprint list on meeting page, let me know if you want more added, i just put on the ones with A-1 deliverables16:51
JFok16:51
apwnominally i would use a named PPA for such a specific thing though16:51
tgardneracht pht16:52
lagDoes anyone know what this means: <directory>/*[!~]16:53
bjflag, context?16:54
lagbash16:54
lag* = everything16:54
lagDon't know what [!~] means16:54
tgardnernot $HOME ?16:54
lagNot home?16:54
lagDoh!16:54
smbdepends on how regex bash is. I thought there were limits16:55
smbMaybe only something ending with ! or ~16:55
lagIt's actually /etc/pm/config.d/*[!~]16:56
manjoIf the first character following the ‘[’ is a ‘!’ or a ‘^’ then any character not enclosed is matched16:56
blue_annacan I get help getting i2c-core module for my build? it's not in my kernel and I don't see an alternative in the repositories16:56
tgardnerlag, um, I think that matches all files except those ending in '~'16:56
lagThat could work16:57
manjolag, If the first character following the ‘[’ is a ‘!’ or a ‘^’ then any character not enclosed is matched16:57
lagmanjo: ack16:58
lagThanks :)16:58
JFoapw, did we say KMS was core or graphics?16:58
=== kamal-away is now known as kamal
* JFo is in forgettory mode16:59
keestgardner: if there's anything I can help with for the ptrace review, please let me know.16:59
tgardnerkees, ack16:59
bjfapw, ogasawara, JFo, adding more BPs to the agenda, just a sec16:59
bjfapw, ogasawara, JFo, meeting agenda updated let me know if you want changes17:01
JFok17:01
JFoapw, nm I think that was KVM I was thinking of17:01
smbJFo, KVM as in the virtualization engine?17:03
apwJFo, KMS kernel-graphics, KVM kernel-core yea17:03
JFoyeah17:04
JFothat was it17:04
JFoI was getting them tangled17:04
smbapw, Wasnt there a KSM too17:04
* JFo slaps smb17:04
JFo:)17:04
apwheh maybe17:04
smbHey I am only the messenger :-P17:04
JFo:-D17:04
* smb thinks of something with shared memory17:04
* JFo puts an action item to continue updating the Kernel Dictionary17:05
bjfJFo, manjo, jjohansen, apw, tgardner, cnd, ogasawara, cking, smb, just a heads up, you are on todays meeting agenda for a blueprint17:08
jjohansenbjf: yep thanks17:09
apwbjf, ack ... am prepared17:09
tgardnerbjf, INPROGRESS17:09
bjf:-)17:09
jjohansenapw: why wouldn't all the items on my blueprints be showing up in https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick17:10
smbbjf, I did not see me on a complete blueprint but as subitems. apw Ithing in yours (misc)17:10
apwjjohansen, which blueprint17:10
bjfsmb, sorry, your on for the usual reason :-)17:10
apwsmb, he prolly means for the stable update17:10
bjfsmb, we just love ya man!17:10
apwjjohansen, there are many reasons, easiest to look at the source of the blueprint17:11
smbheh, thanks a lot17:11
jjohansenhttps://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel17:11
jjohansenhttps://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor17:11
jjohansenhttps://blueprints.launchpad.net/ubuntu/+spec/security-m-apparmor17:11
jjohansenhttps://blueprints.launchpad.net/ubuntu/+spec/security-m-apparmor-profile-packaging17:11
jjohansenapw: okay, what am I looking for, some of the items are there, and some of the items there aren't reflecting status changes that were made friday17:11
apwok the DB was last updated my end about an hour ago17:12
* bjf notes it's going to be a balmy 60 degrees F today in Portland (and rain _all_ day)17:13
jjohansenokay, so I will assume I broke the work item format, and check all those17:13
apwpvops looks ok17:13
apwjjohansen, bearing in mind 'inprogress' does not get seen17:13
apwit appears as Todo 17:14
jjohansenapw: oh?  For some reason I thought it showed up different17:14
apwapparmor loos ok17:14
apwsadly no, pitti's db squashes inprogress to 'not done yet'17:14
apwjjohansen, as far as i can see they are all there17:16
JFocnd, any Jerone love coming for Big Daddy's bug 581312 ?17:17
ubot2Launchpad bug 581312 in linux (Ubuntu) "Unknown key fee[x] pressed (affects: 1) (heat: 20)" [Medium,Triaged] https://launchpad.net/bugs/58131217:17
jjohansenapw: hrmm, /me wonders why is browser tab isn't refreshing when reload is hit17:17
cndJFo: I haven't heard anything17:17
blue_annacan I get help getting i2c-core module for my build? it's not in my kernel and I don't see an alternative in the repositories17:17
JFok17:17
blue_annaI was directed here form ubuntu devel17:18
blue_anna*from17:18
cndblue_anna: I'm guessing it's already built in17:18
jjohansenapw: alright killing firefox fixed it, sorry and thanks17:19
cndblue_anna: yes, it's already builtin in Ubuntu kernels17:19
apwjjohansen, la la la can't heard you17:19
cndCONFIG_I2C=y17:19
blue_annacnd: not in 2.6.32-21-powerpc64-smp17:20
smbapw, Bah! Having one common enforcer file was probably not the most brilliant idea17:20
ograjjohansen, stop moaning, i'm trying to get mobile blueprints on our charts and fail miserably, you ate least have something more than one work item :) (http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html) 17:20
ogra*at least17:20
apwsmb, that is already sorted in my ubuntu-debian replacement17:20
apwit moves to being repository specific17:20
smbapw, More reason to have that soon. *sigh*17:21
apwsmb, its waiting on your trees quiesing long enough to apply it17:21
apwi know thats a difficult thing17:22
blue_annacnd: apt-file search i2c-core | wc -l | xargs -0 echo "results found " ==> results found 017:22
jjohansenogra: wow I guess that means you have no work items for this ;)17:22
smbapw, While its causing more trouble getting then quieting down. :-P 17:22
ograjjohansen, easy dev cycle this round :)17:22
apwblue_anna, if its built-in there is no module file to search for17:23
blue_annaapw: oo that kind of built in :)17:23
apwblue_anna, yep, =y on a CONFIG_* item means make it part of the kernel image itself17:24
apwogra, heh got an example blueprint, i've been through most of the errors this week17:24
apw(one thats missing i mean)17:24
ograapw, just catched pittin in -devel :)17:25
blue_annaapw: so I can just behave as if it is already loaded as a module -- like I can do all the insmods without the modprobe at this instructions? http://ubuntuforums.org/showpost.php?p=4267018&postcount=717:25
ogra*pitti in17:25
blue_annaapw & cnd thank you both17:25
ograapw, seems i always make the same mistakes of adding a blank line after "Work items" (it looks so ugly without)17:27
apwogra, hehe :)17:27
cndblue_anna: you should be able to ignore anything that tells you to insmod or modprobe i2c-core17:27
ograand since all our specs were discussed under ubuntu-arm they are all named wrongly as well17:27
ograits a total mess17:27
blue_annacnd: thanks again17:28
cndnp17:28
* cking is going ACPI testing loopy17:34
achiangcking: ah, is there anything from the bios testing blueprint i can help with?17:35
bjf##17:37
bjf## Kernel team meeting in 25 minutes17:37
bjf##17:37
manjobjf, wonder why I don't see it in the canonical calendar17:43
bjfmanjo, looking17:43
JFosounds like user error manjo :-P17:43
ckingachiang, I have a git repo now with my code on it - it may be worth occasionally giving it a test spin17:44
achiangcking: ah, cool. pointer to the repo?17:44
ckingachiang, http://kernel.ubuntu.com/git?p=cking/ubuntu-firmware-test-suite/.git;a=summary17:45
bjfmanjo, it's on the calendar that i'm looking at17:45
achiangcking: thanks17:45
manjobjf, strange... something wrong at my end 17:45
ckingachiang, check it out, ./configure and run ./src/testsuite --help ;-)17:46
achiangcking: yep, maybe i'll get a chance to play with it today17:46
bjfmanjo, the calendar it's on is "Ubuntu Kernel Schedule"17:46
manjobjf, ah I am subscribed to it somehow... wonder what happened17:47
manjobjf, *not*17:48
manjobjf, can you add me to that calendar ? 17:48
bjfmanjo, i don't think so, probably has to be pgraner or tgardner 17:49
JFolooks like the other meeting will run over bjf 17:51
bjfJFo, when we all stomp into the channel, they may close up17:52
JFomayhap17:52
manjobjf, you need to get ops fro that one too17:53
bjf##17:57
bjf## Kernel team meeting in 5 minutes17:57
bjf##17:57
apwthey finished on the dot18:00
bjf##18:01
bjf## Meeting starting now18:01
bjf##18:01
achiangcking: what's the git url to clone your test suite?18:24
achiangcking: my guess of:  git://kernel.ubuntu.com/projects/cking/ubuntu-firmware-test-suite.git was unsuccessful18:24
ckingachiang, hrm, dunno why, let me check it out after the meeting18:25
apwhttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/39784518:31
ubot2Launchpad bug 397845 in linux (Ubuntu) "Thinkpad T30 backlight remains on during supend (affects: 1)" [Undecided,Expired]18:31
phunge0hi i have a question18:33
phunge0for pgraner possibly18:33
phunge0i'm the submitter of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/58509218:33
ubot2Launchpad bug 585092 in linux (Ubuntu) "tmpfs umount slowdown (affects: 1) (heat: 12)" [Undecided,Incomplete]18:33
phunge0i have a ubuntu-lucid git fork with backports of mainline packages that i'd like to link on that bug18:34
phunge0so i need to be able to host the git repo somewhere18:35
apwphunge0, if the backport is big enough that you can't attach it, then its likely not going to be SRUable18:36
phunge0it's 3 cherrypicked patches18:36
ckingachiang, try git clone  git://kernel.ubuntu.com/cking/ubuntu-firmware-test-suite18:36
phunge0should i just attach 3 patches?18:36
apwthen simply putting the three headers from those in the bug18:36
phunge0how do you mean headers? fyi the cherrypicking involved some merging18:37
JFoapw: http://status.qa.ubuntu.com/qapkgstatus/linux18:38
achiangcking: yep, that got it, thanks18:38
apwthen attach the full patches.  if they were just cherry-picks then the sha1's and description would have been enough ... else the whole patches are needed18:38
phunge0k i'll do that tx18:38
ckingachiang, you need to do a git pull on that got pick up klog.h - then ./configure and run sudo ./src/testsuite --show-progress --results-output=achaing.log --stdout-summary18:43
* cking goes for food18:44
apwKeybuk, yo ... SYSFS deprecated settings you wanted off, were there any other than the SYSFS_DEPRECATED* those ones ... 18:46
apwcnd, http://people.canonical.com/~scott/daily-bootcharts/20100406-max-kernel.png that was from the 4th18:46
Keybukno, was just wanting to make sure they're all in the config checker18:47
Keybukthey should be all off atm18:47
apwKeybuk, ack ... thakns18:47
apwKeybuk, do you need warning of getting all kernel command line options in upstart18:48
KeybukI'd like to know when that lands18:49
Keybukbut I don't need to do anything first18:49
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/KernelTeam/ || Lucid Kernel Version: 2.6.32 || Ubuntu Kernel Team Meeting - June-01 - 17:00 UTC
apwbjf, is the topic here on the list to change page, and i note the link still points to my copy not yours and mine exists and shouldn't18:51
bjfapw, ack, haven't fixed that yet, will do so now18:51
bjfapw, which link are you refering to, i'm looking on the knowledgebase page18:53
* manjo going to a meeting on improving server testing with checkbox ... yaaay!18:55
* cking wonders if we should have an ignorancebase page for answers we don't have18:55
apwbjf i added one to the top of the meeting page, as that is where i yearned to find the info18:55
bjfapw, that's too obvious18:56
apwsorry18:56
JFobjf, that topic probably needs to change to Home: https://wiki.ubuntu.com/Kernel/18:57
JFowhoops18:57
JFonm18:57
JFoI just finished reading back18:57
JFo:)18:57
ckingachiang, any luck with the test tool?19:05
achiangcking: trying to get my test machine up. :-/19:09
cking;-(19:11
* achiang learns a lesson about touching interesting BIOS knobs on proto hardware.19:12
achiangluckily, pulling the CMOS battery did the trick19:12
ckingphew19:12
ckingachiang, well, when you get some results, email the log to me so i can sanity check the code19:20
cking..no rush19:20
achiangcking: yep, i'm installing lucid now19:20
phunge0JFo: i've updated my bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585092 with the triage info, what needs to happen to get it out of incomplete triage land?19:21
ubot2Launchpad bug 585092 in linux (Ubuntu) "tmpfs umount slowdown (affects: 1) (heat: 12)" [Undecided,Incomplete]19:21
JFophunge0, I need to get to it :)19:22
phunge0thanks :)19:22
JFophunge0, done19:26
phunge0JFo, thanks19:26
JFonp19:26
jjohansen-> lunch19:59
vanhoofJFo: I grabbed that bug for now until I can divy it out20:26
JFocool, thanks bro :)20:27
JFosorry for all the confusion20:27
* ogasawara -> lunch20:31
* bjf -> lunch20:35
vanhoofJFo: no worries, the whole thing is kinda screwed up20:37
JFoyeah20:38
JFoCan HAz bug servur dat stays available longer than 5 minutes? kthxbai21:06
* JFo kicks Launchpad in it's bad pants21:06
cwilluis btrfs anybody's pet project here?21:12
pgranerbjf: can you add ubuntu-news-team@lists.ubuntu.com to cc: list of the email you send out after the k-t meeting21:13
bjfpgraner, sure21:13
pgranerbjf: thanks that way it will make UWN21:14
pgranerbjf: I sent them this weeks already21:14
pgranerbjf: thanks21:14
bjfpgraner, "the queen" was going to take care of it for me :-), but I'll do this as well21:14
bjfJFo, I'm looking at your "Release Meeting Bugs", you have "fsl" and "mvl" listed though we don't have them in maverick21:22
JFohmmm, excellent point :)21:22
bjfogasawara, ^21:23
* JFo marks them for removal if that is the consensus21:23
bjfogasawara, what should we be tracking "Release Meeting Bugs" wise?21:23
ogasawarabjf: we don't have fsl and mvl-dove for Maverick at the moment, so no need to track21:45
ogasawarabjf: release meeting have yet to start, so nothing to track at the moment21:45
ogasawarabjf: I'd just go with tracking any Alpha1 targeted bug at the moment21:45
bjfogasawara, ok21:46
svuchrisccoulson, hi :)21:47
svuchrisccoulson, who would be the person to talk to?21:48
vanhoofwhat is the key for push to talk on mumble?22:05
vanhoofanyone know off hand22:05
bjfvanhoof, you set it yourself22:05
vanhoofhmm ok22:05
* vanhoof looks22:05
bjfvanhoof, configure->settings->shortcuts22:05
vanhoofbjf++ thanks!22:06
keesogasawara: around?  I need rebase help.  :)23:05
ogasawarakees: I'm here23:06
keesogasawara: okay, so I have a git tree that was a clone of ubuntu/ubuntu-maverick.  I've worked on it and comitted locally.  more changes have gone into the origin, so how do I carry my stuff forward to be at the "top"?23:07
kees(if I do "git pull" I end up with a "merge" commit at the top)23:07
achianggit fetch && git rebase origin23:08
kees\o/ that worked.  thanks achiang :)23:08
ogasawarakees: what achiang said :)23:08
keeshuzah, my git push even worked now.23:08
achiangkees: in general, you almost never want to do a git pull23:09
achiangsince it'll more often than not add a merge commit on top23:09
keesachiang: yeah, totally agreed.  :)23:09
achianggit fetch will pull down the new metadata and then you can do a git rebase origin to move your patches to the end23:10
achiangalso, stacked git is way nicer than raw git23:10
keesachiang: what is "stacked git" ?23:10
keesogasawara: here is my tree, is this in the right form for me to do a pull-request?  http://kernel.ubuntu.com/git?p=kees/ubuntu-maverick.git;a=summary23:11
achiangkees: conceptually, it's quilt + git23:11
achiangkees: but way nicer than either quilt or git by itself. :)23:11
keeshunh, neat23:11
achiangkees: basically, the problem it solves is, "how do i manage a patch queue on top of a git tree?"23:12
achiangso here's a limitation in git: a commit is forever. so if you're developing a bunch of patches, say 1, 2, 3 ; have committed 1 and 2 and are now working on 3, then realize that you really wanted to do something different in 1, you are screwed23:13
cwillu_at_workgit pull --rebase23:13
achiangyou have to do ugly stuff like save off the patches manually, then reapply them23:14
achiangin stacked git, you can just say: stg pop ; stg pop ; <hack hack hack> ; stg refresh ; stg push ; stg push23:14
ogasawarakees: git request-pull Ubuntu-2.6.34-4.11 git://kernel.ubuntu.com/kees/ubuntu-maverick.git master23:14
keesogasawara: cool; I had most of that but not the final "master".  what is the convention for the email subject line?23:15
cwillu_at_workachiang, why wouldn't you just branch off a to a'; hack hack hack; and then rebase b and c on a'?23:16
keesogasawara: but, I mean, it's sane for me to have the reverts followed by the updates?23:16
ogasawarakees: subject line can just be "Maverick pull request for <insert blurb>"23:17
achiangcwillu_at_work: in your example, what are b and c?23:17
ogasawarakees: yep, sane to revert patches you want to drop and then apply the ones you want23:17
keesperfecto23:18
cwillu_at_workachiang, I meant your 1, 2, 323:18
cwillu_at_workthe patches series23:18
achiangcwillu_at_work: to keep a clean development history23:19
achiangthat's the simplest answer23:20
cwillu_at_workI don't follow;  that's what rebase is for:  to keep a clean development history, no?23:20
keeswheee, I did a pull request.  ;)23:20
achiangcwillu_at_work: what if you want to edit the changelog of patch 1 and your HEAD is pointing to patch 3?23:21
ogasawarakees: \o/23:21
keesogasawara: and I even did the sneaky interactive rebase merge thingy.23:22
ogasawarakees: I'll get these applied and uploaded for Alpha123:22
keesogasawara: oooh, cool, thanks.23:23
cwillu_at_workachiang, I'm finding it difficult to come up with something different than "uh, rebase it?" as a response :p23:25
achianghm.23:27
achiangso you commit patch 1.23:27
achiangthen, commit patch 223:27
achiangdecide you want to change patch 1, so ... git branch <sha1 of patch 1 - 1>23:28
achiangactually, i can't figure out how you would do what you propose with rebase23:28
achiangeach commit is atomic, so i fail to see how a rebase lets you change a commit23:30
* achiang shrugs, goes outside to hack at stubborn roots23:34
=== kamalmostafa is now known as kamal
jjohansenachiang: you can do an interactive rebase, tell it which commits you want to edit23:45
jjohansenbut I find guilt/stgit easier to work with than interactive rebase23:45
jjohansenguilt/stgit also make it easier to shelve patches23:47

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