[00:01] <RAOF> ogasawara: Hah.  Excellent timing for my email then!  Yeah, I'll wait for them to get back :)
[00:01] <ogasawara> RAOF: cool.  just didn't want you think it was getting ignored.
[00:47] <jjohansen> -> back on later
[09:03] <bullgard5> What is the function of the phy0 process on my Ubuntu 10.04 computer?
[09:20] <smb> bullgard5, Just a guess but phy* usually relates to network cards, so I would suspect a certain network driver to create it.
[09:24] <bullgard5> smb: I see. Thank you for commenting.
[13:31] <chetnick> Hello everyone. I would like to add support for few things in kernel without losing current configuration. I am on the default Ubuntu install/kernel right now. How do I do that? Would make oldconfig do the thing?
[15:37] <mpoirier> ogra ?
[16:07] <bjf> ##
[16:07] <bjf> ## Kernel team meeting in two hours
[16:07] <bjf> ##
[16:38] <manjo> bjf, the meeting does not show on the canonical cal
[16:38] <manjo> bjf, does it show for you ? 
[16:42] <bjf> manjo, yes it does
[16:44] <manjo> bjf, strange
[16:51] <ogra> mpoirier, whats up ?
[16:53] <mpoirier> ogra: I had questions but got in touch with Sebastien @ TI - all good.
[16:53] <ogra> oki
[17:35] <cking-afk> back in 15
[17:47] <bjf> ##
[17:47] <bjf> ## Kernel team meeting in 14 minutes
[17:47] <bjf> ##
[18:30] <ogasawara> tgardner, smb, apw:  just fyi , cjwatson  moved the kernel upload permissions to be attached to the ubuntu-kernel-uploaders team.  If this breaks anything (either upload permissions for any of us, or the ability to target bugs to releases), then please let him know
[18:31] <smb> ogasawara, ok, will do as soon as I notice anything
[18:31] <ogasawara> tgardner: you actually might not be affected as you're motu I think
[18:32] <smb> ogasawara, sconklin, bjf FYI, if yo not already know this: http://people.canonical.com/~ubuntu-archive/pending-sru.html
[18:32] <sconklin> now ~that~ is a handy thing
[18:33] <smb> sconklin, If you see a red bug number at the side of a kernel package, run! :)
[18:34] <tgardner> smb, the SRU verification team must hate the kernel packages.
[18:35] <smb> tgardner, They surely do. Even with the hundreds of patches hidden in one tracking bug, we cause quite a bit a work...
[18:35]  * bjf has to run an errand will be back asap
[19:23] <manjo> cking, around ? 
[19:23] <manjo> cking, interested in uefi banter?
[19:25]  * tgardner lunches
[19:25] <kees> sure is nice to have a 64-way builder :)
[19:26] <smb> kees, Surely beats my 4-way :-P
[19:32] <manjo> cking, ?
[19:37] <cking> manjo, I'm kinda tied up doing some OEM work and putting the kids to bed
[20:07] <jjohansen> -> lunch
[20:39] <shadeslayer> hi,is there a way to delay the boot,and to get it to go step by step? 
[20:39] <shadeslayer> like each process is loaded one at a time and not getting it multi threaded
[21:03] <kees> shadeslayer: there is not yet.  I really want something like this, though, it's very painful to debug at the moment.
[21:03] <shadeslayer> :)
[21:04] <shadeslayer> kees: were discussing a problem over at #ubuntu-x,its related to something between the boot and the part where gdm has to start up
[21:04] <shadeslayer> X starts up,but g/kdm hangs
[21:04] <kees> ew
[21:05] <kees> smb: okay, so you have your local u-c-t branch, with one commit, and you want to merge the recent upstream u-c-t changes?
[21:05] <smb> right. this is my current local head.
[21:06] <smb> revno: 2796
[21:06] <smb> committer: Stefan Bader <smb@maximegalon>
[21:06] <smb> branch nick: ubuntu-cve-tracker
[21:06] <smb> timestamp: Tue 2010-06-29 18:55:13 +0200
[21:06] <smb> message:
[21:06] <smb>   Assigned smb to CVE-2008-7256
[21:06] <ubot2> smb: mm/shmem.c in the Linux kernel before 2.6.28-rc8, when strict overcommit is enabled and CONFIG_SECURITY is disabled, does not properly handle the export of shmemfs objects by knfsd, which allows attackers to cause a denial of service (NULL pointer dereference and knfsd crash) or possibly have unspecified other impact via unknown vectors.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-1643. (http://cve.mitre.
[21:06] <smb> Oh shut up
[21:06] <kees> heh
[21:07] <kees> we should train ubot2 to only respond to CVEs if we specifically say !CVE....
[21:07] <smb> That might be helpful
[21:07] <kees> smb: alright, so if you do "bzr pull lp:~ubuntu-security/ubuntu-cve-tracker/master/" what happens?
[21:07] <kees> who controls ubot2?
[21:08] <smb> bzr: ERROR: These branches have diverged. Use the missing command to see how.  
[21:08] <smb> Use the merge command to reconcile them
[21:08] <kees> okay
[21:08] <smb> kees, maybe someone in IS does?
[21:08] <kees> so, now if you do "bzr missing" it should say 1 (yours) and 1 (marc's)
[21:09] <smb> That says nothing as my change is pushed to my remote 
[21:09] <kees> oh, sorry, "bzr missing lp:~ubuntu-security/ubuntu-cve-tracker/master/"
[21:09] <smb> Basically I bzr branches from lp:~canonical-kernel-team...
[21:10]  * kees nods
[21:10]  * smb waits for bzr
[21:10] <smb> ok says I am missing one change
[21:10] <shadeslayer> kees: btw if you have any idea,head over to ubuntu-x :P
[21:11] <kees> shadeslayer: I don't; I had been fighting bug 597075 which caused a much earlier hang
[21:11] <ubot2> Launchpad bug 597075 in linux (Ubuntu) (and 1 other project) "2.6.35 hangs at boot due to regression in i915 or intel_agp (affects: 2) (heat: 12)" [High,Triaged] https://launchpad.net/bugs/597075
[21:11] <kees> smb: alright, so "bzr merge lp:~ubuntu-security/ubuntu-cve-tracker/master/" should pull down marc's change and apply it.
[21:11] <shadeslayer> kees: ow
[21:11] <kees> smb: and when you go to commit, you'll make a "merge" commit.
[21:12] <shadeslayer> kees: when you have time,bug 593041
[21:12] <ubot2> Launchpad bug 593041 in linux (Ubuntu) "New 2.6.35 kernel keeps toggling bluetooth radio and wireless radio (affects: 1) (heat: 192)" [Undecided,Triaged] https://launchpad.net/bugs/593041
[21:12] <shadeslayer> its very annoying
[21:12] <smb> kees, Well it pulls down the changes, yes and I can commit them, but then there is no evidence about those changes made by him
[21:12] <smb> I think
[21:12]  * shadeslayer didnt know it had 192 heat
[21:14] <kees> smb: it's visible if you do "bzr log --include-merges"
[21:15] <Kano> hi, why does my i5 run with 1200 mhz with lucid?
[21:15] <Kano> then i installed powernowd and it went to 3334
[21:15] <Kano> tested with load
[21:16] <smb> kees, How obvious. :-P I am beginning to feel the urge of apw-like rants...
[21:16] <kees> smb: now you know how I felt learning git when I already knew bzr.  :P  *head explodey*
[21:16] <kees> tgardner: btw, I learned how to do a moving rebase when maverick gets rebased.
[21:17] <kees> git rebase --onto maverick commit-of-old-maverick-head-in-my-maverick-topic-branch my-topic-branch
[21:17] <smb> kees, Did you have to concentrate as much as I need to not to type git everytime I mean bzr. :)
[21:17] <kees> smb: I still type "bzr" instead of git about 1/4 of the time.  :)
[21:18] <smb> kees, hehe
[21:18] <kees> though I'm now getting very angry that "bzr log" doesn't automatically use the $PAGER env var.  :P
[21:18] <smb> Right that is very useful. As it is rare that you want to know about the first comit
[21:19] <kees> no kidding :)
[21:20] <kees> heh, maximegalon.
[21:21] <smb> kees, Oh well, I still don't know how to override the local hostname with something sensible. :)
[21:21] <kees> ~/.bazaar/bazaar.conf
[21:21] <kees> [DEFAULT]
[21:21] <kees> email = Kees Cook <kees.cook@canonical.com>
[21:21] <kees> launchpad_username = kees
[21:21] <smb> Ohhh, no BZR_EMAIL? :-P But thanks
[21:22] <kees> and you can do individual overrides in ~/.bazaar/locations.conf
[21:22] <kees> hm, looks like both $EMAIL and $BZR_EMAIL are respected, actually (so says "man bzr")
[21:22] <jaminc> looking for some help tracking down the cause of an oddity... changing only the system's kernel version results in libvirt being unable to write to VM disk images unless the images are owned by root.  I've ruled out apparmor interactions as apparmor is uninstalled and the behavior persists
[21:23] <jdstrand> jaminc: is this on maverick?
[21:23] <smb> kees, Ok, guess i try to implement something of that in my scripts, as they also take some of that
[21:23] <jdstrand> jaminc: actually, I was thinking it was something else, but you ruled out apparmor
[21:24] <jaminc> jdstrand, not on maverick, but I guess I could give it a shot... Lucid's stock kernel works fine, but mainline's 2.6.34 and 2.6.35 exhibit the problem
[21:24] <jaminc> had to move to mainline to fix a periodic kernel crash/reboot that appears to be related to the wireless
[21:47] <jaminc> chatting with the libvirt folks, indications are that the write failure is some sort of kernel issue.  Considering that simply booting to an older kernel alleviates the issue, I'm inclined to agree, but not sure how to pin it down...
[21:51]  * ogasawara late lunch
[21:57] <dandel> i caught a regression between 2.6.35-rc1 and 2.6.35-rc5... however, i'm not sure what to classify the bug as.... the bug is that onboard keyboard and mouse on my laptop stopped responding to all input, however i can reboot the machine with a usb mouse.
[21:58] <dandel> ** 2.6.35-rc3 (latest git revision)
[22:01] <kees> how do I specify a branch in the request-pull ?
[22:02] <kees> oh, duh [end]
[22:03] <smb> kees, Yeah, sorry slow
[22:03] <smb> kees, the name of the branch refers to the HEAD of it
[22:04] <kees> I keep getting an error, though
[22:04] <kees> warn: No branch of git://kernel.ubuntu.com/kees/ubuntu-maverick.git is at:
[22:04] <kees> warn:   7bc505d: SAUCE: security: unconditionally chain to Yama LSM
[22:04] <kees> warn: Are you sure you pushed maverick-yama there?
[22:04] <kees> oh man, it must be time for lunch
[22:04] <kees> I see the problem
[22:07] <jjohansen> kees: something like
[22:07] <jjohansen> git request-pull c2e8d51100f22433062a86ec36383b549b7eb191 git://kernel.ubuntu.com/jj/ubuntu-maverick.git atop
[22:08] <jjohansen> using git:// is important
[22:08] <kees> jjohansen: yeah, I was aiming at the wrong repo.  *hang head*
[22:09] <smb> kees, Hah, this looks ok. Thanks for the hints
[22:09] <kees> smb: okay, great
[22:11] <smb> kees, Now it will get interesting if you ever pull things back. I *am* very confident of bzr as you see. :)
[22:12] <kees> smb: heh
[22:13] <kees> smb: this is why I like "bzr missing" it's kind of handy
[22:14] <smb> kees, I won't go into the how this likely can be done with git just the same (or is not needed that much). Its too late here...
[22:22] <jaminc> is there a place to report bugs found in kernels from the mainline-ppa?
[22:24] <jjohansen> jaminc: https://bugzilla.kernel.org/
[22:26] <jaminc> guess I'm a bit confused, are the mainline builds essentially just the kernel.org versions?
[22:27] <jjohansen> yes
[22:27] <jjohansen> just built into a deb for testing
[22:27]  * jaminc slaps himself
[22:27] <jaminc> thank you
[22:33]  * smb Thinks its time to call it a day
[22:37] <jaminc> Bug 16316 filed
[22:37] <ubot2> Launchpad bug 16316 in debian (and 1 other project) "ximian-connector: FTBFS: Cannot find evolution libs (heat: 1)" [Unknown,Fix released] https://launchpad.net/bugs/16316
[22:38] <jaminc> ubot2 got it wrong... https://bugzilla.kernel.org/show_bug.cgi?id=16316
[22:38] <ubot2> jaminc: Error: I am only a bot, please don't think I'm intelligent :)
[22:38] <ubot2> bugzilla.kernel.org bug 16316 in kvm "VM's started through libvirt can't write to disk image files unless the file is owned by root" [Normal,New]
[22:42] <Kano> btw. i tested a lucid install, my i5-680 runs with 1200 MHz by default and does NOT scale up
[22:42] <Kano> same with maverick
[22:42] <Kano> is that normal...
[22:49] <bullgard4> What does the message "ath5k_pci 0000:02:00.0: registered as 'phy0'" mean in http://www.ureader.de/msg/12564876.aspx? (My Ubuntu 10.04 dmesg produces the same message.)
[22:50] <mjg59> It means that the atheros 5000-series wireless device at pci address 02:00.0 has been associated with the wireless core and given the name phy0
[22:51] <ogra> Kano, its called green computing :P
[22:52] <Kano> no its called stupid
[22:52] <ogra> well, rather buggy i'd guess
[22:59] <bullgard4> mjg59: What programs will use the name 'phy0' thereafter? '~$ iwconfig' only lists »lo«, »eth0«, »irda« and»wlan0«.
[23:06] <mjg59> bullgard4: It's not a network interface
[23:06] <mjg59> iw will use the phy name for some things
[23:08] <bullgard4> mjg59: In order to establish this association you spoke about, does the kernel just run a process called 'phy0'? (My Ubuntu 10.04 computer does run a kernel process called 'phy0'.)
[23:08] <mjg59> No, that's just the kernel workqueue associated with the phy
[23:09] <bullgard4> mjg59: Thank you very much for your explanations.
[23:38] <Kano> i just tested a few things, ondemand does nothing with that i5, performance is 100% and conservative works too
[23:38] <Kano> it scales up/down
[23:38] <Kano> on demand does definitely not scale