tag:blogger.com,1999:blog-6469704299235308349.post3639451196627636873..comments2024-03-28T15:50:13.644+11:00Comments on -ck hacking: linux-4.8-ck8, MuQSS version 0.144ckhttp://www.blogger.com/profile/02904761195451530213noreply@blogger.comBlogger115125tag:blogger.com,1999:blog-6469704299235308349.post-20618589915265876192016-12-12T09:46:52.537+11:002016-12-12T09:46:52.537+11:00Sorry,
obviously very impatient :/
Sorry,<br />obviously very impatient :/<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87563165647941237692016-12-12T09:21:36.115+11:002016-12-12T09:21:36.115+11:00Just how impatient can someone be???Just how impatient can someone be???ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-13230065821038712772016-12-12T09:21:00.222+11:002016-12-12T09:21:00.222+11:00Thanks for 4.8-ck8.
How is 4.9 going on? :)Thanks for 4.8-ck8.<br />How is 4.9 going on? :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-64907910601710681162016-12-11T13:28:28.356+11:002016-12-11T13:28:28.356+11:00Xeon W3520 quadcore 2.66 GHz, 6 GB 1066 MHz RAM, n...Xeon W3520 quadcore 2.66 GHz, 6 GB 1066 MHz RAM, nvidia quadro 4000, samsung evo 850 250GB SSD, seagate 500GB HDD. Old Lenovo Thinkstation S20 but still good (enough).<br /><br />I suggest switching from O3 to O2 and all will be fine, well most of the time.<br />I had gcc produce microbugs even with plain O2 in rare cases.<br /><br />The O3 adventure went fine here, no problems (and faster in some cases) although I reverted to the above with O2 instead of O3 on the server for reliability.<br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-29471779068386084492016-12-11T09:37:09.026+11:002016-12-11T09:37:09.026+11:00The "-O3" option still remains erratic. ...The "-O3" option still remains erratic. Like Con wrote about low level bugs above. <br />On my system reboots or powerdowns get stuck before doing so.<br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-29984014905094352492016-12-10T09:04:31.233+11:002016-12-10T09:04:31.233+11:00I've reinstalled a very very old MESA known-go...I've reinstalled a very very old MESA known-good backup now. Same problem with flash.<br />Either the source server is misbehaving since some days or the recent firefox-esr update is trash.<br />The CFLAGS changes are not relevant for my problems, cross tested, but maybe for this subthread's original poster.<br /><br />@ck & @Florian:<br />Atm. I'm using a 512Hz kernel, what allows virtualbox modules to compile, and astonishing: don't make APIC timer issues (like with 128, 256).<br /><br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-30173666595012507822016-12-10T08:37:40.273+11:002016-12-10T08:37:40.273+11:00Lenovo Thinkstation S20, Xeon W3520 2.66 GHz quadc...Lenovo Thinkstation S20, Xeon W3520 2.66 GHz quadcore, 6GB RAM, 250GB SAMSUNG 850 EVO, 500GB Seagate HDD, NVIDIA Quadro 4000, Intel EXPI9301 ethernet, NEC USB 3.0, no issues.<br />Regarding conservative cflags, even gcc will sometimes fail to build a proper kernel (microbugs) even when using just the standard -O2.<br />But yes -O2 is more safe than -O3.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-40781876737665312912016-12-10T07:51:00.819+11:002016-12-10T07:51:00.819+11:00The CFLAGS chosen in the kernel makefile are often...The CFLAGS chosen in the kernel makefile are often carefully selected based on regression testing and low level assembly errors discovered with higher levels of optimisation so they appear to be relatively conservative intentionally. Using custom CFLAGS is likely to lead to subtle low level bugs which is why I've never included any in my kernels nor included the option to do so.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-28565267930869861232016-12-10T07:33:45.659+11:002016-12-10T07:33:45.659+11:00What system do you run? More details, please.
Unfo...What system do you run? More details, please.<br />Unfortunately, I've had to take a break with this Makefile testings. The "-O3" was prone to runtime errors in former compiler/kernel days, but really months or years ago.<br />I've needed to make sure, that none of these optimisations were causing, that my firefox doesn't playback any flash videos in firefox anymore. It's a pity that I can't rewind the recent MESA updates, what I'd call responsible for my actual issue.<br /><br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-80956568709671132982016-12-09T22:14:18.859+11:002016-12-09T22:14:18.859+11:00I never knew how cool SysRq was until now.
Unfort...I never knew how cool SysRq was until now.<br /><br />Unfortunately, most of the time osu! locks up the system entirely and none of the shortcuts work. When the time comes when it hangs and only hangs, iamready.monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-32748523240734889882016-12-09T13:08:34.098+11:002016-12-09T13:08:34.098+11:00Ah if you're getting realtime priority then it...Ah if you're getting realtime priority then it's highly likely that it's related to rt capabilities and the CPU caps imposed on rt in mainline kernels that aren't there in muqss. Try sysrq-N when the machine locks up to see if it unlocks it. Make sure you have built support for it in your kernel config (under kernel hacking) and that it's enabled by setting the value or /proc/sys/kernel/sysrq to 1. Then when it hangs try the sysrq-n combination which converts real time priority tasks to sched normal.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-73416470492914804362016-12-09T10:04:32.802+11:002016-12-09T10:04:32.802+11:00--> osu!.exe doesn't crash on linux-rt and ...--> osu!.exe doesn't crash on linux-rt and linux stable on any Pulseaudio/Cadence setting ... is what I forgot to clearly specify.monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-60840208440397669242016-12-09T10:01:44.185+11:002016-12-09T10:01:44.185+11:00I have removed the ck and commented out the gcc op...I have removed the ck and commented out the gcc optimization patch and added MuQSS: https://gitlab.com/tom81094/pkgbuild-edits/raw/master/linux-ck-MuQSS.<br /><br />Still locks up the system. I did notice that setting a higher buffer size in Cadence for jackd doesn't make it crash until much later or when auto-playing very complex maps. Turning it off and using Pulseaudio locks up on launch.<br /><br />A few things to note off the top of my head: <br />- I get very measurable (200+) xruns for jackd (-S/hpet) on 128bit buffer size, 3 periods per buffer on linux-rt and linux stable. It doesn't happen on linux-ck. <br />When playing osu! with these settings, it crashes or locks up pretty quickly during selection or beginning of songs. Raising it to 256 bit buffer size, 3 periods per buffer - delays this lock up significantly.<br /><br />- Regardless of whether I set wine-staging RT priorities, from htop specifically only osu!.exe gets RT priority.monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-7847867301985045462016-12-09T06:51:51.845+11:002016-12-09T06:51:51.845+11:00Not yet. I will compile it now and see how it goes...Not yet. I will compile it now and see how it goes.monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-79917020922254296592016-12-08T21:45:58.020+11:002016-12-08T21:45:58.020+11:00Did you try muqss by itself?Did you try muqss by itself?ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-47883564574834433392016-12-08T19:36:45.468+11:002016-12-08T19:36:45.468+11:00For GPU testing, I ran through using intel only, n...For GPU testing, I ran through using intel only, nvidia through bumblebee and with nvidia only configured through xorg.conf.<br /><br />For runtime testing with osu on wine (staging), notable environment changes were primusrun with bumblebee and rt priority (STAGING_RT_PRIORITY_SERVER=90 STAGING_RT_PRIORITY_BASE=90) in staging. Either randomly freezes, crashes, or locks up the system. Lock ups always happen after setting staging rt priority environments.<br /><br />I've had similar results with vanilla wine and wine-rt, but not thoroughly tested in this case.monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-70237654077731573692016-12-08T18:43:22.121+11:002016-12-08T18:43:22.121+11:00osu! still crashes, hangs, and locks up (the entir...osu! still crashes, hangs, and locks up (the entire system) for me even with the workaround mentioned in earlier post comments. After several tries with ck and ck-ivybridge, I did get a different result in dmesg:<br /><br />snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj<br /><br />CPU: Intel i5-3317u<br />RAM: 7853MiB<br />GPU: Intel HD4000/NVIDIA 640M LE<br />WM (tested): bspwm/i3<br />Dist: Arch Linux (Reinstalled twice)<br />Device: Dell 3421monotykamarynoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-89800928886769465212016-12-08T08:55:05.079+11:002016-12-08T08:55:05.079+11:00From my test runs it speeds up the kernel consider...From my test runs it speeds up the kernel considerably. Maybe those enhancements cause latency.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-13830308608528350142016-12-08T08:06:37.518+11:002016-12-08T08:06:37.518+11:00Atm. I don't understand why you disable cpu sp...Atm. I don't understand why you disable cpu specific enhancements (-mno-mmx -mno-sse...). Can you explain the reason, please?<br /><br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-61309965914745633112016-12-06T11:28:08.691+11:002016-12-06T11:28:08.691+11:00Hi ck, a while back you offered a Ubuntu 4.8.7-ck7...Hi ck, a while back you offered a Ubuntu 4.8.7-ck7 kernel. That is running ever so smoothly that I took to building a more recent 4.8.12 kernel, incl. your latest MuQSS patches. Builds fine, but I must be missing an important part of the puzzle, as I can't get it to boot. Would you consider posting your Ubuntu kernel build script here (if you use one..)?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-31559008075568956322016-12-06T10:18:12.485+11:002016-12-06T10:18:12.485+11:00@ck:
addon: all chosen values tested/ written abov...@ck:<br />addon: all chosen values tested/ written above haven't led to this msg. 1000 remains a border. I find it funny that virtualbox complains for above 1000.<br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-23679617520858190192016-12-06T10:07:14.801+11:002016-12-06T10:07:14.801+11:00@ck:
Quite a nice one from Virtualbox after trying...@ck:<br />Quite a nice one from Virtualbox after trying 1024Hz:<br />/tmp/vbox.1/r0drv/linux/the-linux-kernel.h:332:3: error: #error "HZ is not a multiple of 1000, the GIP stuff won't work right!"<br /> # error "HZ is not a multiple of 1000, the GIP stuff won't work right!"<br /><br />BR, Manuel KrauseAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-39734224142657228232016-12-05T07:40:41.455+11:002016-12-05T07:40:41.455+11:00^ sry, I mean autostart of desktop environment.
^ sry, I mean autostart of desktop environment.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-44453362869905589072016-12-05T07:39:23.720+11:002016-12-05T07:39:23.720+11:00just add schedtool -I `pidof Xorg` to rc.localjust add schedtool -I `pidof Xorg` to rc.localAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-79356543475501204562016-12-05T07:14:17.766+11:002016-12-05T07:14:17.766+11:00having said that is there a way to use an automati...having said that is there a way to use an automatic sched_iso policy for X using MuQSS?Anonymousnoreply@blogger.com