[08:01]  * smb hails cking 
[08:01]  * cking requires more coffee
[08:05]  * apw yawns
[08:26] <ppisati_> diwic: so, the pulseaudio in the ppa:audio-dev fixed the cracking noise i head wrt skype
[08:26] <ppisati_> diwic: but i had to rip it off this morning cause after a bit
[08:27] <ppisati_> diwic: i got a loud 'beeeeepp' coming out of my speakers
[08:27] <ppisati_> diwic: and the noise didn't stop until some other audio samples was played
[08:31] <diwic> ppisati_, hmm, that sounds strange
[08:31]  * ppisati_ prepares some more coffee
[08:31] <ppisati_> diwic: if you want i can reinstall everything
[08:32] <diwic> ppisati_, nah, but I wonder what that beeeepp came from, really
[08:32] <ppisati_> diwic: and do some more debugging for you
[08:32] <ppisati_> diwic: is there a way i can find it out?
[08:32] <diwic> ppisati_, hard to tell without a verbose log, and examining the state when it's present
[08:33] <ppisati_> diwic: pulseaudio log?
[08:33] <diwic> ppisati_, https://wiki.ubuntu.com/PulseAudio/Log
[08:33] <diwic> ppisati_, but you need to reproduce the beep while the logging is active
[08:34] <ppisati_> diwic: yep, no prob
[08:34] <ppisati_> diwic: it happened two times in a row
[08:34] <diwic> ppisati_, do you know how to reproduce it?
[08:35] <ppisati_> diwic: login, play a couple of songs on you tune and that's it :)
[08:35] <ppisati_> *youtube
[08:36] <diwic> ppisati_, ok, while the beep is present also take a "pacmd list"
[08:37] <ppisati_> diwic: cool, will do
[08:54] <smb> infinity, Am I right in assuming you have not looked at any of the Xen packages, yet?
[09:06]  * apw bets on good old flash for pp's issue
[11:30] <alexbligh1> Is there a reason why module-init-tools is built with --disable-zlib? I've tried rebuilding with --enable-zlib, it adds no library dependencies, and allows for modules to be compressed with gzip. The saving of even one module's compression will outweigh the extra size of a static zlib I'd have thought. And compressing all the modules in Ubuntu running from RAM saves 100MB (150MB down to 50MB). I think cjwatson added the --disable-zl
[11:30] <alexbligh1> ib stuff (or just did the packaging). Any reason not to change this? (will supply patches)
[11:32] <cjwatson> module-init-tools is removed as of raring
[11:32] <cjwatson> And I have made one change to module-init-tools ever, according to the changelog, and it wasn't that
[11:33] <alexbligh1> cjwatson, ah I'm looking at Precise. Where do they live now?
[11:33] <cjwatson> For current releases, please look at kmod, not module-init-tools; for stable releases, I suspect such a change wouldn't be appropriate
[11:34] <alexbligh1> cjwatson, I have no idea where I got your name from :-)
[11:34] <alexbligh1> would it be appropriate to use zlib in kmod?
[11:35] <alexbligh1> For Precise I'll just build a custom package. I was just checking there was nothing deathly about module compression.
[11:35] <cjwatson> No idea
[11:36] <cjwatson> Would probably need benchmarking to make sure it doesn't regress boot performance for some reason (yes, intuitively the I/O gain should outweigh that, but it still needs benchmarking)
[11:36] <alexbligh1> thanks
[13:00]  * ppisati goes out for a bit, brb
[13:38]  * henrix -> back in 15
[13:45]  * rtg pushes v3.10-rc3 rebase to Saucy unstable
[13:46] <ogra_> vs Saucy stable ?
[13:48] <rtg> ogra_, vs Saucy master-next (which is likely to be much more stable then -rc3)
[13:48] <ogra_> ah :)
[13:48] <rtg> ogra_, I'm gonna do some testing on -rc3 today. if it looks OK, then perhaps I'll make it the new stable.
[13:49] <rtg> or master-next I mean
[14:09] <smb> Hm... seems today's netboot saucy images go straight into a panic (at least on Xen)
[14:13] <rtg> smb, I don't think the kernel has changed in awhile.
[14:15] <rtg> yeah, uploaded on the 20th
[14:15] <smb> rtg, I thought that did work last week but who know. Dumping now to see the more useful parts of dmesg... At least with today I seem to run into a bit of lvm trouble, too. Only some LVs of my 30 or so get their symlinks created in /dev/<vgname> or /dev/mapper/...
[14:16] <rtg> smb, wouldn't that be a udev problem ?
[14:17] <smb> rtg, Right, those are likely unrelated. Just an indication that it might just be one of those days
[14:30] <bjf> apw, i think bug 1098378 should be on your radar
[14:30] <ubot2> Launchpad bug 1098378 in linux (Ubuntu Raring) "chroot+overlayfs seems to cause umount mis-behavior" [High,Confirmed] https://launchpad.net/bugs/1098378
[14:30] <smb> Oh, maybe the failure inside the guest actually is related to udev, too... "cannot open /dev/null" (twice) and "mounting none on /dev/pts failed"...
[14:48] <apw> bjf, ta
[14:52] <jsalisbury> **
[14:52] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:52] <jsalisbury> **
[14:53] <bjf> apw, you are most welcome
[15:25] <rtg> apw, rtg@gomeisa:~/r/kern$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-raring.git
[15:25] <rtg> Cloning into 'ubuntu-raring'...
[15:25] <rtg> remote: error: Could not read bce134d73d6d2bc23aeea1d32e559f11e61b8958
[15:25] <rtg> remote: fatal: bad tree object bce134d73d6d2bc23aeea1d32e559f11e61b8958
[15:25] <rtg> remote: aborting due to possible repository corruption on the remote side.
[15:25] <rtg> fatal: early EOF
[15:25] <rtg> fatal: index-pack failed
[15:27] <apw> rtg, eep
[15:27] <rtg> apw, yeah. I think my local repo is up to date.
[15:38] <smb> have we recently moved some other repo to archive?
[15:39] <smb> (iow could it be that weird --reference badness again)
[16:07] <apw> smb, no i think this is actually because we started using linux.git on there as a rewind tree, a nono with this setup
[16:08] <apw> rtg, i think i have it repaired, you might want to try recloning, i am letting fsck finish again, if it is clean then i will repack the repo without an alternative
[16:08] <rtg> apw, ack
[16:08] <apw> bjf, sconklin, henrix, your raring master repo is unhappy, i am working on it
[16:08] <sconklin> apw: ack
[16:08] <bjf> ack
[16:09] <smb> apw, Hm, and I thought Linus repo as alternative would always be safe
[16:10] <apw> smb, it would be _if_ we weren't putting stable in it, which has 'pending' branches which are rebased; bad
[16:10] <smb> apw, eew
[16:11] <apw> smb, yeah, and that expalins the objects which have gone, they are blobs and trees which would have been common on patches in another branch
[16:12] <smb> Sounds like we should give up --reference as long as git allows us
[16:27] <bjf> apw, i'm totaly confused why we would be using the "stable" tree (linux.git) as a reference to _any_ of our repos
[16:27] <bjf> apw, that just seems so wrong
[16:30] <rtg> bjf, I don't think it started out being the stable tree
[16:31] <bjf> rtg, ack
[16:32] <rtg> hmm, 'Failed to execute /init' is a real problem. v3.10-rc3 is kind of a fail.
[16:47] <rtg> apw, is your git fsync done ?
[16:51] <jsalisbury> ##
[16:51] <jsalisbury> ## Kernel team meeting in 10 minutes
[16:51] <jsalisbury> ##
[16:52] <infinity> smb: You might be right.
[16:54] <smb> infinity, Looking at the changelog, Daviey thinks I need to get TechBoarded anyway
[17:07] <apw> rtg, bjf,  sconklin, ubuntu-raring looks to be in good shape now; i have separated it from the linux.git repo now so we should be safe going forward
[17:07] <apw> rtg, i am just checking saucy which has the same linkage
[17:07] <sconklin> ack, thanks
[17:07] <rtg> apw, yep, cloned it a bit ago with no problems
[17:07] <bjf> apw, ack, thanks
[17:08] <apw> smb, did i see that the issue with devtmpfs was a systemd/udevd issue?
[17:09] <smb> apw, for the installer part yes
[17:09] <rtg> apw, ok to push saucy master-next ?
[17:09] <smb> some script from debian rather using tmpfs not devtmpfs
[17:23] <sconklin> apw:  do I need to clone raring fresh?
[17:23]  * rtg -> lunch
[17:40] <apw> sconklin, nope, it should be fine if you have a copy
[17:40] <sconklin> ok, too late :-)
[17:40] <apw> sconklin, it was the central copy which was missing an object or two; now restored
[20:30]  * rtg -> EOD