[08:31] <lag> Morning apw
[08:37] <apw> lag y
[08:37] <apw> lag, yeah morning, sorta
[08:38] <lag> apw: Sorta? Still up from last night?
[08:39] <apw> lag more sorta up, its been a long week
[08:39] <lag> apw: You're still in bed? :)
[08:39] <apw> having to get up at 8 on a sunday and go to work is not the best cure for tiredness
[08:39] <apw> heh
[08:40] <lag> Yeah, that sucks :)
[08:40] <lag> How did it all go though?
[08:40] <lag> Everyone looks happy enough in the photos 
[08:40] <apw> still i think it all went out near to hitch free, as near as sometihng that complex can ever be so i suspect
[08:41] <apw> though trying to even sync an iso today is taking hours, so i assume we are being hammered to death still
[08:41] <lag> That's a good thing :)
[08:41] <lag> Mo' users
[08:42] <apw> i am seeing about 25KB/s from here, and i can smell the DC from here
[08:42] <apw> so i assume we are red-lining all our b/w
[08:42] <lag> :)
[08:42] <lag> So what now?
[08:43] <apw> a lazy day for me for sure
[08:45] <lag> And for the rest of us saps?
[08:51] <apw> heh *crack* back to digging out the ore
[08:52] <apw> this is the slack time, there is a lull between now and UDS where we start to think about what we are going to do
[08:52] <apw> and we start the sprint again
[08:53] <lag> Okay
[08:53] <lag> I guess I'll just crack on with my bugs then
[09:29] <cking_> where's the URL to the kernel related blueprints for natty?
[09:37] <tgardner> cking_, apw was messing with that stuff earlier last week
[09:39] <apw> cking_, they are likely all lost now as someone renamed them
[09:39] <apw> let me find them
[09:43] <apw> cking_, https://blueprints.edge.launchpad.net/sprints/uds-n?searchtext=kernel
[09:43] <cking_> apw, ta
[09:43] <apw> cking_, all of them are on that page, many have hardware-prefix, a couple have other-
[09:43] <apw> new fun track prefixes
[09:43] <apw> that messes up all my links gah
[09:47] <cking_> is there any naming scheme being used - looks a little ad-hoc to me
[09:50] <smb> cking_, yes <random name>-<your track name<
[09:53] <cking_> smb, what's our official "track name" then?
[09:54] <smb> cking_, whatever they think could match. I don't think it was a single track that apw found
[09:54] <cking_> gah
[09:55] <apw> cking_, yep the tracks are 'ideas' oriented this time not team oriented
[09:56] <apw> so like cloud, hardware, etc
[09:57] <cking_> fwts falls into hardware I suppose,
[09:57] <apw> i guess
[10:00] <cking_> smb, I see a lot of the blueprints named "hardware-kernel-n-some-title" - doesn't that conflict with <random name>-<your track name> as you mentioned earlier. I'm confused
[10:02] <smb> cking_, Are you always taking me up to the word?
[10:02] <smb> It was more of an impression
[10:03] <smb> I yet have to find my blueprints again to even know what they changed them into
[10:03] <smb> cking_, There was a mail by jcastro where he was telling the scheme I think
[10:04] <cking_> ah, /me looks
[10:17] <diwic> how do I export a single commit with git format-patch? if I just do "git format-patch abcdef" it'll take everything from abcdef+1 to HEAD, which is not what I want.
[10:18] <smb> diwic, with -1
[10:18] <smb> git format-patch <sha1> -1
[10:19] <diwic> smb, thanks. Strange, this was not documented on "git help format-patch"
[10:21] <smb> diwic, Likely it is hidden somewhere in git-rev-parse in a very unovious way
[10:21] <smb> diwic, I usually found a "ask apw" much more effective
[10:22] <apw> diwic, git format-patch -1 <commit>
[10:22] <apw> diwic, or git format-patch <commit-A>..<commit-B>
[10:23] <apw> (where A is before the range as normal)
[10:24] <diwic> apw, right, could have done git format-patch abcdef^..abcdef as well
[10:24] <apw> yep
[10:24] <apw> -N is easiest for small values of N
[10:24] <diwic> aha, so abcdef -2 will take abcdef and abcdef+1? 
[10:25] <cking_> apw, when registering a blueprint I'm asked "For:" ..(The project for which this proposal is being made.". If I put in "ubuntu" LP complains that there are too many matches on this keyword. How did you fill in this field?
[10:26] <apw> cking_, for as in project, thats ubuntu
[10:29] <apw> cking_, pretty sure that i just typed it in and moved on
[10:29] <apw> cking_, yeah just shove in the text ubuntu and move to the next field, the searchy thing blows a sprocket
[10:29] <cking_> argh, it's now lost it *again*. LP time outs are getting me crosser by the moment
[10:30] <lag> Who will do the ti-omap4 packaging for natty?
[11:02] <cking_> Blueprint saga now complete·
[11:08] <apw> cking_, how many am i looking for ?
[11:09] <cking_> apw, just one, I've been wrestling with other things too, it's been a background task for this morning
[13:38] <jcastro> smb: $track-$team-n-$title is the format
[17:46] <ogasawara> vanhoof: are you working today?
[17:47] <ogasawara> vanhoof: I assumed you'd be recovering from jet lag and observing the holiday anyways
[17:50] <lag> ogasawara: Congratulations :)
[17:50] <ogasawara> lag: thanks :)
[17:51] <lag> What's next?
[17:52] <ogasawara> lag: world domination
[17:52] <lag> Sounds like you're up to it 
[18:28] <bo> hi people
[18:28] <bo> i wonder why on ubuntu/debian nouveau on recent (nvidia gt230m and 310m) cards i get a black screen on boot
[18:29] <bo> while on fedora it works great since lots of months
[18:29] <bo> it's a problem related to some of debian/ubuntu kernel patches?
[18:31] <vanhoof> ogasawara: kinda sorta, we're on holiday :)
[18:31] <vanhoof> ogasawara: wanted to get that tested though, gonna head out to lunch
[18:32] <ogasawara> vanhoof: am gonna build you another test kernel with those additional suspend related looking patches.  But don't test it till tomorrow and just enjoy the rest of your day.
[18:33] <vanhoof> ogasawara: kk :)
[18:33] <apw> bo it may be a firware issue, or lacking of patches ... we'd want a bug filed from the machine
[18:33] <apw> ogasawara, morning ...
[18:33] <apw> looks like its all gone out ok ... congrats on your first born
[18:34] <ogasawara> apw: heh, hopefully baby #2 will be just as painless
[18:34] <apw> ogasawara, heh i bet you do :)
[18:37] <bo> apw: now i'm on fedora, how can i report a bug in a machine with a black screen from the first second of boot? (but not freezed, in fact i heard the gdm sound)
[18:37] <apw> bo, fair enough then
[18:38] <bo> on fedora-kernel they told me that they don't ship any nouveau code that isn't upstream
[18:38] <bo> i don't know if it's a kernel problem or whatelse!
[18:38] <apw> bo and what kernel version is fedora shipping
[18:39] <apw> most likely a combination between that and the mesa
[18:39] <bo> now, 2.6.35.6-39.fc14.x86_64... but it works with many past fedora kernel
[18:41] <bo> there are a lot of forum topic on this problem, i tought it was a card problem, but some months ago i find that on fedora worked
[18:41] <apw> bo, and you were testing lucid or maverick
[18:42] <bo> didn't work on both
[18:42] <bo> and also on debian alpha
[18:44] <apw> whats the card bo ?
[18:44] <bo> before maverick i used closed driver, and a put on xorg the EDID file description path, 
[18:44] <bo> and the it worked
[18:44] <bo> so maybe it isn't related to nouveau
[18:44] <apw> yet nouveau works on fedora
[18:45] <apw> bo, what nvidia card ?
[18:45] <bo> 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 230M] (rev a2) (prog-if 00 [VGA controller])
[18:46] <apw> RAOF, Sarvatt, know anything about noveau not working with the above card on maverick ?
[18:47] <apw> bo i assume your testing was on the live CD image as you are on fedora ?
[18:47] <bo> no, now i installed fedora
[18:48] <bo> cause on lucid i managed to have graphic with closed driver and EDID file on xorg
[18:48] <bo> in maverick it doesn't work
[18:49] <apw> bo, how long ago did you switch away, ie. when did you last test maverick
[18:49] <bo> it works just with vesa 
[18:49] <bo> i tested maverick yesterday
[18:50] <bo> i use fedora since august
[18:50] <bo> yesterday i tried to come back on ubuntu
[18:51] <bo> before these months I always used ubuntu o debian with closed driver
[18:55] <apw> bo, thanks
[18:55] <bo> now i remember that i can connect the notebook to my tv via hdmi, in this configuration i DO see things on video
[18:55] <bo> and i can report bug
[18:56] <apw> so you should be able to do that via the liveCD at least
[18:56] <bo> yes
[18:56] <bo> now it seem to me just a monitor problem
[18:57] <apw> we may be able to tell that from the info in the bug
[18:57] <bo> what kind of infos do you need?
[18:57] <bo> i mean a log or whatelse?
[18:57] <apw> perhaps fedora has edid hacks, which would be common to all drivers and not specific to edid
[18:58] <apw> bo id you file a bug against the xorg driver nouveau we should get the kernel drm information too
[18:59] <bo> so i'll ask to fedora team i they've done an hack!
[18:59] <bo> sorry, how can i see kernel drm info? kernel.log?
[19:02] <apw> /sys/kernel/debug/dri
[19:02] <bo> ok, thanks, i have to go now, see you later
[19:03] <apw> and /sys/class/drm/card0-*
[19:03] <bo> (i'll read later)
[19:25] <Edgan> abogani: What is your gpg key ID?
[19:25] <Edgan> abogani: nm
[20:01] <vanhoof> ogasawara: i know i shouldn't be working, but i couldnt resist :)
[20:01] <vanhoof> ogasawara: success w/ v2
[20:01]  * vanhoof updates thread
[20:01] <ogasawara> vanhoof: sweet, I'll build one more to narrow it down between the two
[20:02] <ogasawara> vanhoof: but seriously, don't feel the need to test it till tomorrow
[20:02] <vanhoof> ogasawara: you keep sending them, i'll keep testing :)
[20:02] <vanhoof> ogasawara: im just ignoring everything else in my inbox atm ;D
[20:03] <vanhoof> but i do feel its time for a nap lol
[21:17] <maxb> Hi, I need some debugging help
[21:18] <maxb> Maverick kernels occasionally seem to malfunction on my box, manifesting as system monitor graphs showing the CPUs very busy with system time
[21:18] <maxb> top shows nothing - how can I trace which kernel task is to blame?
[21:31] <freetz> 10.04 appears to have KSM enabled, but I can't get madvise() to return success on when I pass the MADV_MERGEABLE flag
[21:31] <freetz> anyone else use KSM successfully?
[21:36] <stgraber> AFAIK kvm uses it and I seem to remember seeing over 500MB of merged pages on some boxes (running libvirt with kvm)
[21:37] <soren> freetz: What error do you get?
[21:37] <freetz> einval
[21:37] <freetz> which should only be returned if ksm is disabled
[21:37] <soren> freetz: Stock maverick kernel?
[21:37] <soren> freetz: Oh, sorry, 10.04, you say.
[21:38] <stgraber> root@chopin:~# cat /sys/kernel/mm/ksm/pages_shared 
[21:38] <stgraber> 136582
[21:40] <stgraber> (10.04.1 on 2.6.32-24-generic 64bit)
[21:42] <freetz> yes
[21:43] <freetz> grep KSM /boot/config-2.6.32-25-generic
[21:43] <freetz> returns CONFIG_KSM=y
[21:43] <freetz> i get that too for pages_shared
[21:43] <freetz> i enable ksmd by setting /sys/kernel/mm/ksm/run = 1
[21:44] <soren> madvise will also return EINVAL if your addr arg isn't page-aligned.
[21:45] <freetz> hmm, i'll check on that real quick
[21:45] <vanhoof> ogasawara: v4 ftw
[21:45]  * vanhoof grabs a beer
[21:46] <soren> freetz: That's really (AFAICT) all it can be. madvise doesn't give EINVAL if you don't have ksm enabled, only if you haven't compiled it in at all.
[21:46] <freetz> isn't valloc deprecated?
[21:46] <freetz> or is there a better way to ask for page aligned memory
[21:47] <ogasawara> vanhoof: \o/
[21:47] <soren> memalign
[21:47] <soren> freetz: ^
[21:47] <freetz> woop just saw that...
[21:49] <soren> QEMu (which I /know/ succesfully uses KSM) uses posix_memalign to ensure properly aligned pages.
[21:49] <soren> fwiw.