[12:27] <visi> Hi everybody
[12:28] <visi> Is this a good place to ask a Karmic koala kernel related problem?
[12:38] <amitk> visi: yes
[12:40] <visi> I have raised a bug manualy in the launchpad but so far no comment/assignment etc. so I was wondering that someone could take a quick look (probably 5 mins) and change the assignment/team etc. settings if I did something wrong.
[13:09] <visi> I feel a bit "stupid" that I don't see here any conversation.... like a monolog by myself. Am I here in the wrong time or something?
[13:14] <soren> a long time can go by without anyone saying anything. 
[13:14] <soren> ...and until you tell us which bug you're talking about, that's not likely to change a whole lot. :)
[13:15] <visi> Well Thanks :-) So the bug is: https://bugs.launchpad.net/bugs/452175
[13:15] <ubot3> Malone bug 452175 in linux "Random segfaults when using ld.so explicitly to start a program" [Undecided,New] 
[13:18] <amitk> visi: most of the kernel team is sprinting currently (and yes it is a little early in the US)
[13:19] <visi> Just wondering: Is the kernel team in the US? I somehow had the idea that it is either in London or everybody works from there home...
[13:20] <amitk> visi: it is spread out, but _currently_ they are in the same location in the US
[13:21] <visi> Ok.
[13:22] <amitk> visi: you script seems to be working for me on a x86-64 bit karmic machine
[13:22] <amitk> *your
[13:22] <amitk> how long does it take to trigger the problem?
[13:23] <visi> well within 10sec. it should produce.
[13:23] <visi> I have not tested under 64 bit. It could be different there too.
[13:24] <amitk> I haven't managed to trigger it under 64 bit
[13:26] <visi> My testmachine has now 32bit 2.6.31-14-generic #48-Ubuntu and it is still does.
[13:26] <visi> Can you please still check that the bug assignment to team etc. are correct?
[13:31] <amitk> visi: I _can_ reproduce it on my 32-bit laptop
[13:31] <visi> Good, than I am not alone... ;-)
[13:32] <amitk> It could be several things from the top of my head - hardening gcc flags, apparmor, bash, etc.
[13:33] <amitk> I've commented on the bug and increased its priority a bit
[13:34] <visi> Well as I have described in the bug report, I recompiled under the same system the latest stable kernel and it was working without those errors. So I feel this is rather kernel related.
[13:35] <visi> A big THANKS for your effort <amitk>.
[13:44] <amitk> visi: this is most certainly an upstream bash bug.
[13:44] <amitk> try replacing /bin/bash with /bin/dash
[13:53] <visi> Ok. I see the problem is not coming up with /bin/dash. I still have to confirm that this workaround is working for us...
[14:13] <mzeal> can someone advise what the deal is with changing INIT_WORK and DECLARE_WORK from 3 arguments to 2?
[15:10] <JFo> pgraner, FYI: no joy finding a link in the local participation for hotel/room accommodations.
[15:31] <pgraner> JFo: just a sec
[15:32] <JFo> k, no rush
[15:58] <Keybuk>  EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
[15:58] <Keybuk>      Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
[15:58] <Keybuk>      Might be a BIOS bug, if BIOS says ECC is enabled
[15:58] <Keybuk>      Use of the override can cause unknown side effects.
[15:58] <Keybuk> hmm
[15:58] <Keybuk> karmic's kernel is grumpy
=== thunderstruck is now known as gnomefreak
[19:45] <virtuald> http://www.kerneloops.org/submitresult.php?number=837280
[19:46] <virtuald> got this when i plugged my webcam
[19:46] <virtuald> while i was talking to my sister and brother on msn (telepathy) and skype
[19:49] <Kano> hi, where is the 2.6.31.5 rebase?
=== MTeck-ricer is now known as MTecknology
[23:25] <dtchen> thankfully quite a few of these mic issues are resolved with a combination of the latest alsa-utils upload and linux-backports-modules-alsa-karmic
=== cking is now known as cking-afk