[14:56] <nvez-> Hello everyone.. I have identified a bug that has regressed (few other people reported it). I created a new bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435363
[14:58] <apw> henrix, ^
[14:58] <henrix> looking...
[15:00] <henrix> nvez-: there's a new kernel in -proposed that should be released soon... have you tried it?
[15:01] <nvez-> henrix: I haven't tried anything yet, I just wanted to make sure to get the ball rolling on it by starting first steps of opening a bug, etc.
[15:01] <nvez-> I just saw the same exact behaviour when I first had that bug, made that change and it's worked fine now.
[15:02] <nvez-> made that change = disable KSM
[15:02] <henrix> ack
[15:02] <nvez-> I haven't done more in depth testing but I think servers running mdraid are affected but those with hardware weren't
[15:02] <nvez-> But don't quote me on that yet, it's just something I've noticed but don't have 100% confirmation on
[15:03] <nvez-> The iowait was insanely high on mdraid machines for no reason, but hardware had no issues.  I didn't check if they were affected or not.
[15:39] <infinity> henrix: The "new kernel in proposed" is in updates/security.
[15:43] <mnaser> sorry, i disappeared.. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435363
[15:43] <mnaser> added data here
[15:43] <mnaser> i'll look at the proposed kernel if i can run it on a server and replicate
[15:44] <henrix> infinity: ack, thanks
[15:44] <henrix> mnaser: looks like the kernel is now in -updates (and security)
[15:46] <infinity> mnaser: Just a simple update/dist-upgrade should get you -48 ... Would be worth seeing if the bug's still there.
[15:46] <mnaser> henrix: just out of curiosity, are you proposing to upgrade just to see if its still there, or because it was patched/seen?
[15:46] <mnaser> oh ok
[15:47] <mnaser> henrix i might be making noise..
[15:47] <mnaser> the server which i suspect was seing most of the issues
[15:47] <henrix> mnaser: i was simply wondering if the issue was fixed in the new kernel
[15:47] <mnaser> was running 3.13.0-32-generic
[15:48] <henrix> mnaser: ah, that's a much older kernel...
[15:48] <mnaser> *sigh* i guess this machine wasnt updated
[15:48] <mnaser> let me do some more checks :X
[15:48] <mnaser> i'm very sorry about this if this is the case
[15:49] <henrix> mnaser: yeah, i was looking at the bug logs and i see a few ooops there, so i would definitely upgrade and see what happens with a newer kernel
[15:50] <mnaser> nope i can confirm
[15:51] <mnaser> this issue exists on a machine running 3.13.0-46-generic
[15:52] <mnaser> i'll be setting up a new machine either today or tomororw
[15:52] <mnaser> similar specs
[15:52] <mnaser> ill tets it out
[15:52] <mnaser> *test it out
[15:56] <henrix> mnaser: ack, thanks.  please update the bug report with those results (and the logs)
[15:56] <mnaser> good idea
[15:56] <mnaser> can i just run apport again?
[15:56] <henrix> mnaser: or, if it's easier for you, just open a new bug and simply mark this one as a dup ;)
[15:57] <henrix> mnaser: yes, re-running apport should do be enough (i guess...)
[15:57] <mnaser> i'll remove the logs i uploaded there
[15:57] <mnaser> just in case that someone looks over itagaina
[15:57] <mnaser> and dismisses it because they see -33
[16:00] <apw> df
[16:02] <smb> apw, you use too much space
[16:02] <apw> smb, always
[16:04] <mnaser> henrix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1435363 bug updated
[16:11] <henrix> mnaser: ack, thanks.  i'll have a look in a bit
[16:35] <henrix> mnaser: is the bug easily reproducible?  if so, could you add the steps to reproduce in the bug report?
[16:36] <henrix> mnaser: probably, it's a perf degradation, right?  or do you actually see a crash/hang...?
[18:55] <Sleaker> I'm curious what the linux-lts-utopic package is for, and what the benefit of moving to the 3.16 kernel over the 3.13 provides.
[18:56] <Sleaker> oh maybe I found it on the 14.04 section of the Ubuntu wiki under Kernels.
[18:56] <Sleaker> support cycle for 3.13 is the full 5 yrs and the 3.16 is only 18 months
[19:00] <infinity> Sleaker: It's purely for hardware enablement reasons.  If 3.13 is working for you, there's no reason to use the HWE kernel(s).
[19:01] <Sleaker> infinity: alright, thanks.  do the point releases come with the newer kernel preinstalled?
[19:01] <Sleaker> like 14.04.2
[19:01] <apw> yes
[19:03] <infinity> Sleaker: Depending on what media you install from, but yes.
[19:04] <Sleaker> infinity: hmm ok. Seems odd for canonical to not support the default install media for as long as the LTS is valid.
[19:06] <Sleaker> thanks for the answers though, that's what I needed.
[19:07] <infinity> Sleaker: When 16.04 ships, we strongly encourage (and tools yell at you) people using one of the HWE kernels to upgrade to the 16.04 lts backport kernel, which is supported for the rest of 14.04.
[19:07] <infinity> Sleaker: It's just the interim ones we drop support for.
[19:07] <Sleaker> right.
[19:07] <infinity> Sleaker: For instance, on 12.04, the 12.10, 13.04, and 13.10 kernels are no longer supported, but the 12.04 (3.2) and 14.04 (3.13) kernels are supported until 12.04 EOL.
[19:07] <Sleaker> just seems odd to ship a kernel that wont be supported across the full release but label it as such.
[19:08] <Sleaker> ie, 14.04.2 ships the 3.16kernel, but support gets dropped after 18 months, wheras the full release is supported long past that?
[19:08] <infinity> Sleaker: You're not the only person who thinks that.  Many of us are just cogs trying to make do with the requirements given to us. ;)
[19:08] <Sleaker> mhmmm
[19:08] <Sleaker> just glad I didn't get that kernel in atm.
[19:08] <Sleaker> :D
[19:09] <Sleaker> hopefully don't need it for the new hardware we'll be testing on either.
[20:09] <mnaser> henrix: sorry, went afk, ill update more details on how i identify the issue
[21:44] <backjlack> Hello!
[21:44] <backjlack> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.9-vivid/ is missing MEMCG configuration.
[21:45] <backjlack> The entire memory cgroup is missing.