=== ming is now known as Guest38993
=== ming is now known as Guest90227
=== ghostcube_ is now known as ghostcube
=== ghostcube_ is now known as ghostcube
=== ghostcube_ is now known as ghostcube
=== ghostcube_ is now known as ghostcube
=== ghostcube_ is now known as ghostcube
[15:09] <cwillu_at_work> the mainline images install and work fine without kmod (which is expected and sane).  Could someone fix the deps to consider the old package to be a valid alternative so that silly --force-depends tricks can be avoided when using the mainline kernel builds to test if issues are fixed in mainline?
[15:09] <cwillu_at_work> kthxbye
[18:30] <Kano> hi, where is the wily git?
[18:31] <rtg> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily
[18:33] <Kano> nice you rebased it already
[18:37] <Kano> do you patch the kernel for active skylake support?
[18:40] <rtg> I can't remember doing anything special for skylake yet
[18:40] <Kano> i think it is only active with 4.3
[18:41] <rtg> tjaalton has some patches the he'd like pulled, but I'm gonna wait until they are merged in 4.3
[19:41] <pepee> hi. this bug seems to be present in the kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359766 . I'm running 3.19.0-26-generic (from linux-image-generic-lts-vivid), I don't have a swap file/partition, and while the OOM killer was working in 3.16 (IIRC), it hasn't worked for me in months
[19:41] <ubot5> Ubuntu bug 1359766 in linux (Ubuntu) "Kernel fails to execute code for killing OOM task if oom_kill_allocating_task = 0" [Medium,Fix released]
[19:42] <pepee> btw, what was the fix? how come lp.net doesn't even show that info?
[19:42] <pepee> also, is this bug ubuntu-specific? if so, why are you guys patching things that should "just work"?
=== JanC_ is now known as JanC
[21:21] <infinity> pepee: The submitter closed the bug claiming it was fixed in 3.13.0-35, the changelog has some 'mm' commits that might relate: https://launchpad.net/ubuntu/+source/linux/3.13.0-35.62
[21:22] <infinity> pepee: And no, that wouldn't be an Ubuntu-specific bug.
[21:22] <infinity> pepee: It's also pretty unlikely that a bug reported (and reported fixed) on 3.13 is the same as what you're seeing on 3.19, but "the OOM killer doesn't work right" is a pretty vague description of a bug.
[21:24] <pepee> infinity, well, the description in this case would be: with a OOM situation and vm.oom_kill_allocating_task set to 1, the system won't kill the program, and instead just keep the disk spinning. but it seems to be exactly the same bug
[21:25] <pepee> now I remember, 3.13 isn't supported anymore, except by ubuntu IIRC...
[21:25] <infinity> pepee: Ergo, it's supported.
[21:25] <infinity> pepee: But your bug is in 3.19, not 3.13, so not sure how that relates.
[21:26] <pepee> infinity, sure, but then, all bugs in 3.13 are ubuntu specific, heh
[21:26] <infinity> pepee: Also, your description is the exact opposite of the bug you linked, no?
[21:26] <pepee> in the bug I linked they use vm.oom_kill_allocating_task=0
[21:27] <infinity> pepee: Yes, and you said it fails if it's =1
[21:27] <infinity> pepee: Anyhow, please file a bug and describe in more detail how to reproduce, etc.
[21:27] <pepee> but the description looks similar, disk spinning when it shouldn't
[21:27] <infinity> pepee: Yeah, any number of kernel bugs could lead to that situation, though.  Similar symptom != same bug.
[21:28] <infinity> Though I wish the world were that simple.
[21:28] <pepee> infinity, ah, ok, thanks for your help. I'll report later
[21:28] <pepee> well, the bug report doesn't mention any other specific info, so...
[21:31] <infinity> Right, the first report is pretty lacking too. :P
[21:31] <infinity> Sadly.