[01:32] <susu> hi everyone..
[01:33] <susu> I got a problem about linux kernel modules debug...
[01:33] <susu> my kernel module dead sometimes,not always,and I just can't get the reason.
[01:35] <susu> I want to know how I can I make the debug tools like kgdb, and I make my module working, when the bug happend ,the debug tools interrupt the kernel module, and display the debug info.like the function call trace
[01:36] <susu> is there any debug tools can do this?
[05:15] <shadeslayer> Hi! I was wondering if the intel dual lvds channel patch is going to be applied in the 3.6 kernel ... that's the only thing that's remaining to get proper graphics driver support on my machine
[09:15] <ogra_> hmm, seems ppisati forgot to enable the LDE driver again in the new omap4 kernel
[09:15] <ogra_> *LED
[09:39]  * cking gets jenkins + autotests working nicely and grabs a coffee 
[10:52] <brendand> what's  a normal figure for wakeups p/s in powertop?
[11:23] <cking> brendand, it depends on the system
[11:24] <cking> ..and what it is doing
[11:33]  * henrix -> lunch
[12:04] <brendand> cking, well is 300 high?
[12:06] <apw> brendand, did that kernel work?
[12:06] <cking> brendand, as I said, it depends - on what it is doing, the system config, devices etc, desktop or server install.. etc
[12:08] <brendand> apw - the one you asked me to try? i didn't try it because jwi said it's definitely not the same issue
[12:10] <apw> might be worth seeing if it is a contribution to the issue
[12:24] <alexbligh> Any idea how I can mount a block device (iscsi if that matters) and avoid the kernel processing the partition table and creating the minor devices? Would be happy disabling partition handling entirely.
[12:48] <henrix> psivaa: could you please take a look at bug #1036178?
[12:48] <ubot2`> Launchpad bug 1036178 in linux "linux: 3.0.0-25.41 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1036178
[12:48] <henrix> psivaa: looks like you have set regression-testing task to 'fix released' but forgot to tag it
[12:49] <psivaa> henrix, i think i did, let me double check
[12:49] <henrix> psivaa: thanks
[12:51] <psivaa> henrix, yes, the tag did not get applied, apologies,
[12:51] <psivaa> henrix, is that ok if i add this now?#
[12:52] <henrix> psivaa: yes, sure. just tag it and set the status of the task again
[12:52] <psivaa> henrix, thanks, will do
[12:52] <henrix> psivaa: also, please set 'kernel-sru-workflow' to 'in progress' again :)
[12:53] <psivaa> henrix, ack
[12:53] <henrix> psivaa: the bot will set it to 'incomplete' if it fails to find the tag
[12:53] <henrix> psivaa: thanks
[12:55] <psivaa> henrix, just did it, thanks
[12:55] <henrix> psivaa: great, thanks a lot
[12:56] <psivaa> henrix, yw
[14:04] <dholbach> hey
[14:04] <dholbach> could http://paste.ubuntu.com/1177876/ indicate a hardware problem?
[14:10] <dholbach> could it be a memory issue?
[14:21] <cwillu_at_work> how would one go about getting a line number out of a repeatable oops ("unable to handle kernel null pointer deref at (none)")?
[14:21] <cwillu_at_work> http://permalink.gmane.org/gmane.comp.file-systems.btrfs/19461
[14:21] <dileks> dholbach: what ubuntu-release?
[14:23] <dholbach> dileks, 12.04
[14:23] <dholbach> dileks, it seems like the machine is also getting quite hot, 73°C was last I saw
[14:24]  * dileks loves hot bare metal
[14:24]  * cwillu_at_work loves hot bare metal in his kitchens, not his offices
[14:25] <dholbach> I think I'd agree with cwillu_at_work on this one :)
[14:25] <dileks> IIRC there is a newer ubuntu-kernel around for precise
[14:26] <apw> dholbach, well that your machine is getting hot would fit with it spinning like mad waiting on a lock, nothing to indicate its h/w specificially
[14:27] <dileks> dholbach: tried a mainline or q-lts kernel?
[14:27] <dholbach> it's a windows machine of a friend, which after a 'repair shop' still had the same problems, so I put Ubuntu on it to try to find the issue
[14:28] <dileks> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.28-precise/
[14:28] <dileks> https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport/+packages
[16:41] <rbasak> When is linux precise-proposed currently due to land in -updates? Is it this weekend?
[16:41] <rbasak> -proposed publication date is 2012-08-25
[16:41] <henrix> rbasak: no, not during the weekend. it should be on Monday
[16:42] <rbasak> OK, thanks. I'll leave what I'm doing now since using -proposed is awkward for me. I'll just wait for -updates :)
[16:42]  * henrix will be out for a bit
[17:05] <infinity> bjf: I thought the SRU bot wasn't supposed to set the updates promotion tasks on Fridays?
[17:06] <infinity> bjf: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036178 was changed 4h ago, which seems Fridayish to me.
[17:06] <ubot2`> Ubuntu bug 1036178 in linux "linux: 3.0.0-25.41 -proposed tracker" [Medium,In progress]
[17:06] <bjf> herton, ^
[17:07] <infinity> Hrm.  We also still don't have a new ti-omap4 in precise to match master.
[17:07] <herton> infinity, it changes the tasks until 18:00 utc
[17:07] <herton> on friday
[17:07] <herton> let me check
[17:07] <infinity> herton: Ahh.  I misunderstood.  I thought it wouldn't set them on Fridays at all, because we didn't want to release on Fridays.
[17:08] <herton> yeah, 4h ago still matches this criteira
[17:08] <herton> infinity, it was agreed, but we could set the time back further if needed
[17:08] <herton> or avoid friday at all
[17:09] <infinity> herton: I'm not wildly picky, it's you guys that have to respond if I release something on a Friday that breaks.  So, really, it's more your call.
[17:10] <infinity> (Though, if we desperately break things and need to involve a crisis response team, it drags in a bunch of people on a (long) weekend).
[17:10] <herton> infinity, about ti-omap4, ppisati who does it is on vacation. Perhaps I could try to rebase and build the package, but not sure if it's important enough to not wait
[17:11] <infinity> herton: Well, the bug/regression is such that I won't release the current ti-omap4.  So, either we get them in sync, or ti-omap4 just misses an SRU cycle.
[17:11] <infinity> herton: The rebase is trivial, if you'd like to do it.
[17:14] <herton> infinity, thinking here I'm gonna proceed and do the rebase. The previous bug is already closed as duplicate against new one, and sure the current -proposed shouldn't go out.
[17:16] <infinity> herton: Indeed.  If/when you do it, feel free to just go ahead and do the copy too, it won't need NEW processing, since it's not an ABI bump.
[17:16] <herton> ack
[17:16] <infinity> herton: (I can check later tonight or tomorrow that everything looks sane from my POV)
[17:19] <infinity> Woohoo.  arm64 is making the 3.7 merge window.
[18:34]  * henrix -> eod
[19:22]  * cking -> EOD