[05:00] Zero hour. [05:03] Core temperature high. Is there a boot time kernel param to force powersave cpufreq? [05:04] New initscrips and rc.local echos do not work. [05:18] ZagfeO New initscrips and rc.local echos do not work. [05:38] Trippeh New initscrips and rc.local echos do not work. [06:30] Zyga New initscrips and rc.local echos do not work. [06:30] Lone i? [07:26] Ara New initscrips and rc.local echos do not work. [07:32] these_eyes: hey, what's up? [07:34] Hello zyga. [07:34] Remodeling. [07:36] The host is overheating and attempts to make powersave frequency governor default have not been effective. [07:39] So far I've made init scripts using the default on demand script and subbing in powersave. Also adding the echo to the appropriate sys settings file in rc.local. Neither show effect. However the echo powersave works when run manually. [07:45] these_eyes: sorry, can you work with ara [07:45] I cannot spare cycles now [07:46] these_eyes, what system are you running? and what version of Ubuntu? [07:47] these_eyes, I would recommend you to file a bug using "ubuntu-bug linux". That will upload all the required logs and the ubuntu kernel team will be able to investigate it [07:48] I expect it to enter the cpu into powersave mode as it does when used manually from command line the settings look fragmented as though the configuration is done with some gui using more complicated methods some combination of things that interact with init scripts so trying rc.local is a simple alternative and even it doesn't work. [07:50] Work with ara sure do you know where ara come from? I have a guess. [07:51] Memtest is showing problems on another machine running an older kernel. [07:52] So ara comes in. [07:52] these_eyes, sorry? [07:53] Ara sorry for what? [07:53] these_eyes, I mean, sorry as I don't understand what you are saying :) [07:54] It looks intentional. Sorry is usually not a response for intentional aras. [07:57] I notice the memory tests as bad but is not bad memory I can test it using another memtest and check but while that is happening I want the other machine to run cooler. [07:57] Find out how to set powersave as default cpufreq. === lan3y is now known as Laney [08:04] Ok ara? === Laney is now known as Guest61035 === Guest61035 is now known as Laney [08:06] Hello, does anyone know how to do 'modprobe uio' on ubuntu trusty? [08:06] these_eyes, it should also switch to powersave about 20s after boot [08:07] these_eyes, we default to performance to improve boot speed [08:08] or I don't need to modprobe uio, it's already in kernel 3.13~ ? [08:12] debian.master/config/config.common.ubuntu:CONFIG_UIO=m [08:12] looks to be a module [08:14] apw: thx thx [08:16] xianghui, might be uio-pci-generic you are looking for [08:19] smb: hmm, didn't find uio-pci-generic, seems it's in kernel 3.13.0-63-generic default, thx. [11:14] Hi, I was wondering if this fix made it into any release kernel yet: [11:14] http://bitsup.blogspot.ch/2015/09/thanks-google-tcp-team-for-open-source.html [11:18] data, i know it is applied but not uploaded for wily, and as it is dave.miller i would expect it to go to stables is possible [11:19] ok great. we have some benchmarks where we always assumed that it was our wonky code, but I am putting some hope into this ;) Where can I find information like this? [11:24] data, information like what ? [11:25] which patches are applied? [11:45] data, our git repositories are the ultimate definition of waht is applied [13:17] apw: Would you have a chance to review the proposal for a fix for LP: #1496317 ? [13:17] Launchpad bug 1496317 in kexec-tools (Ubuntu) "kexec fails with OOM killer with the current crashkernel=128 value" [High,In progress] https://launchpad.net/bugs/1496317 [13:18] apw: or maybe I can ask to someone in the server team. But you already know the context [15:06] caribou, cna do, do chase me if i don't today [15:06] apw: debdiff is in the patch. I'll ping you by tomorrow morning if I don't hear anything [15:07] apw: thanks! [15:42] query sconklin [16:58] arges, hi there. [16:59] arges, I understand that 1487085 is queued for this upcoming SRU for 3.19, right? [17:01] leitao, yup, should be out in the next day or so [17:02] by "out", I mean promoted to -updates [17:02] leitao: what rtg said : ) [17:02] rtg, cool. And the SRu cycle is a traditional 3 weeks cycle, right? [17:03] leitao, generally. The stable team (in the form of bjf) publishes a schedule about every three weeks. [17:03] leitao: https://lists.ubuntu.com/mailman/listinfo/kernel-sru-announce this list announces cycle dates, and yes typically it is 3 week intervals [17:03] good. Thank you guys! === swordsmanz is now known as hugbot === hugbot is now known as swordsmanz === adrian is now known as alvesadrian