[07:58] <tjaalton> ddebs.u.c doesn't have l-i-debug for 2.6.28-11, is there a way to build it myself?
[07:59] <tjaalton> (I'd like to use oprofile to find out what causes the extra load every ~15min)
[09:16] <vertix> vertix: for developers: check out http://cppgoldmine.uuuq.com programmer's goldmine library to find the answers on any of your issues or problems in C++
[09:19] <vertix> btw, no marketing or any other adds on those collections. it is totally clean site containing only articles in 100+ categories, nothing else
[16:56] <Kano> hi, still no aufs2 in there yet?
[16:56] <Kano> every other live cd is created via aufs(2) nowadays...
[16:58] <apw> Kano, heh, nope as strangly we have not yet had the UDS discussions on this matter, as they occur in a week
[16:59] <Kano> and you expect another result, do you
[17:01] <amitk> Kano: probably not, but who knows :)
[17:01] <Kano> thats basically impossible
[17:03] <amitk> Kano: but you welcome to attend the session at UDS where we discuss the issue
[17:03] <amitk> you can even dial in
[17:04] <Kano> the thing is, when you add aufs2 in the kernel + squashfs 4 userspace then your tools would already create working test images 
[20:53] <tjaalton> how can I build just the debug debs from the kernel source? been trying to do that, since there's no ddeb for 2.6.28-11
[20:54] <rtg> tjaalton: you pretty much have to build the whole damn thing in order to get the debug debs
[20:56] <tjaalton> rtg: right, so changing 0-common-vars.mk so that it doesn't skip ddeb's should be enough?
[20:56] <tjaalton> and then debuild -b?
[20:56] <rtg> tjaalton: you could just 'sudo mkdir /CurrentlyBuilding' as well
[20:57] <tjaalton> heh, ok
[20:57] <rtg> then 'debuild -b'
[20:57] <rtg> either way should work
[20:58] <tjaalton> ok, let's see
[20:59] <BenC> rtg: I think /CurrentlyBuilding is just a file, not a dir
[20:59] <BenC> but probably will still work
[20:59] <rtg> BenC: I think it can be either, make just looks at the wildcard, doesn't it?
[21:00] <BenC> rtg: yeah, I think it's just an existence test
[21:03] <awe> rtg: are then good pointers on the kernel team's wiki pages for debugging crashes / restarts?  my machine (mbpro3 / amd64 ) reboots an awful lot after updating to jaunty.
[21:03] <awe> s/then/there/
[21:04] <rtg> awe: cold boots with no warning?
[21:04] <awe> yea
[21:04] <awe> usually re-sizing windows, but not always
[21:04] <rtg> those are tough. 
[21:04] <rtg> awe: i915 ?
[21:04] <awe> nvida
[21:05] <awe> geforce 8600M GT
[21:05] <rtg> there is a section on debugging in https://wiki.ubuntu.com/KernelTeam/KnowledgeBase
[21:06] <awe> all i could find was the suspend/resume debugging page, but i'll look again
[21:06] <BenC> awe: using nvidia proprietary driver, or open source one?
[21:06] <awe> prop
[21:07] <rtg> awe: --> screwed
[21:07] <BenC> awe: best bet is to see if nvidia can help...I'd try switching to open source driver for a bit to see if it still happens though
[21:07] <awe> well, it's not like i wasn't told "it's recommended". ;)
[21:07] <awe> i'll switch back and see how that works...
[21:08] <rtg> awe: I've had to switch back to 2d before. the 3d driver was flickering and getting real annoying.
[21:09] <awe> alright, i'll give it a whirl
[21:09] <tjaalton> hmm, so my kernel (karmic) spends most of the time in read_hpet
[21:09] <infinity> rtg: It's definitely a file, not a directory.
[21:09] <rtg> infinity: the rule is 'ifeq ($(wildcard /CurrentlyBuilding),)'
[21:10] <infinity> rtg: Yeah, should work for anything, then.
[21:10] <infinity> rtg: Just pointing out that it's a file, should you ever do something with it in shell (say -f or -d)