salsbury | ping gnarface | 02:46 |
---|---|---|
gnarface | yo | 02:47 |
salsbury | hey | 02:48 |
salsbury | remember the kernel performance thing? | 02:48 |
gnarface | maybe, which one? | 02:48 |
salsbury | the 4.19.8 | 02:48 |
gnarface | gonna need more to go on. you're not the one who switched from nvidia 390 to 396 and it fixed the problem, were you? | 02:49 |
salsbury | ah no | 02:49 |
salsbury | I'm the one who noticed temperatures going up after booting a new kernel | 02:50 |
gnarface | oh, yea, i remember that part | 02:51 |
salsbury | I just wanted to say that I still don't know what happened here, or why it runs hotter now, but I've compiled 4.9.144 and the same thing happened. só it's not a 4.19.8 thing. it's a -->me<-- thing (as suspected) | 02:52 |
gnarface | oh but you're also the one who had the problem with the +350MB initrd.img, right? | 02:52 |
salsbury | now I'm back to ascii's 4.9.130 | 02:52 |
salsbury | yes! | 02:53 |
salsbury | thats me :D | 02:53 |
gnarface | i think it's wise to avoid Linus's personal build tree for your own daily use... | 02:53 |
salsbury | I managed to bring it down to 60mb though | 02:53 |
gnarface | wow that's still a lot | 02:53 |
salsbury | yeah... not ideal | 02:54 |
salsbury | why should I avoid linus's? | 02:54 |
gnarface | i would just expect it to be highly experimental | 02:54 |
salsbury | even longterm branches? | 02:55 |
gnarface | the configs for 4.9 that debian & devuan use are very well tested over the course of many years | 02:55 |
salsbury | hmmm, makes sense | 02:55 |
salsbury | but in my case, even using the ascii .config-4.9.0-8 to build the new 4.9.144, resulted in the same situation | 02:57 |
salsbury | maybe there's some special patches debian or devuan are using | 02:58 |
salsbury | right? | 02:58 |
gnarface | hmmm | 02:59 |
gnarface | debian is using patches | 02:59 |
gnarface | lots of them | 02:59 |
gnarface | and to be clear the devuan kernel is the same exact package | 03:00 |
salsbury | btw, do you know where I could find detailed docs on devuan's kernel building process? | 03:00 |
gnarface | these kernels aren't rebuilt at all | 03:00 |
gnarface | they're copied directly from debian, unaltered | 03:01 |
salsbury | oh I see | 03:01 |
gnarface | they're not even repackaged | 03:01 |
salsbury | that's interesting | 03:01 |
gnarface | only some of the ARM images have kernels built by devuan devs, but i am under the impression they worked hard to use the debian configs there too | 03:01 |
gnarface | (at least, as much as possible for hardware debian doesn't support) | 03:02 |
salsbury | I tried building a debian kernel but the building process is kind of weird. there's some python scripts to build the tarball ...but they depend on some debian modules that I don't have... I didn't try to get those python modules but now I think I will | 03:04 |
gnarface | there's more than one ways to do it | 03:04 |
salsbury | give it another shot | 03:04 |
gnarface | first get the source package with "apt-get source linux-image-[whatever]" then you should be able to just build it with make-kpkg | 03:05 |
gnarface | there's some debian-specific build script in the ./debian/ directory that can work, but it tends to choke on minor things like unrecognized patches and perfectly valid package names and stuff | 03:06 |
gnarface | you can get the build deps easily with "apt-get build-dep [package name]" and "apt-get build-essential" | 03:07 |
salsbury | with make-kpkg, can I still mess around with .config? | 03:07 |
gnarface | yea, you would still do menuconfig before make-kpkg | 03:07 |
salsbury | oh nice | 03:07 |
salsbury | on second thought... hmmm | 03:08 |
gnarface | ideally you wouldn't need to change much, if anything, if you're starting with a debian config | 03:09 |
salsbury | what I'd really like to do... would be to get linus's and apply the patches and configs myself... | 03:09 |
salsbury | hmmm | 03:10 |
salsbury | I mean, this is a purely academic endeavor :D | 03:11 |
gnarface | i did have one machine that just installing the amd64-microcode package to seemed to raise the idle temperatures | 03:12 |
gnarface | but even if that's happening to you, it's unrelated to the huge initrd.img size | 03:12 |
gnarface | i couldn't be too sure about that machine anyway because it had failing fans too | 03:13 |
salsbury | could be, the temp difference on idle is +10deg C | 03:14 |
gnarface | that's a lot | 03:14 |
salsbury | system is running at 39deg right now, I've got firefox running | 03:14 |
gnarface | i was seeing a difference of less than 5C | 03:15 |
gnarface | 2-4 | 03:15 |
gnarface | 39 doesn't seem outrageous | 03:15 |
gnarface | i'm at 35 now with firefox running | 03:15 |
salsbury | if I just let it idle, it goes down to 37deg | 03:15 |
gnarface | i know if i dusted the fan vents better it would go down to 34 | 03:15 |
salsbury | but on the compiled kernel, it idles at 47deg | 03:15 |
gnarface | that's a real puzzle, i wonder what changes | 03:16 |
salsbury | yeah | 03:16 |
gnarface | and you're sure it's still using the same cpu frequency governor by default for both kernels? | 03:16 |
salsbury | yep | 03:16 |
salsbury | it always defaults to powersave | 03:16 |
salsbury | but one thing I've noticed is that the temp jumps much faster | 03:17 |
salsbury | if I start a new process, it spikes about 3deg almost instantaneously. if I start something a bit heavier like firefox there's even a bigger spike | 03:19 |
salsbury | but it's always the same governor, same graphics driver (nouveau with bumblebeed) | 03:20 |
gnarface | hmm | 03:21 |
gnarface | did you ever try nouveau with dri_prime instead of bumblebee? | 03:21 |
salsbury | ohh and the funny thing is | 03:21 |
salsbury | if I force the fan speed to max, the temp still doesn't go down | 03:22 |
gnarface | hmmm | 03:22 |
gnarface | that makes me wonder if it's even reading the same sensor | 03:22 |
salsbury | havent tried dri_prime | 03:22 |
salsbury | it is | 03:22 |
salsbury | i checked them manually | 03:22 |
gnarface | damn | 03:22 |
salsbury | on /sys | 03:22 |
salsbury | I'm now inclined to believe there's some magic patches doing perf improvements | 03:25 |
salsbury | some non-configurable scheduler tweaks...something related to context switching | 03:28 |
salsbury | I'll give the debian kernel another try in a few days. | 03:34 |
* man_in_shack collapses | 14:56 | |
minnesotags1 | Ok. What am I doing wrong with the Devuan VM image? I created a virtual machine in virt-manager, gave it a name, and I guess I assumed that creates a new qcow2 image, but it doesn't? | 19:32 |
djph | sounds like making the disk is where you went wrong ... | 22:21 |
treeview | Curious, was ever there a Devuan Tails fork available? | 23:54 |
MinceR | yes, it's called heads | 23:55 |
treeview | BOOM! Thanks! Merry Christmas! | 23:56 |
MinceR | :) | 23:57 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!