[06:07] <Book_em_Dano> My pc is displaying a "soft-lockup detected on CPU#1..." error message which halts the bootup process, how can I resolve this?
[06:38] <BenC> Book_em_Dano: file a bug report with the full message of the lockup…take a pic if needed
[07:26] <smb> morning
[07:26] <apw> morning
[07:32] <abogani> morning
[13:54]  * ogasawara back in 20
[15:13] <ogasawara> apw: I thought we were going to disable compcache?
[15:13] <apw> ogasawara, and in better news I have also gotten it working again i think
[15:13] <apw> ogasawara, we were talking about removing the ramzswap ubuntu/compcache) yes
[15:14] <apw> though it was still being used by casper.  welll actually as i discovered its not working at
[15:14] <apw> all in natty cause the casper bits just don't work at all
[15:14] <apw> and that explains why our minimum memory supported had to be bumped in natty
[15:14] <apw> (i bet)
[15:14] <apw> anyhow ... i am about to push you some patches with ramzswap reverted as its broken beyond belief
[15:15] <ogasawara> apw: ack
[15:15] <apw> and as i've had to fix casper i've fixed it to support zram instead which is a staging driver in the main kernel
[15:15] <apw> </end nig
[15:15] <apw> </end nightmare>
[15:16] <ogasawara> apw: do we want to get a beta freeze exception for this and upload?
[15:17] <apw> ogasawara, oh no i see no need to doing anything before b1 as the casper userspace is so broken than it simply cannnot corectly load the driver anyhow
[15:17] <apw> which is good else smoke pours out :)
[15:17] <ogasawara> heh
[15:17] <apw> and we released with this broke without noticing for natty :/
[15:33] <cking> quality
[15:45] <apw> cking, assured
[15:46] <cking> right
[16:07] <apw> ogasawara, if ramzswap made it into P please zap it there
[16:07] <ogasawara> apw: ack
[16:08] <apw> ogasawara, i've just pushed the drop of ramzswap given its completely fooked anyhow
[16:08] <apw> makes no difference if its in
[16:08] <ogasawara> apw: cool, thanks
[16:08] <apw> ogasawara, now we wait on foundations to review their side so we can get the functionality back
[16:23] <tgardner> apw, do you need to diddle the modules bits in debian.master/abi after reverting compcache  ?
[16:24] <apw> tgardner, ahh yeah must have to... let me unf*ck that
[16:24] <tgardner> apw, I haven't built it yet, just was wondering
[16:25] <apw> tgardner, thats what happens when you remove it and test and fix and build, and then decide to revert instead
[16:26] <tgardner> apw, should likely do the same for ubuntu-p
[16:26] <apw> tgardner, ogasawara is on the case for p
[16:26] <ogasawara> apw: yep, I'll fix up p
[16:27] <tgardner> same with all the config settings ?
[16:27] <apw> they go naturally but i am commiting anyhow
[16:27] <ogasawara> yep, am working on syncing all my config changes right now
[16:27] <tgardner> cool. I'll just crawl back into my hole now.
[16:29] <apw> tgardner, ok that should be better now
[16:30] <tgardner> apw, wfm
[17:50]  * tgardner --> lunch
[18:38] <jdstrand> kees: hey. I'm looking at this: http://www.openwall.com/lists/oss-security/2011/08/15/3. can you verify if oneiric is affected? based on dates alone, I am thinking not, but want to be sure
[18:39] <kees> jdstrand: oh, ew. I will check
[18:39] <jdstrand> thanks
[18:39] <jdstrand> kees: fyi, I've also got some new kernel CVEs coming in, but it'll be a few minutes before I check them in
[18:40] <kees> okay, cool
[18:41] <kees> jdstrand: yeah, oneiric is fine. we're already carrying the fixes
[18:41] <kees> 1ae2a2c0515870d784f1ea101b079bd0962b6cd5 and 8b180803c66ccc825d2969c1ea9929fcb7fba98e in our tree
[18:41] <jdstrand> cool :)
[18:50] <shbk> hello,does anybody have experience with compiling of modules for kernel?   I've described problem detailed here : http://gekannt.narod2.ru/       .thanks in advance
[18:50] <shbk> I have headers : sh@sh-laptop:~$ uname -r
[18:50] <shbk> 2.6.32-33-generic
[18:51] <shbk> I can't find  linux/module.h, but linux/kernel.h is
[18:56] <shbk> I read that I should compile kernel  yourself
[18:57] <shbk> but there are opinions that I shouldn't and that it's enough only headers
[18:59] <shbk> but there is something wrong, I don't know,  should I at first compile kernel?
[19:00] <shbk> I can  explain this as my precompiled ubuntu 10.04 hasn't source code , so I should  compile it or 
[19:00] <shbk> can I just put source in /usr/src folder?
[19:01] <shbk> if I do  find /  -name *module.h   I receive:
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33-generic/include/linux/module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/drivers/media/dvb/frontends/s921_module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/arch/sparc/include/asm/module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/arch/mips/include/asm/module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/arch/xtensa/include/asm/module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/arch/h8300/include/asm/module.h
[19:01] <shbk> /usr/src/linux-headers-2.6.32-33/arch/mn10300/include/asm/module.h
[19:03] <shbk> ooops, sorry 
[19:03] <shbk> so I'm confused what to do
[19:04] <shbk> I asked on #ubuntu , #ubuntu-devel, but they sent me to here
[19:43] <jdstrand> kees: ok, finished checking in the new CVEs, there are several new kernel ones, including Kaminsky's tcp seq one
[19:51] <kees> jdstrand: ok, thanks