System Freezing And Cant Set CpuPower to "schedutil"

Bookmarked inxi: Dump your "inxi -Fxxxza --no-host" here and bookmark it

Cant say if the 2 problems are related, but journalctl doesnt show me anything at the time of the crash except the constant repeating of the CpuPower error that has apparentyl been happening since 5/28 when the oldest record in my journalctl is. Also, the freeze seems to have started when I switched to kernel 5.7, but it happens so randomly i cant recreate it fast enough to know if the kernel is really the problem.

I will just be watching a video, usually with the ramdisk mounted (not really in it) and some hours (2-12) after a suspend (not sure if required), it will lock the whole dektop, sometimes mouse is still usuable, sometimes not, and keyboard commands dont work to get to ttyl. However, if I'm connected to the ramdisk by samba from another system I can continue to pull files from it as if nothing is wrong.

At first I thought it was a cinnamon issue, due to an error poppin gup at start up, but I have been through the journal and dmesg and fixed any errors I could figure out how to fix.

The only error left is this stupid cpu power one that runs on repeat from the moment the system hits the kernel. And no amount of messing with the governor seems to fix it...

Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Failed to apply profile => Error: setGovernor: choosen governor 'powersave' is not available (/sys/devices/system/cpu/cpu0) available are: ["performance","schedutil"]
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Failed to set default cpu config => Error: setGovernor: choosen governor 'powersave' is not available (/sys/devices/system/cpu/cpu0) available are: ["performance","s>
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Incorrect settings, reapplying profile
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core31 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core30 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core29 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core28 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core27 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core26 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core25 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core24 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core23 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core22 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core21 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core20 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core19 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core18 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core17 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core16 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core15 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core14 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core13 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core12 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core11 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core10 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core9 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core8 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core7 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core6 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core5 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core4 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core3 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core2 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core1 scaling governor  => 'schedutil' instead of 'powersave'
Jun 10 18:49:03 cw-pc tccd[1071]: CpuWorker: Unexpected value core0 scaling governor  => 'schedutil' instead of 'powersave'

Thank you for any help you can provide!

1 Like

Okay! Update of the solution so far...
tccd is apparently tuxedo control center...daemon? Either way, it is code for the tuxedo laptop that was put on my system as a dependency for running another program with (badly done) code for linux (Streamlabels). So I have solved the problem of the cpupower repeating error, and I will report back if it has also solved the freezing issue.

Thanks again for anyone who took a look!

1 Like

Will do! Just want to make sure the freezing is actually solved before I do. Thanks!

Okay, so freezing problem not solved. So far, I have only seen it in 5.7 since I updated to it. I usually don't see anything in the logs I haven't gone back and fixed...starting to get stumped....

I'm currently running 5.6 to see if it ever freezes on me, but it's so hard to get it to happen since it never seems to overlap on any particular event.

I have the journals for the most recent crash that happened last night, and I'll post that here just in case, but I am going to go through it myself and see if anything stands out, but usually nothing seems to.

If you know anything about problems with 5.7, especially on threadripper, that would be a huge help! Thanks!

Journal for last 24 hours: https://drive.google.com/file/d/1i3l3xgM5BIwfMAei4ezbDL1smi__Q1fs/view?usp=sharing
Crash is somewhere around 22:35 2020-06-12

I normally don't install any .0 kernels (on any OS) as they are more unstable and always wait for .1 (first patches)

E.G.:
5.0: no-no
5.0.1: only if you have issues with the 4.X series
5.1.0: no-no
5.1.1: yes
etc...

Well I broke down and did a full rebuild after running into some issues while trying to test my nvme for possible issues. So I will see if I have anymore freezes on 5.7 or not. I'll report back if something freezes or in a couple days if there have been no problems since the rebuild. I was running a build I had around since 2017, so the possibility for issues was high, hence all the journal cleaning (going to become a habit to check it and fix things earlier).

But you're right, it may have just been the x.0 thing, but I've always gotten on them early and had few issues

1 Like

Okay, update time, I think.

No further issues after rebuild, still running 5.7.0 (-3 as of now). I believe my problem was a mix of things. I needed to check my journals more regularly to catch on to random problems I would have that linux would power through, but were easily fixable if I just looked. I also had many .pacnew files that I never transferred in that have changed quite a bit since the 2017 build that I started with.

So I need to be more conscious of pulling in those new files. Also just cleaning up my system from so many little things I installed to try, then uninstalled, but didnt clean up behind.

Many little changes that will make me a better linux user in the future, but stuff I appreciated not having to deal with before as it just kept working.

I'll report once more after a few more, harder, real world tests are run in the coming week.

If you would be so kind as to give all the exact commands you ran (in response to this), that would be helpful for another user that isn't as smart as us as they might be able to replicate your commands and this thread will then become something more useful to the community at large.

I'll DM you with tips and tricks to make this into a shiny pearl in the middle of the mud.

:joy: :wink:

No need, it finally happened again, and I seem to have narrowed down an error when the problem occurs....just cant tell from the log what it is. It always seems to be a combination of firefox, a ramdisk, and post-sleeping the computer. This time was almost exactly 2 hours after waking the computer.

Heres the section catching my eye:

Jun 24 19:24:50 cw-pc kernel: general protection fault, probably for non-canonical address 0x19e4872467aaffd8: 0000 [#1] PREEMPT SMP NOPTI
Jun 24 19:24:50 cw-pc kernel: CPU: 0 PID: 396902 Comm: kworker/u257:4 Tainted: G           OE     5.7.0-3-MANJARO #1
Jun 24 19:24:50 cw-pc kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH EXTREME, BIOS 2001 07/31/2019
Jun 24 19:24:50 cw-pc kernel: Workqueue: events_unbound commit_work [drm_kms_helper]
Jun 24 19:24:50 cw-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2aa/0x2310 [amdgpu]
Jun 24 19:24:50 cw-pc kernel: Code: 4f 08 8b 81 e0 02 00 00 41 83 c5 01 44 39 e8 0f 87 46 ff ff ff 48 83 bd f0 fc ff ff 00 0f 84 03 01 00 00 48 8b bd f0 fc ff ff <80> bf b0 01 00 00 01 0f 86 ac 00 00 00 48 b9 00 00 00 00 01 00 00
Jun 24 19:24:50 cw-pc kernel: RSP: 0018:ffffa48e9b31faf8 EFLAGS: 00010206
Jun 24 19:24:50 cw-pc kernel: RAX: 0000000000000006 RBX: ffffa08260b0ec00 RCX: ffffa0828ccf4000
Jun 24 19:24:50 cw-pc kernel: RDX: ffffa07a76a54c00 RSI: ffffffffc19c05e0 RDI: 19e4872467aaffd8
Jun 24 19:24:50 cw-pc kernel: RBP: ffffa48e9b31fe60 R08: 0000000000000001 R09: 0000000000000001
Jun 24 19:24:50 cw-pc kernel: R10: 0000000000069f49 R11: 000000000006ac08 R12: 0000000000000000
Jun 24 19:24:50 cw-pc kernel: R13: 0000000000000006 R14: ffffa08260b0d400 R15: ffffa07a15a78580
Jun 24 19:24:50 cw-pc kernel: FS:  0000000000000000(0000) GS:ffffa07a9e200000(0000) knlGS:0000000000000000
Jun 24 19:24:50 cw-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 24 19:24:50 cw-pc kernel: CR2: 00007f29fe7fca08 CR3: 0000000822ab6000 CR4: 00000000003406f0
Jun 24 19:24:50 cw-pc kernel: Call Trace:
Jun 24 19:24:50 cw-pc kernel:  ? cpumask_next_and+0x19/0x20
Jun 24 19:24:50 cw-pc kernel:  ? update_sd_lb_stats.constprop.0+0x799/0x8f0
Jun 24 19:24:50 cw-pc kernel:  ? find_busiest_group+0x41/0x310
Jun 24 19:24:50 cw-pc kernel:  ? __switch_to_asm+0x40/0x70
Jun 24 19:24:50 cw-pc kernel:  ? 0xffffffffb2000000
Jun 24 19:24:50 cw-pc kernel:  ? _raw_spin_unlock_irq+0x1d/0x30
Jun 24 19:24:50 cw-pc kernel:  ? finish_task_switch+0x80/0x270
Jun 24 19:24:50 cw-pc kernel:  ? __switch_to_asm+0x34/0x70
Jun 24 19:24:50 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jun 24 19:24:50 cw-pc kernel:  commit_tail+0x94/0x130 [drm_kms_helper]
Jun 24 19:24:50 cw-pc kernel:  process_one_work+0x1da/0x3d0
Jun 24 19:24:50 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jun 24 19:24:50 cw-pc kernel:  worker_thread+0x4d/0x3e0
Jun 24 19:24:50 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jun 24 19:24:50 cw-pc kernel:  kthread+0x13e/0x160
Jun 24 19:24:50 cw-pc kernel:  ? __kthread_bind_mask+0x60/0x60
Jun 24 19:24:50 cw-pc kernel:  ret_from_fork+0x22/0x40
Jun 24 19:24:50 cw-pc kernel: Modules linked in: rmd320 rmd256 rmd128 algif_hash af_alg btrfs blake2b_generic xor raid6_pq ufs hfsplus hfs minix ntfs msdos jfs xfs dm_mod fuse xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT nf_reject_i>
Jun 24 19:24:50 cw-pc kernel:  sp5100_tco realtek syscopyarea snd k10temp i2c_piix4 sysfillrect libphy sysimgblt i2c_algo_bit fb_sys_fops soundcore dca pinctrl_amd gpio_amdpt evdev mac_hid acpi_cpufreq eeepc_wmi asus_wmi battery sparse_k>
Jun 24 19:24:50 cw-pc kernel: ---[ end trace bb4b1776c1e6e514 ]---
Jun 24 19:24:50 cw-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2aa/0x2310 [amdgpu]
Jun 24 19:24:50 cw-pc kernel: Code: 4f 08 8b 81 e0 02 00 00 41 83 c5 01 44 39 e8 0f 87 46 ff ff ff 48 83 bd f0 fc ff ff 00 0f 84 03 01 00 00 48 8b bd f0 fc ff ff <80> bf b0 01 00 00 01 0f 86 ac 00 00 00 48 b9 00 00 00 00 01 00 00
Jun 24 19:24:50 cw-pc kernel: RSP: 0018:ffffa48e9b31faf8 EFLAGS: 00010206
Jun 24 19:24:50 cw-pc kernel: RAX: 0000000000000006 RBX: ffffa08260b0ec00 RCX: ffffa0828ccf4000
Jun 24 19:24:50 cw-pc kernel: RDX: ffffa07a76a54c00 RSI: ffffffffc19c05e0 RDI: 19e4872467aaffd8
Jun 24 19:24:50 cw-pc kernel: RBP: ffffa48e9b31fe60 R08: 0000000000000001 R09: 0000000000000001
Jun 24 19:24:50 cw-pc kernel: R10: 0000000000069f49 R11: 000000000006ac08 R12: 0000000000000000
Jun 24 19:24:50 cw-pc kernel: R13: 0000000000000006 R14: ffffa08260b0d400 R15: ffffa07a15a78580
Jun 24 19:24:50 cw-pc kernel: FS:  0000000000000000(0000) GS:ffffa07a9e200000(0000) knlGS:0000000000000000
Jun 24 19:24:50 cw-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 24 19:24:50 cw-pc kernel: CR2: 00007f29fe7fca08 CR3: 0000000822ab6000 CR4: 00000000003406f0

Everything before and after is just kernel: logitech-hidpp-device 0003:046D:4041.0010: multiplier = 8 until it sees me pressing the power switch (which it gladly ignores). Hope this can help someone narrow this down, cause it's kinda annoying and hard to get to repeat.

I dont know what it is about linux (Manjaro?) and 2 hours, but this is like the 3rd system crippling (everything locking up) problem I've had that popped up at exactly 2 hours after the culprit starts since I have switched to Manjaro 4-5 years ago (kinda weird).

Okay, can solidly confirm that this is an amdgpu bug as it just happened again and I got the same stream of errors with almost an overlap in most of the information. I have also found an bug reported in arch that seems to be the same that is being hunted down apparently and it is believed that a fix will be out in 5.7.7, but is not yet comfirmed. However, much as I believed before I didn the rebuild of my system, the bug is something that has been rolled back to previous kernels, since I had it happen on 5.6 and the arch bug says they had it happen on 5.4.

Logs again for the newest crash:

Jul 08 01:37:05 cw-pc kernel: general protection fault, probably for non-canonical address 0xfd02e7a825adb3f7: 0000 [>
Jul 08 01:37:05 cw-pc kernel: CPU: 1 PID: 796659 Comm: kworker/u257:1 Tainted: G           OE     5.7.0-3-MANJARO #1
Jul 08 01:37:05 cw-pc kernel: Hardware name: System manufacturer System Product Name/ROG ZENITH EXTREME, BIOS 2001 07>
Jul 08 01:37:05 cw-pc kernel: Workqueue: events_unbound commit_work [drm_kms_helper]
Jul 08 01:37:05 cw-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2aa/0x2310 [amdgpu]
Jul 08 01:37:05 cw-pc kernel: Code: 4f 08 8b 81 e0 02 00 00 41 83 c5 01 44 39 e8 0f 87 46 ff ff ff 48 83 bd f0 fc ff >
Jul 08 01:37:05 cw-pc kernel: RSP: 0018:ffffaf3b1aba7af8 EFLAGS: 00010282
Jul 08 01:37:05 cw-pc kernel: RAX: 0000000000000006 RBX: ffff93ce44437000 RCX: ffff93d64a392800
Jul 08 01:37:05 cw-pc kernel: RDX: ffff93d63656ba00 RSI: ffffffffc19765e0 RDI: fd02e7a825adb3f7
Jul 08 01:37:05 cw-pc kernel: RBP: ffffaf3b1aba7e60 R08: 0000000000000001 R09: 0000000000000001
Jul 08 01:37:05 cw-pc kernel: R10: 000000000005ddb7 R11: 000000000005ddb7 R12: 0000000000000000
Jul 08 01:37:05 cw-pc kernel: R13: 0000000000000006 R14: ffff93ce44430000 R15: ffff93cd68317880
Jul 08 01:37:05 cw-pc kernel: FS:  0000000000000000(0000) GS:ffff93ce5e240000(0000) knlGS:0000000000000000
Jul 08 01:37:05 cw-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 08 01:37:05 cw-pc kernel: CR2: 00007f26142c6000 CR3: 000000051860a000 CR4: 00000000003406e0
Jul 08 01:37:05 cw-pc kernel: Call Trace:
Jul 08 01:37:05 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jul 08 01:37:05 cw-pc kernel:  commit_tail+0x94/0x130 [drm_kms_helper]
Jul 08 01:37:05 cw-pc kernel:  process_one_work+0x1da/0x3d0
Jul 08 01:37:05 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jul 08 01:37:05 cw-pc kernel:  worker_thread+0x4d/0x3e0
Jul 08 01:37:05 cw-pc kernel:  ? rescuer_thread+0x3f0/0x3f0
Jul 08 01:37:05 cw-pc kernel:  kthread+0x13e/0x160
Jul 08 01:37:05 cw-pc kernel:  ? __kthread_bind_mask+0x60/0x60
Jul 08 01:37:05 cw-pc kernel:  ret_from_fork+0x22/0x40
Jul 08 01:37:05 cw-pc kernel: Modules linked in: fuse hid_logitech_hidpp xt_CHECKSUM xt_MASQUERADE xt_conntrack xpad >
Jul 08 01:37:05 cw-pc kernel:  sp5100_tco sysfillrect realtek sysimgblt i2c_piix4 fb_sys_fops libphy k10temp soundcor>
Jul 08 01:37:05 cw-pc kernel: ---[ end trace d8200c720bfdc01a ]---
Jul 08 01:37:05 cw-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x2aa/0x2310 [amdgpu]
Jul 08 01:37:05 cw-pc kernel: Code: 4f 08 8b 81 e0 02 00 00 41 83 c5 01 44 39 e8 0f 87 46 ff ff ff 48 83 bd f0 fc ff >
Jul 08 01:37:05 cw-pc kernel: RSP: 0018:ffffaf3b1aba7af8 EFLAGS: 00010282
Jul 08 01:37:05 cw-pc kernel: RAX: 0000000000000006 RBX: ffff93ce44437000 RCX: ffff93d64a392800
Jul 08 01:37:05 cw-pc kernel: RDX: ffff93d63656ba00 RSI: ffffffffc19765e0 RDI: fd02e7a825adb3f7
Jul 08 01:37:05 cw-pc kernel: RBP: ffffaf3b1aba7e60 R08: 0000000000000001 R09: 0000000000000001
Jul 08 01:37:05 cw-pc kernel: R10: 000000000005ddb7 R11: 000000000005ddb7 R12: 0000000000000000
Jul 08 01:37:05 cw-pc kernel: R13: 0000000000000006 R14: ffff93ce44430000 R15: ffff93cd68317880
Jul 08 01:37:05 cw-pc kernel: FS:  0000000000000000(0000) GS:ffff93ce5e240000(0000) knlGS:0000000000000000
Jul 08 01:37:05 cw-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 08 01:37:05 cw-pc kernel: CR2: 00007f26142c6000 CR3: 000000051860a000 CR4: 00000000003406e0

So yea...guess I'm waiting for the kernel team to find this bug...

Once again, I'll keep up to date as things proceed.

Link to arch bug of similar/same problem, if interested: https://bugs.archlinux.org/task/66991

1 Like

Update again, I'v ebeen riding pretty clean for a while, but it finally happened again...I opened one too many tabs in firefox and it froze as I was watching a youtube video (the usual)

Need to catch back up with progress with this, but I know that the updates they are talking about are quite a bit ahead of Manjaro's

So, even on the newest 5.7 update from Manjaro, still happens with amdgpu.

I have confirmed now though, that I can do a lot after it happens. I was starting and stopping the youtube video (audio only obviously) and fast forwarding and rewinding. However, attempting sleep, much like shutdown, just gets registered as being attempted in the logs and then you lose all response from keyboard after that and all logs stop.

Hope this gets settled soon, I hate having to make sure I dont do too much with my browsers so I dont accidentally lock up my computer...

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by