=== bladernr_ is now known as bladernr_afk
[07:21] <_ruben> guys, do you have some doc describing how to create/build/maintain your own kernel flavour (i'm looking at creating -server variant which includes the scst patches (scst.sf.net))?
[07:23] <vwj> hey guys I have a question about how to create a bug ticket against the latest precise kernel (linux-image-3.2.0-22-generic) which generates a oops during startup if the machine is used as a XEN host
[07:27] <vwj> the problem has been confirmed on the kernel mailing list (http://www.spinics.net/lists/kernel/msg1321449.html) and if I intsall linux-image-3.2.13-030213-generic which is older then the current stock kernel the problem is not there
[07:28] <vwj> note that the issue is introduced in kernel 3.2.14 which is possibly the base for the stock precise kernel
[07:42] <ppisati> moin
[08:12]  * ppisati -> back in ~10
[10:26] <luc4> Hi! Anyone who noticed crashes of various applications with the last released kernel?
=== bladernr_afk is now known as bladernr_
[14:18] <luc4> Hi! Anyone who noticed crashes of various applications with the last released kernel?
[14:23] <bjf> luc4, if you are talking about oneiric, then yes, we have a new kernel that is about to go into -proposed
[14:30] <luc4> bjf: yes, oneiric 3.0.0-18. Everything is segfaulting with that. Now I switched back to 3.0.0-16 and it seems to be ok so far.
[14:31] <bjf> luc4: ok, a new one should be available shortly
[14:31] <luc4> bjf: thank you very much!
[14:40]  * ppisati -> rush out for an errand, be right back
[14:59] <ppetraki> vanhoof, ayan: got ayan's ping, answered him privately. My wiki is pretty good, could stand to be integrated into the public wiki/debugging section
[15:12] <bjf> ppetraki: a link from somewhere in the wiki.ubuntu.com/Kernel briar patch would be good
[15:26] <Amoz> ogasawara :)
[15:26] <ogasawara> \o/
[15:27] <jsalisbury> Amoz, o/
[15:27] <ogasawara> jsalisbury: Amoz has informed me they are interested in helping with the kernel...I thought a good place to start is triage work to get a feel for the workflow etc.
[15:28] <jsalisbury> Amoz, triage is a great place to start, and we can always use the help :-D
[15:28] <Amoz> i always find it hard starting out triaging stuff though
[15:28] <ogasawara> jsalisbury: I was hoping you could maybe help point him in the right direction to get started
[15:28] <jsalisbury> ogasawara, sure thing.
[15:29] <jsalisbury> Amoz, This is a great first place to start: https://wiki.ubuntu.com/Kernel/BugTriage
[15:29] <jsalisbury> Amoz, There are some good pages there, but some may be out of date.
[15:30] <ogasawara> Amoz: there is also pretty good info off of wiki.ubuntu.com/Kernel for development too if that interests you more...
[15:31] <ogasawara> Amoz: or even testing is helpful, eg testing of -proposed kernels
[15:32] <Amoz> ogasawara, that I can do!
[15:32] <Amoz> I think I've read the kernel triaging stuff before
[15:33] <Amoz> it still feels like a hard thing to do.. the triaging I mean
[15:33] <Amoz> one can't learn to triage kernel bugs just by reading some docs, right?
[15:33] <jsalisbury> Amoz, we're always here to help and answer questions.
[15:33] <ppetraki> bjf, ayan, vanhoof: https://wiki.ubuntu.com/Kernel/Systemtap , lets have some fun :)
[15:33] <Amoz> that will be a million of questions then jsalisbury 
[15:34] <jsalisbury> Amoz, by testing, you may come across new bugs.  That can be a good start into triaging
[15:34] <ogasawara> Amoz: there's a general process, but there are always deviations
[15:34] <ogasawara> jsalisbury: +1 on that
[15:34] <Amoz> yeah I need to start somewhere, I guess
[15:35] <martinphone> any new 3.0.0.18 that doesnt segfault my xubuntu installation when I load parole (media player)?
[15:35] <jsalisbury> Amoz, If you test and find a new bug, I can guide you through the triage process.  That will help you see the full process.
[15:39] <Amoz> jsalisbury, that'd be great. so for testing proposed kernels on precise, I'll just change a source ?
[15:39] <Amoz> in sources.lists
[15:40] <jsalisbury> Amoz, There is a wiki on how to do it.  Let me find it.
[15:40] <Amoz> I think I found it jsalisbury 
[15:40] <jsalisbury> Amoz, cool
[15:40] <Amoz> but it's applicable on precise as well?
[15:41] <Amoz> even though it's in development phase
[15:41] <jsalisbury> Amoz, well not really for precise, since the latest kernel is always similar to proposed for stable kernels
[15:43] <jsalisbury> Amoz, just running the latest precise kernel, and applying updates regularly is a great way to test.
[15:43] <Amoz> great
[15:44] <jsalisbury> Amoz, I think there is a list of test cases on the QA wiki.  I'll take a look.
[15:45] <jsalisbury> Amoz, here is a wiki if your looking for specific test cases to try while running the -proposed or latest development kernels:
[15:45] <jsalisbury> Amoz, http://testcases.qa.ubuntu.com/
=== Nafallo_ is now known as Nafallo
[15:51] <Amoz> jsalisbury, my Asus u36sd doesn't hibernate/sleep because of some usb3 bug. Is it worth reporting? or is it the manufacturer's fault (driver etc.) ?
[15:53] <jsalisbury> Amoz, absolutely 
[15:56] <Amoz> jsalisbury, there's a fix documented here https://help.ubuntu.com/community/Asus_U36SD
[15:56] <Amoz> jsalisbury, is that possible to get working OOTB?
[15:58] <jsalisbury> Amoz, possibly.  The first thing to do would be to open a kernel bug.  We can then see if the bug also exists upstream.  If it does, we can open an upstream bug.  If the bug is fixed upstream, we can look at getting it pulled into Precise.
[15:58] <jsalisbury> Amoz, The first step is to open a bug in launchpad
[15:58] <Amoz> I'll check if it is
[16:00] <dileks> hi
[16:00] <Amoz> jsalisbury, is this where all kernel bugs are? v
[16:00] <Amoz> https://bugs.launchpad.net/ubuntu/+source/linux
[16:00] <dileks> drm/i915: suspend fbdev device around suspend/hibernate
[16:00] <dileks> is that included in latest precise-kernel?
[16:04] <jsalisbury> Amoz, yes that is all the open bugs
[16:04] <dileks> http://thread.gmane.org/gmane.linux.kernel/1274203
[16:05] <Amoz> jsalisbury, should I try to get a strace or something of the crash?
[16:05] <jsalisbury> Amoz, the first step would be to open a new bug with: apport-collect linux
[16:06] <jsalisbury> Amoz, That will collect a good amount of logs and debug information to get started.  Based off that, we can see what additional data is needed.
[16:07] <Amoz> jsalisbury, I see. thanks :)
[16:07] <jsalisbury> np
[16:59] <Sarvatt> dileks: yep its in 3.2.0-22.35
[17:01] <dileks> Sarvatt: OK, thanks. lemme check kernel here
[17:50] <Amoz> jsalisbury, bug filed :)
[19:57] <beata> Hm. I checked out Ubuntu-3.2.0-22.35 just a moment ago; it has debian.master/abi/3.2.0-21.34/