[05:11] <ivan> why does https://insights.ubuntu.com/2017/04/05/ubuntu-on-aws-gets-serious-performance-boost-with-aws-tuned-kernel/ mention "Disabled CONFIG_NO_HZ_FULL to eliminate deadlocks on some instance types" when it's already N / unset in ubuntu-xenial.git:master?
[13:36] <mvo> hey sforshee - apw send me your way. I was looking at the testsuite failure of snapd with the latest zesty kernel from proposed. we have some tests that excercise the seccomp filtering. it looks like with the kernel from -proposed we don't get messages like http://paste.ubuntu.com/24327651/ anymore in dmesg which makes the tests fail
[13:37] <mvo> sforshee: let me know if I can do anything to help with that issue
[13:37] <sforshee> mvo: yeah I've been looking, unfortunately the snapd tests have been broken for so long I can't tell when this first started happening :-(
[13:38] <sforshee> mvo: do you know if this happens with the kernel in -release?
[13:38] <sforshee> mvo: and what's the easiest way to reproduce the problem?
[13:41] <mvo> sforshee: its fine with the kernel in release
[13:41] <mvo> sforshee: its broken with the kernel in -proposed
[13:44] <mvo> sforshee: easiest (for me, ymmv) is git clone https://github.com/snapcore/snapd ; cd snapd/cmd; ./autogen.sh; make check
[13:45] <mvo> sforshee: let me know if that does not work for you, you may need to do "sudo apt build-dep snapd" first
[13:45] <mvo> sforshee: but the C parts are light on dependencies so it may work without
[13:45] <mvo> sforshee: there are three tests failing with the new kernel, they all do dmesg|tail -n1|grep "audit"
[13:47] <sforshee> mvo: thanks, I'll see what I can find
[13:47] <jdstrand> mvo: curious if ratelimiting is getting in the way
[13:47] <jdstrand> mvo: note my (now ancient) mknod PR had a bunch of testsuite improvements in this area
[13:48] <jdstrand> mvo: are we at a point where we can consider that PR (and the other seccomp arg filtering PRs) again?
[13:48] <jdstrand> mvo: afaik, we still need this: https://github.com/snapcore/snapd/pull/2810
[13:48] <mvo> jdstrand: re rate-limiting> I think not, I don't see any audit message at all in dmesg
[13:49] <mvo> jdstrand: the mknod is close, we still need #3027 first but that one is close, it looks there there is agreement
[13:49] <jdstrand> mvo: well, that could be a sympton. the kernel is funny like that sometimes
[13:50] <jdstrand> mvo: ok, cool. I'll keep an eye on 3027. will that be the pr instead of 2810?
[13:51] <mvo> jdstrand: yes, that is the new direction(the second new direction actually)
[13:51] <mvo> jdstrand: but close finally :)
[13:52] <jdstrand> mvo: great to hear :) thanks! :)
[16:00] <ad-n770> do you have any estimated date on when the 4.10 kernel will land into Ubuntu 16.04 repositories as linux-image-generic-hwe-16.04-edge ?
[16:08] <infinity> ad-n770: Two days ago.
[16:11] <ad-n770> oh, it's there
[16:11] <ad-n770> going to try it
[16:58] <ad-n770> we had participated in the tracking and fixing of an issue affecting drm/radeon that causes a system lockup under certain loads
[16:58] <ad-n770> the fix is at https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.9&id=03df14330dd6a6cfa91964131e001c1ca58a380f
[16:59] <ad-n770> what should be the procedure to request it to be backported into Ubuntu 16.04 4.4 kernels ?
[17:01] <tjaalton> clone ubuntu-xenial.git, backport the patch, send the patch to the list. and file a bug for it, reference it in the patch
[17:02] <tjaalton> or, ask mrcooper to send it to stable@vger
[17:02] <tjaalton> takes a bit longer to reach 4.4 though
[17:35] <ad-n770> thanks
[17:37] <ad-n770> tjaalton: could please be more specific in which list we should send the patch ?
[17:39] <tjaalton> kernel-team@
[17:41] <tjaalton> https://wiki.ubuntu.com/Kernel/Dev/KernelPatches
[19:14] <ad-n770> thanks