tag:blogger.com,1999:blog-6469704299235308349.post9034990783880038768..comments2024-03-28T15:50:13.644+11:00Comments on -ck hacking: linux-4.16-ck1, MuQSS version 0.171 for linux-4.16ckhttp://www.blogger.com/profile/02904761195451530213noreply@blogger.comBlogger36125tag:blogger.com,1999:blog-6469704299235308349.post-49921040911067897812018-08-27T04:06:31.095+10:002018-08-27T04:06:31.095+10:00Just for reference purposes; the issue, as it turn...Just for reference purposes; the issue, as it turned out, is related to BFQ (the IO scheduler).<br /><br />100% confirmed.<br /><br />It is simply not production ready. And not sure it ever will be. It just keeps getting worse actually. A year ago it performed just as well WITHOUT crashing.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87394285830732248792018-08-21T10:08:02.825+10:002018-08-21T10:08:02.825+10:00So many of you might need the help of a hacker to ...So many of you might need the help of a hacker to do a job.<br /><br /><br /><br />But most of you haven't be able to meet one. Well at The Hack geeks, we provide you with the best hacking services there is.<br /><br />We have hackers in stand by ready to do a job immediately at your pace.<br /><br /><br /><br />Contact: <br /><br />thehackgeeks@gmail.com<br /><br />We look forward to hearing from you.Bernard Ryanhttps://www.blogger.com/profile/00917621710878038704noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-26425611663893152782018-07-30T05:03:32.686+10:002018-07-30T05:03:32.686+10:00Hey, i'm using a linux server(CPU E3-1231 v3 @...Hey, i'm using a linux server(CPU E3-1231 v3 @ 3.40GHz, 4 core - 8 thread) to host a private game server and my question is if this kernel patch may help my server to have a better latency in the gameplay?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-66322115857863164992018-07-23T18:21:04.489+10:002018-07-23T18:21:04.489+10:00Wow really good information ! keep up the great wo...Wow really good information ! keep up the great work!<br /><br /><a href="https://vegas99.bet/category/prediksi-bola/" rel="nofollow">Prediksi Bola</a><br /><a href="https://daftarjudionline.win/bandar-daftar-togel-online/" rel="nofollow">Bandar Datar Judi Togel</a><br /><a href="https://vegas99bet.win/situs-judi-roulette-online-terpercaya/" rel="nofollow">Situs Judi Roulette Terpercaya</a><br /><a href="http://vegas99bet.org/" rel="nofollow">Agen Casino SBOBET</a>vegas99bethttps://www.blogger.com/profile/01550666163502268458noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-10318656737176920112018-07-10T19:20:02.268+10:002018-07-10T19:20:02.268+10:00Just in case people were curious, here's anoth...Just in case people were curious, here's another update:<br /><br />It is not hardware at all... not even remotely. It's a bug in BFQ. Finally saw the kernel panic floating by (no log was ever recorded for it though, just happened to be in one of the virtual TTY's when it happened, so no desktop manager was in the way of me seeing the kernel panic).<br /><br />"kernel panic in blahblahblah/bfq_sq/iosched.c" or words to that effect.<br /><br />End of the line for Liquorix for me. End of the line for BFQ for me. Apparently it is still in too rough of a shape to be relied upon.<br /><br />Back to stock. So, no more MuQSS either. Sadly. Because I really fell in love with it. It is lightyears ahead of CFS.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-36101317919310315042018-06-27T12:08:30.712+10:002018-06-27T12:08:30.712+10:004.16.17 & 4.16.18 didnt boot here. Early crash...4.16.17 & 4.16.18 didnt boot here. Early crash within 0.3s. 4.16.16 working fine though.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87165333174500377862018-06-26T20:37:28.626+10:002018-06-26T20:37:28.626+10:00Hi Con,
First of all thank you very much.
Linux ha...Hi Con,<br />First of all thank you very much.<br />Linux has been way more fun for me because of your work.<br />Since 4.16 is EOL now, are there 4.17 patches in the making?<br /><br />Best regards,<br />AnonymousAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-62121481536465213982018-06-21T05:35:11.303+10:002018-06-21T05:35:11.303+10:004.16.16-ck1 panics or hangs at "Sharing SMP r...4.16.16-ck1 panics or hangs at "Sharing SMP runqueue from CPU 3 to CPU0" in virtualbox 5.2.12 vm.<br />Might boot after like 5 tries or more.<br />config https://pastebin.com/raw/dqKm9MvWAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-76512875701364387412018-06-03T23:17:17.789+10:002018-06-03T23:17:17.789+10:00CK, I have a static IP and domain with 5 Megabit u...CK, I have a static IP and domain with 5 Megabit upload. I'd like to offer to mirror your materia for free (I'm not hosting anything else). Are you interested? If so, send an SMS to 0438 470 680KHolznoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-61162192096018829292018-05-30T06:38:19.490+10:002018-05-30T06:38:19.490+10:00@Enih -- As per Con's own entry for this versi...@Enih -- As per Con's own entry for this version of MuQSS -- Threaded IRQ were defaulted to off. And, besides, this problem never occurred before. I'd have expected a problem to occur long, long ago if that was the problem. The PC is years old and I've been using Linux for years on it as well. This problem never occurred until quite recently.<br /><br />@Anonymous -- Running oom would not cause the entire system to completely seize up. The Linux kernel is a bit more sophisticated than that, it will, at one point or another, start aggressively killing applications just to keep running. No joke, it will.<br /><br />Anyhow, traced the issue -- It's hardware. Specifically, it seemed to have been an overheating issue. It has been rather warm lately and apparently the PC just needed a good cleaning. Been running very stable for hours now after I gave it a quick once-over.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-21566270976409455172018-05-30T04:27:19.184+10:002018-05-30T04:27:19.184+10:00If you got no swap and disabled oom maybe you run ...If you got no swap and disabled oom maybe you run out of memory?<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-56071796732857366522018-05-30T00:15:49.075+10:002018-05-30T00:15:49.075+10:00Good news: MuQSS is not the cause. Stock kernel an...Good news: MuQSS is not the cause. Stock kernel and configuration also displayed this behaviour.<br /><br />Bad news: Something is really wrong. Going to have to look elsewhere. Not inclined to point to a hardware issue though, as it mostly seems to occur when context switching between tasks and putting memory pressure on the box by having an array of heavy applications open is no guarantee. So, probably not memory. And if it had been the CPU, I'd have expected it to fail to boot. I'd be expecting kernel panics if it had been hardware.<br /><br />Anyhow, nothing to see here, sorry to have cried wolf over... well, something that is unrelated to MuQSS.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-4367103291617372082018-05-30T00:04:36.291+10:002018-05-30T00:04:36.291+10:00rqshare=none did nothing to resolve the issue; sti...rqshare=none did nothing to resolve the issue; still experiencing complete deadlocks. And no mention of any warning or error or panic in any of the logs in /var/log. Not even in kern.log, which should be the one that is always being updated.<br /><br />Implying the kernel is really deadlocking hard.<br /><br />Trying a completely stock kernel and configuration now.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-58318136116460866432018-05-29T22:58:18.221+10:002018-05-29T22:58:18.221+10:00Ever since this version of MuQSS I have been havin...Ever since this version of MuQSS I have been having complete lockups; initially I figured it to have been WINE since it seemed to only occur when using that.<br /><br />But just now, it also happened after having completely removed WINE. Another theory was Chromium but it also did occur at least once without having a single instance of Chromium running.<br /><br />Having discounted all other variables over time by now, all I can say is that the sole constant is this new version of MuQSS.<br /><br />This is on an AMD A6-3650.<br /><br />Was running rqshare=mc, going to try rqshare=none now to see if that resolves the issue. If not, I am going to try to see what happens if I run the stock kernel (so, no MuQSS at all).<br /><br />I'd hate for it to truly be related to MuQSS though, it is such an amazing scheduler.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-32556520277268153712018-05-24T21:16:15.369+10:002018-05-24T21:16:15.369+10:00yes.
i was refering to "the system will be al...yes.<br />i was refering to "the system will be almost twice as slow." though.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-55800926274316119992018-05-24T06:17:26.843+10:002018-05-24T06:17:26.843+10:00https://en.wikipedia.org/wiki/Hyper-threading
&quo...https://en.wikipedia.org/wiki/Hyper-threading<br />"For each processor core that is physically present, the operating system addresses two virtual (logical) cores and shares the workload between them when possible."fidajhttps://www.blogger.com/profile/11667278719546201906noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-78913024045813617522018-05-24T03:41:51.472+10:002018-05-24T03:41:51.472+10:00the real number of cores is at least twice as smal...the real number of cores is at least twice as small as the number of cores with HT - the system will be almost twice as slow.fidajhttps://www.blogger.com/profile/11667278719546201906noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-59714002882762136212018-05-23T23:23:05.585+10:002018-05-23T23:23:05.585+10:00bad advice?bad advice?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-14492713172839575072018-05-23T22:08:19.586+10:002018-05-23T22:08:19.586+10:00why are you giving bad advice?why are you giving bad advice?fidajhttps://www.blogger.com/profile/11667278719546201906noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87487461495353558762018-05-23T20:25:41.477+10:002018-05-23T20:25:41.477+10:00fail^ maxcpus=xfail^ maxcpus=xAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-16366211985097203022018-05-23T20:24:38.421+10:002018-05-23T20:24:38.421+10:00Use maxcpus= kernel parameter, where x is # of rea...Use maxcpus= kernel parameter, where x is # of real cores.<br />HT sucks anyway.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-10568781554080429132018-05-15T04:25:10.672+10:002018-05-15T04:25:10.672+10:00Hi Con,
Compile error on 32 bit Pentium 4:
CC ...Hi Con,<br /><br />Compile error on 32 bit Pentium 4:<br /><br /> CC kernel/sched/MuQSS.o<br />In file included from kernel/sched/MuQSS.c:73:0:<br />kernel/sched/MuQSS.h:739:46: warning: ‘struct sched_domain’ declared inside parameter list will not be visible outside of this definition or declaration<br /> unsigned long arch_scale_cpu_capacity(struct sched_domain *sd, int cpu)<br /> ^~~~~~~~~~~~<br />kernel/sched/MuQSS.h: In function ‘arch_scale_cpu_capacity’:<br />kernel/sched/MuQSS.h:741:15: error: dereferencing pointer to incomplete type ‘struct sched_domain’<br /> if (sd && (sd->flags & SD_SHARE_CPUCAPACITY) && (sd->span_weight > 1))<br /> ^~<br />kernel/sched/MuQSS.h:741:25: error: ‘SD_SHARE_CPUCAPACITY’ undeclared (first use in this function)<br /> if (sd && (sd->flags & SD_SHARE_CPUCAPACITY) && (sd->span_weight > 1))<br /> ^~~~~~~~~~~~~~~~~~~~<br />kernel/sched/MuQSS.h:741:25: note: each undeclared identifier is reported only once for each function it appears in<br /><br />Kernel is 4.16.8, only your patch is added. But the same with zen Kernel.<br /><br />Old 4.15 muqss was working fine.<br />Thanks.<br /><br />Regards sysitosAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-67792702650497276882018-05-10T19:24:01.629+10:002018-05-10T19:24:01.629+10:00Most of the time, yes, though there is variance in...Most of the time, yes, though there is variance in results too, so repeating the tests is almost important if something suddenly looks much better or much worse.Con Kolivashttps://www.blogger.com/profile/05355844537881606702noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-55233167832598659792018-05-10T19:22:03.510+10:002018-05-10T19:22:03.510+10:00Thanks for answering.
So could these tools be used...Thanks for answering.<br />So could these tools be used for regression testing between MuQSS releases ?<br />I don't know if the internals change that much between MuQSS and mainline releases.<br /><br />PedroAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-23113390075094806232018-05-09T07:13:47.326+10:002018-05-09T07:13:47.326+10:00Any tools that hook into function calls in the ker...Any tools that hook into function calls in the kernel are simply not going to work as the function names and purposes are different in muqss. As for interbench results, it is a fairness test as well as a latency test so looking for just the lowest latency as some kind of perfect endpoint will give you the wrong conclusion.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.com