[01:18] <ogasawara> bjf: yo
[01:24] <matti> http://www.ustream.tv/channel/live-iss-stream -- technology is so great. A live stream from above the Planet.
[01:25] <matti> Ahh. :)
[01:25] <pbuckley> nice
[01:25] <matti> If somebody would suggest to me back in 1999 that in 2012 I will be watching I live stream from the orbit of our planet.
[01:25] <matti> I would have rather mixed feelings.
[01:26] <matti> And look at it now...
[01:26] <matti> [ Although, still not flying cars ;d ]
[02:05] <ScottL> apw,  TheMuso has made some changes to the lowlatency kernel, picking up on comments:  git://kernel.ubuntu.com/themuso/ubuntu-precise-lowlatency.git
[02:11] <bjf> ogasawara: sort of figured it out, thanks though
[08:33]  * apw yawns
[08:33]  * smb crawls out of a pile of emails
[08:34]  * apw crawls out from under a pile of leaking nm-applet
[08:34] <apw> i am going to have to start killing it before i suspend, the machine is almost unrecoverable when its out of control
[08:35] <aBound> Hello all, is there anyway I can find out a few release notes for a Ubuntu kernel release?
[08:35] <apw> there are release notes for each main release which contain any issues for the kernel
[08:36] <apw> https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes
[08:37] <apw> for instance
[08:37] <apw> aBound, ^^
[08:37] <aBound> apw, Thankies I been trying to find that for quite a while.
[08:37] <smb> apw, nm-applet sounds fun. but how does it get worse on suspend? Or just worser than before because it has to rescan?
[08:38] <apw> worse cause the machine dumps all of its ram on the floor when it suspends
[08:38] <aBound> apw, There's no kernel release notes for Alpha's are there?
[08:38] <apw> and swaps like a complete swine
[08:38] <apw> aBound, there are release notes for the latest one i believe
[08:38] <apw> they get reused for the next one and become the final release notes
[08:39] <aBound> apw, Awesome. :P
[08:39] <aBound> Always good to know what's been fixed.
[08:39] <apw> aBound, i found those by searching for 'ubuntu precise alpha 2 release notes' in google
[08:40] <apw> https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview/Alpha2
[08:40] <aBound> Thankies again. :)
[08:40] <apw> smb, ok now sound settings is crashing when i select an input source ... wtgf
[08:40]  * apw reboots
[08:48] <apw> diwic, i have sound setting dieing in a heap every time i select an external sound source, known?
[08:48] <diwic> apw, what does "external sound source" mean?
[08:48] <apw> diwic, going to the inputs setting and selecting my external usb mic as input
[08:49] <apw> (or trying to as i don't believe its changing it)
[08:49] <apw> diwic, today is the first time i have had _two_ input sources for my external mic
[08:49] <apw> i now have an iec958-stereo-input and Microphone
[08:49] <diwic> apw, oh :-/
[08:49] <apw> up till today i have only had Microphone
[08:50] <apw> this is hampering my use of mumble to say the least
[08:50] <diwic> and that's for the usb mic I suppose
[08:50] <apw> yes my blue snowball
[08:50] <apw> not that i can upgrade any further right now as it wants to ... guess ... go on ...
[08:50] <apw> remove half my machine again
[08:50] <diwic> apw, well, as an immediate workaround, install the pavucontrol package and select input through there
[08:51] <apw> diwic, ok that shows just one input for it
[08:51] <diwic> ignore the iec958 and use Microphone only.
[08:52] <diwic> ronoc's been seeing the duplicate iec958 stuff some times as well
[08:52] <apw> diwic, ok how does one actually select the input source with this thing ?
[08:53] <diwic> apw, easiest is, while recording in mumble, go to the recording tab. It'll show Mumble and a dropdown to select current input
[08:53] <apw> ahh
[08:54] <apw> diwic, yeah that seems to work
[08:55] <diwic> apw, btw, this might store an application <=> input connection in a database.
[08:55] <apw> diwic, would this be 'gnome-control-center' crashing ?
[08:55] <diwic> apw, yes. And assign it to Conor Curran
[08:55] <apw> diwic, as it it might use the mic i selected by default for that app ?
[08:56] <apw> then i can't file a bug as its out of date, and i can't update it.  f*ck this archive ... "always installable all cycle" my ass
[08:57] <aBound> Goody goody sounds like 12.04 will be a nice release. :P
[10:30] <brendand> apw - you can use pacmd
[10:30] <apw> brendand, thanks
[10:31] <brendand> apw - list-sinks/sources, set-default-sink/source
[10:31] <apw> nice
[12:20]  * ppisati -> out for lunch
[12:48]  * apw pops to the pool
[13:08] <tgardner> cking, 3 ecryptfs patches have been queued for 2.6.32.y stable; Ban ecryptfs over ecryptfs, eCryptfs: Remove mmap from directory operations, and Add mount option to check uid of device being mounted = expect uid, CVE-2011-1833
[13:08] <ubot2`> tgardner: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1833)
[13:13] <cking> tgardner, many thanks
[13:40] <Ezim> so now I have reported 2 kernel bug.
[13:41] <Ezim> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/933387
[13:41] <ubot2`> Launchpad bug 933387 in linux "Bluetooth usb problem in Kubuntu 11.10! Kernel related? " [Undecided,Confirmed]
[13:41] <Ezim> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/933443
[13:41] <ubot2`> Launchpad bug 933443 in linux "Problem after installing cpufrequtils! Kubuntu 11.10" [Undecided,Confirmed]
[14:11]  * apw fails to see why the second of those is kernel related
[14:13] <apw> cking, when you did your governer tests, you said you tested a userspace one, which one was that ?
[14:13] <cking> apw,  cpufreqd
[14:13] <cking> et al
[14:13] <apw> and cpufreqd was worse right, badly so ?
[14:14] <cking> it could not beat the default, and it made some less than optimal choices on some scenarios. Also, I suspect it added some extra overhead
[14:14] <apw> got a link to the testing there ?
[14:15] <apw> then i can shove it in this bug and dump it on cpufreqd :)
[14:15] <cking> apw, http://zinc.canonical.com/~cking/power-benchmarking/cpu-governor/
[14:16] <apw> cking, is the results.txt URL there likely to be persistant ?  so i can put it in a bug ?
[14:16] <cking> apw, they should be persistent enough
[14:17] <cking> I won't be removing them in a hurry
[14:23] <apw> cking, yay, great writeup, saved me wodsmithing anything, excellent
[14:23] <cking> apw, that was my aim - collate, analyse, report
[14:24] <smb> copy
[14:24] <apw> when will this archive be installable fully again
[14:24] <smb> apw, May
[14:25] <apw> 2013 ?
[14:25] <cking> heh
[15:12] <apw> ogasawara, am final build testing the HV update and will the push it in
[15:12] <ogasawara> apw: ack
[15:13] <apw> ogasawara, seems that this combination works well for them and is performant, the v3.2 hv drivers just crap out after a few seconds and lose the drives, not hot
[15:14]  * ogasawara back in 20
[15:29] <apw> ogasawara, tgardner-afk, ok Hyper-V combo pushed, deviations.txt included
[15:34] <ogasawara> apw: thanks
[15:37] <apw> ogasawara, just realised that i am still waiting on the initramfs-tools update to go in, check back with me before this gets uploaded, we may need to hold the flipper if its not gone.  am asking for it to be sponsored nwo
[15:38] <ogasawara> apw: will do
[15:56] <apw> ogasawara, the initramfs-tools bits just went up so i think by the time any builds you do make the archive they will be done
[15:57] <ogasawara> apw: cool.  I was thinking of uploading tomorrow.  I want to get this rc6 thing sorted first as if we are going to flip that on by default I want to have it in the beta-1 kernel upload for maximum testing exposure.
[15:57] <apw> ogasawara, sound plan indeed
[15:57] <apw> ogasawara, persuade that cking to do you a call for testing :)
[15:57] <ogasawara> apw: am going to ping eugeni about it and also Sarvatt mentioned having some feedback as well
[15:59] <cking> if anything needs testing by community I'm happy to blog about it
[16:00] <ogasawara> cking: I'll for sure solicit your input for the cft.  what I'm thinking is that we'll want to craft a blurb about it in the Beta-1 release notes and reference a wiki set up with all the info and to capture any test results
[16:01] <cking> ogasawara, so we should capture the results in a wiki, it depends on what we want to exercise really with rc6
[16:02] <ogasawara> cking: is there a simple test we can have users run to compute their overall power savings?
[16:02] <ogasawara> cking: and obviously I'm interested in any regressions should they arise
[16:02] <cking> ogasawara, yep, lemme write up some notes on this and I'll send them to you
[16:03] <ogasawara> cking: perfect, thanks!
[16:07] <sforshee> apw, http://pastebin.ubuntu.com/844550/
[16:23] <cking> ogasawara - instructions in you inbox 
[16:23] <ogasawara> cking: thanks
[16:31] <kees> tgardner-afk: I mis-spoke, you can't only use upstream since it lacks link protections. I sent email with a pointer to a repo to pull from.
[16:40] <orated> I'm finding delay in boot time and these are the bootcharts for last two booting - http://imagebin.org/199031 http://imagebin.org/199035 . I'm not too much concerned about boot time but can anyone explain me what exactly is consuming time and how can I fix it?
[17:06] <tgardner> kees, ack
[17:21] <scott-work> tgardner: TheMuso made the changes you requested i believe for the lowlatency kernel : http://revu.ubuntuwire.com/p/linux-lowlatency
[17:21] <scott-work> tgardner: would you be a person who could check the kernel package and advocate on REVU?  we still just one advocate
[17:22] <tgardner> scottI'll have a look in a bit
[17:22] <tgardner> scott-work, ^^
[17:22] <scott-work> tgardner: thank you very, very much :)
[17:39] <tgardner> kees, jjohansen: have a look at the last 5 commits on precise master-next now.
[17:39] <tgardner> for yama, that is
[17:39] <jjohansen> tgardner: will do
[17:40]  * apw isn't convinces that disk separation hasn't regressed.  i just had my music stop when i was doing a git reset --hard HEAD
[17:46] <bkerensa> apw: Thanks btw for reviewing.... I actually had thought about the description being split and it was a oversight on my part
[17:52] <apw> bkerensa, no worries, the changes are applied to precise now already
[17:52] <apw> bkerensa, and if you'd not looked it'd have not gotten done
[17:53] <bkerensa> apw: Good thing there are some of us who commit time to bitesize :)
[17:53] <apw> yep, thanks for that
[17:53]  * apw wants his next song, now please
[17:54] <apw> no i mean now, really
[17:54] <apw> if its not tooooo much trouble
[18:47]  * cking thinks apw needs a beer
[18:49] <apw> cking, if i wasn't starting to feel ill i might well
[18:50] <cking> apw, time to stop working then methinks
[19:00]  * tgardner -> lunch
[19:00]  * cking -> EOD
[19:51] <kees> tgardner: the commits look good -- the only thing I'd note is that "drop after 3.3" for the last 2 isn't correct.
[19:52] <tgardner> kees, yeah, I figured we'll catch those when we start the Q series.
[19:52] <apw> clap4ham
[19:52] <tgardner> apw, password ?
[19:53] <apw> yeah unity failure
[19:54] <apw> luckily just a screen lock password
[19:55] <apw> about the 5th time its been in here too, one reason i don't change it
[19:56] <apw> as it'll just be in here again next week
[19:59] <tgardner> kees, ok, I updated the commit subject and removed '(drop after 3.3)' for those 2 commits
[20:02] <Sarvatt> heh i've had to make sure to log in with with the mouse instead of pressing enter ever since we switched to lightdm for that same reason
[20:02] <apw> its awful and no mistake
[20:03] <apw> they clearly don't have screen locks on their machines
[20:14] <ogasawara>  /me lunch
[20:15] <ogasawara> lets try that again
[20:15]  * ogasawara lunch
[20:21] <kees> tgardner: I'm still trying to get the link protections into the VFS directly, but it's a very very long path :P
[20:22] <tgardner> kees, no problem. I've been watching your struggles upstream
[20:22] <kees> I've eased back on pressure lately because I'm trying to not distract from drewry's seccomp_bpf stuff :P
[20:23] <tgardner> kees, speaking of which, I don't think precise has any seccomp patches
[20:26] <kees> tgardner: it doesn't and that's basically going to be the way it is unless things settle really quickly upstream.
[20:26] <tgardner> kees, ok, just wanted to be sure you knew about it
[20:26] <kees> tgardner: the old API never had any users, and the new API isn't confirmed really.
[20:27] <kees> tgardner: I wish the timing was better. maybe it could get SRUed, I'm not sure yet.
[20:27] <tgardner> kees, possibly, it is fairly separate from everythign else, and is easily tested.
[20:31] <GrueMaster> sconklin: Question on the power meter.  For measuring a system that has multiple power feeds, would it be better to measure AC power consumption?  I have the meter setup now on a panda inline with the 5v power, but I need to test a PC and server.  Those have multiple DC inputs.
[20:32] <kees> tgardner: the risk currently is that it does merge itself with the network BPF code now, so it's becoming less and less isolated. That's great for code size and runtime hit, but more scary for backporting.
[20:33] <tgardner> kees, ah. well, perhaps those that are real concerned about seccomp can run an LTS backport kernel when they are released
[20:34] <ohsix> GrueMaster: measuring them one at a time would be more useful than measuring the AC
[20:34] <ohsix> unless you want to know the wall plug consumption, which can vary in efficiency
[20:34] <sconklin> GrueMaster: the problem with measuring the AC side is that you also measure all the power supply losses, and anything else that's connected like disk drives, etc
[20:35] <GrueMaster> I was going to eliminate as many hardware differences as possible by using the same drives, ps, etc.  Only change would be motherboard attached.
[20:36] <GrueMaster> But I understand.
[20:36] <GrueMaster> Just a real pita with only one meter.
[20:36] <sconklin> You may still find that the changes you want to measure are lost in the noise if you do that. 
[20:37] <sconklin> i.e. CPU consumption changes may only amount to a range that's the least significant couple of bits in the meter
[20:38] <GrueMaster> True, but I think the goal here is system level.  It is fairly straight forward now, but when we get into blades, it will be much harder I would think.
[20:45] <ohsix> it's more work, but you can sum them in the end
[20:46] <ohsix> i want a 32 channel data logger so i can log everything, mouahouah
[20:46] <tgardner> 9999 %CPU is not a number you see everyday.
[21:05]  * tgardner -> EOD
[22:19] <scott-work_> doh, i wanted to tell tgardner thank you again, i'll catch him manana