=== timchen1` is now known as timchen119 === shirgall is now known as Guest4271 === shirgall is now known as Guest5617 [14:31] apw, rtg: hey, which branch shall I use to have code included in 16.04? master-next? [14:31] tseliot, you should base pull-requests on master-next yes [14:31] apw: ok, thanks [14:32] tseliot, i don't suppose i want to know what this vomit it, but if it is what i expect then we'll want a bug for it please to tie the gazillion commits together === Ursinha_ is now known as Ursinha [14:33] apw: it's all (upstreamed) open source code for amdgpu, and yes, I can file a bug report about it [14:33] tseliot, that'd be lovely, put the buglink in all the commits please too, [14:33] apw: sure === leftyfb is now known as _leftyfb === _leftyfb is now known as leftyfb [16:10] rtg, apw looks like the patches to support http://is.gd/0GhbMU are in 4.1/4.2 any idea if we have this feature in xenial ? [16:13] manjo, i have not, i'd refer you to slangasek or whoever is working it [16:13] yeah [16:13] I will check with slangasek [17:43] is there a way to set isolcpus without rebooting and change the cmdline? [17:43] I need to exclude several cores from the scheduler [17:47] it depends what that actually does, does it unplug them or just ignore them [17:47] apw: was that for me? [17:48] niluje, yes [17:49] I want to ignore them [17:49] I have a DPDK application that calls setaffinity to use four cores [17:49] I dont want something else to run on these cores [17:51] niluje, anyhow the only thing that appears to update that is the early kernel parmeter, so i suspect not [17:53] :( [17:53] thanks a lot apw [18:16] apw: sforshee; so cgroup namespaces are now in linux-next. Do I nee dto do anything to request them going into xenial kernel? (I assume so...) just an email to ubuntu kernel list? [18:48] hallyn and they need to be in before tomorrow, so dont wait [18:49] apw: don't wait with what? [18:49] email to kernel list? [18:49] or something else? Pull request? [18:49] (i guess i used the wrong list last week and earlier this week) [18:58] hallyn: kernel-team@lists.ubuntu.com [19:01] arges: thanks, just sent it there [19:02] hallyn: it may help to have a pull-request of a tree where the specific patches are applied on top of hte xenial tree [19:02] or just [PATCH] emails ifs its short and they cleanly git am on xenial [19:02] arges: ... yeah, xenial is already pretty out of date so a pr may be worthwhile [19:02] grumble [19:03] i wonder whether my kernel.ubuntu.com git acct access is still valid - haven't used it since it migrated i dont' think [19:04] hallyn: i see a /home/serge on that machine [19:04] http://kernel.ubuntu.com/git/?ofs=500 should really provide a [from-to] range under each # at the bottom of the page :) [19:05] * hallyn shuts up before someone drafts him to web hack [19:05] arges: last touched 3 years ago :) [21:17] jsalisbury: next rock, pls? [21:18] lamont, ack, I'll let you knwo when the next one is ready [21:21] ta [22:21] jsalisbury: bad. next ? [22:26] lamont, ack [22:53] lamont, next kernel is ready [22:55] jsalisbury: should I be concerned that it's 4.2.0rc8 when the last known good was 4.3.0-7? [22:56] lamont, no, the naming is kind of weird. The last kernel was bad, so this build is now back in time [22:57] np [22:57] it just means that Ihave to actually interrupt the boot process and pick one [22:57] lamont, the bisect bounces around allot, especially when there are merges [22:57] ah [22:58] jsalisbury: good kernel. next? [22:58] lamont, great, I'll start the next build [23:00] jsalisbury: and not that we care, but one monitor is screaming about "Out of Range" [23:00] h 48.2KHz V 44.3Hz [23:01] (yes the one that disappears in the bad kernels) [23:01] there is just something satisfying about: sudo apt-get purge linux-image-$(uname -r) && reboot