I ran the prime95 test for 5 hours with no errors. I guess thats a good thing… Not sure where to go from here.
EDIT: I don’t think I’ve ever mentioned the symptoms. When I get the freeze, the screen goes black, and I lose power to my keyboard and mouse. There is usually a delay before I lose the keyboard and mouse, and there was ONE time where I was able to get to a TTY. I have not been able to do it again, though.
Hi
So was that with the ngg boot option? Sounds like it’s all good…
Yes, maybe. I was thinking the same thing. But, I don’t remember if I actually rebooted since I added that. =/. So, I’m rebooting now and playing some Dota. Wish me luck!!
Sigh. Nope, crash is still happening. I did not lose my keyboard and mouse this time. That’s something I guess.
Hi
I would remove it then…
Do you have another computer you could ssh in from?
Yes, I have a low-powered laptop. I will need some hand holding as I have no idea about ssh, though.
Hi
Well if your still getting crashes, might be time for a bug report…
If you can’t get information after the fact from the logs, then may need to ssh into the system and tail the logs to capture what is happening.
If you log in to a different desktop environment, eg IceWM and run the game, does it crash?
Environment doesn’t matter. I installed cinnamon to test it out, and same behavior. I will look into figuring out the ssh thing. But, this last time, I was able to get into a tty.
question 1: If I am able to do this again (either in a tty on same machine or via ssh from laptop), what should I be doing?
question 2: Where should I be filing this bug report?
again, thank you. Even though it hasn’t been resolved, I really appreciate your help and patience.
Hi
On the machine your having issues with, just check via YaST services that ssh is running and then in the firewall that the ssh service port is open. Then on the other system with a ssh client try and connect to the ip address… eg
ssh <yourusername>@<ipaddress>
Once get that working then can work out what’s needed 
Bug reports, go here: openSUSE:Submitting bug reports - openSUSE
Okay, I seem to have my laptop connected via ssh. It’s saying “have a lot of fun”. I had it connected before, as soon as my desktop crashed, it lost connection. I was thinking at the time that we needed it connected DURING the crash, but now I’m guessing not so. Anyway, the laptop is reconnected to the desktop (i guess).
Hi
That sounds good, so is the computer your connecting from a linux system or using something like putty?
Anyway, what you may want is a few terminal sessions running, say one tailing the log, so need to switch to root user and run;
journalctl -f
Another one watching process and ram consumption with the command top, maybe before the crash happens you see swap being used as additional memory etc.
See how that goes…
Okay, it finally happened. (aside: I was unable to connect to this forum from either computer while they were linked. I guess it was using the wifi to connect and that was too much for the adapters? anyway, whatever.)
First, there did not appear to be anything unusual in TOP. At least not with ram, which is what I was looking at. There was a whole lot of stuff dumped into the journal, though. So, I’m going to post a rather long one here. The end even says something about broken bios, and complained a lot about tsc.
EDIT: To be clear, the beginning is when the crash first starts. It took a few seconds for the keyboard and mouse to lose power, and that is at the end, where the messages stopped.
Jul 01 22:34:51 linux-i7cx dbus-daemon[1406]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.6' (uid=0 pid=1613 comm="/usr/sbin/NetworkManager --no-daemon ")
Jul 01 22:34:51 linux-i7cx dbus-daemon[1406]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 01 22:34:55 linux-i7cx org_kde_powerdevil[2487]: powerdevil: Enforcing inhibition from ":1.13" "My SDL application" with cookie 459 and reason "Playing a game"
Jul 01 22:34:55 linux-i7cx org_kde_powerdevil[2487]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
Jul 01 22:35:18 linux-i7cx kernel: [drm:amdgpu_dm_commit_planes.isra.0 [amdgpu]] *ERROR* Waiting for fences timed out.
Jul 01 22:35:18 linux-i7cx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=2250936, emitted seq=2250938
Jul 01 22:35:18 linux-i7cx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process hoi4 pid 21410 thread hoi4:cs0 pid 21414
Jul 01 22:35:18 linux-i7cx kernel: amdgpu 0000:0a:00.0: GPU reset begin!
Jul 01 22:35:18 linux-i7cx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=2746868, emitted seq=2746870
Jul 01 22:35:18 linux-i7cx kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process hoi4 pid 21410 thread hoi4:cs0 pid 21414
Jul 01 22:35:18 linux-i7cx kernel: amdgpu 0000:0a:00.0: GPU reset begin!
Jul 01 22:35:19 linux-i7cx dbus-daemon[1406]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.6' (uid=0 pid=1613 comm="/usr/sbin/NetworkManager --no-daemon ")
Jul 01 22:35:19 linux-i7cx dbus-daemon[1406]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 01 22:35:20 linux-i7cx dbus-daemon[1406]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.6' (uid=0 pid=1613 comm="/usr/sbin/NetworkManager --no-daemon ")
Jul 01 22:35:20 linux-i7cx dbus-daemon[1406]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jul 01 22:35:23 linux-i7cx kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Jul 01 22:35:28 linux-i7cx kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:47:crtc-0] hw_done or flip_done timed out
Jul 01 22:35:39 linux-i7cx kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:47:crtc-0] flip_done timed out
Jul 01 22:35:49 linux-i7cx kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:45:plane-5] flip_done timed out
Jul 01 22:35:49 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:49 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x0
Jul 01 22:35:50 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:50 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:50 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x0
Jul 01 22:35:51 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:52 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:52 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x0
Jul 01 22:35:52 linux-i7cx kernel: [drm] REG_WAIT timeout 10us * 3500 tries - dce_mi_free_dmif line:634
Jul 01 22:35:52 linux-i7cx kernel: WARNING: CPU: 10 PID: 22324 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold+0x29/0x30 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: Modules linked in: ccm cmac fuse rfcomm af_packet xt_tcpudp ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nfnetlink scsi_transport_iscsi ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter uinput bnep msr xfs uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 squashfs videodev snd_usb_audio videobuf2_common edac_mce_amd btusb btrtl btbcm snd_usbmidi_lib btintel kvm snd_rawmidi bluetooth loop snd_seq_device irqbypass ecdh_generic arc4 crct10dif_pclmul iwlmvm crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic mac80211 ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlwifi aesni_intel eeepc_wmi snd_pcm asus_wmi aes_x86_64 sparse_keymap crypto_simd
Jul 01 22:35:52 linux-i7cx kernel: snd_timer video wmi_bmof cryptd glue_helper pcspkr igb cfg80211 joydev snd sp5100_tco soundcore rfkill k10temp ptp i2c_piix4 ccp pps_core dca gpio_amdpt pinctrl_amd pcc_cpufreq gpio_generic acpi_cpufreq button btrfs libcrc32c xor hid_logitech_hidpp hid_logitech_dj raid6_pq hid_generic usbhid amdgpu i2c_algo_bit chash gpu_sched amd_iommu_v2 ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci drm crc32c_intel xhci_hcd usbcore wmi sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
Jul 01 22:35:52 linux-i7cx kernel: CPU: 10 PID: 22324 Comm: kworker/10:1 Not tainted 5.1.10-1-default #1 openSUSE Tumbleweed (unreleased)
Jul 01 22:35:52 linux-i7cx kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B350-F GAMING, BIOS 4801 04/26/2019
Jul 01 22:35:52 linux-i7cx kernel: Workqueue: events drm_sched_job_timedout [gpu_sched]
Jul 01 22:35:52 linux-i7cx kernel: RIP: 0010:generic_reg_wait.cold+0x29/0x30 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: Code: ff 44 8b 44 24 68 48 8b 4c 24 60 48 c7 c7 e8 33 6f c0 8b 54 24 58 8b 34 24 e8 04 04 aa e8 41 83 7c 24 20 01 0f 84 bf 7e fe ff <0f> 0b e9 b8 7e fe ff e8 3e a2 ed ff 48 c7 c7 00 b0 79 c0 e8 82 8e
Jul 01 22:35:52 linux-i7cx kernel: RSP: 0018:ffffaa7fcbfa3820 EFLAGS: 00010297
Jul 01 22:35:52 linux-i7cx kernel: RAX: 0000000000000044 RBX: 0000000000000dad RCX: 0000000000000000
Jul 01 22:35:52 linux-i7cx kernel: RDX: ffff8fd5be89f000 RSI: ffff8fd5be896a58 RDI: ffff8fd5be896a58
Jul 01 22:35:52 linux-i7cx kernel: RBP: 00000000000035af R08: ffff8fd5be896a58 R09: 0000000000000001
Jul 01 22:35:52 linux-i7cx kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff8fd5b54c0f80
Jul 01 22:35:52 linux-i7cx kernel: R13: ffff8fd5b664c000 R14: 0000000000000002 R15: ffff8fd3f0384188
Jul 01 22:35:52 linux-i7cx kernel: FS: 0000000000000000(0000) GS:ffff8fd5be880000(0000) knlGS:0000000000000000
Jul 01 22:35:52 linux-i7cx kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 01 22:35:52 linux-i7cx kernel: CR2: 00007fbf302a7000 CR3: 000000073daca000 CR4: 00000000003406e0
Jul 01 22:35:52 linux-i7cx kernel: Call Trace:
Jul 01 22:35:52 linux-i7cx kernel: dce_mi_free_dmif+0xdb/0x1c0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: dce110_reset_hw_ctx_wrap+0x152/0x1f0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: dce110_apply_ctx_to_hw+0x3a/0x470 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: ? hwmgr_handle_task+0x66/0xc0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: ? mutex_lock+0xe/0x30
Jul 01 22:35:52 linux-i7cx kernel: ? pp_dpm_dispatch_tasks+0x45/0x60 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: ? dm_pp_apply_display_requirements+0x1a1/0x1b0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: dc_commit_state_no_check+0x1f2/0x4d0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: ? vsnprintf+0x387/0x4e0
Jul 01 22:35:52 linux-i7cx kernel: dc_commit_state+0x8f/0xb0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_dm_atomic_commit_tail+0x3be/0xa10 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: ? _raw_spin_unlock_irqrestore+0x24/0x40
Jul 01 22:35:52 linux-i7cx kernel: ? __irq_work_queue_local+0x50/0x60
Jul 01 22:35:52 linux-i7cx kernel: ? irq_work_queue+0x46/0x50
Jul 01 22:35:52 linux-i7cx kernel: ? wake_up_klogd+0x30/0x40
Jul 01 22:35:52 linux-i7cx kernel: ? vprintk_emit+0x1cd/0x240
Jul 01 22:35:52 linux-i7cx kernel: ? printk+0x48/0x4a
Jul 01 22:35:52 linux-i7cx kernel: ? _raw_spin_unlock_irqrestore+0x24/0x40
Jul 01 22:35:52 linux-i7cx kernel: ? drm_atomic_helper_wait_for_dependencies+0x1e4/0x1f0 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: ? wait_for_completion_timeout+0xf3/0x110
Jul 01 22:35:52 linux-i7cx kernel: ? wake_up_q+0x60/0x60
Jul 01 22:35:52 linux-i7cx kernel: ? commit_tail+0x3c/0x70 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: commit_tail+0x3c/0x70 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: drm_atomic_helper_commit+0x108/0x110 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: drm_atomic_helper_disable_all+0x144/0x160 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: drm_atomic_helper_suspend+0x4c/0xe0 [drm_kms_helper]
Jul 01 22:35:52 linux-i7cx kernel: dm_suspend+0x1c/0x60 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_device_ip_suspend_phase1+0x91/0xc0 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_device_ip_suspend+0x1c/0x60 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_device_pre_asic_reset+0x1f4/0x209 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_device_gpu_recover+0x67/0x724 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: amdgpu_job_timedout+0xf7/0x120 [amdgpu]
Jul 01 22:35:52 linux-i7cx kernel: drm_sched_job_timedout+0x3a/0x70 [gpu_sched]
Jul 01 22:35:52 linux-i7cx kernel: process_one_work+0x1df/0x3c0
Jul 01 22:35:52 linux-i7cx kernel: worker_thread+0x4d/0x400
Jul 01 22:35:52 linux-i7cx kernel: ? process_one_work+0x3c0/0x3c0
Jul 01 22:35:52 linux-i7cx kernel: kthread+0x117/0x130
Jul 01 22:35:52 linux-i7cx kernel: ? kthread_associate_blkcg+0x90/0x90
Jul 01 22:35:52 linux-i7cx kernel: ret_from_fork+0x27/0x50
Jul 01 22:35:52 linux-i7cx kernel: --- end trace 233c7a5494453ece ]---
Jul 01 22:35:52 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:53 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:53 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x1, error code: 0x0
Jul 01 22:35:53 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:54 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:54 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x4c, input parameter: 0x3, error code: 0x0
Jul 01 22:35:54 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:55 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:55 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x9, input parameter: 0xf4, error code: 0x0
Jul 01 22:35:55 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:56 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:56 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0xa, input parameter: 0xa0b000, error code: 0x0
Jul 01 22:35:56 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:57 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:57 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0x0
Jul 01 22:35:57 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:58 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:58 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x400, error code: 0x0
Jul 01 22:35:59 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:59 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:35:59 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x42, input parameter: 0x1, error code: 0x0
Jul 01 22:36:00 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:36:00 linux-i7cx kernel: amdgpu: [powerplay] No response from smu
Jul 01 22:36:00 linux-i7cx kernel: amdgpu: [powerplay] Failed message: 0x24, input parameter: 0x0, error code: 0x0
Jul 01 22:36:02 linux-i7cx kernel: clocksource: timekeeping watchdog on CPU8: Marking clocksource 'tsc' as unstable because the skew is too large:
Jul 01 22:36:02 linux-i7cx kernel: clocksource: 'hpet' wd_now: b2f0cd wd_last: 5acde1 mask: ffffffff
Jul 01 22:36:02 linux-i7cx kernel: clocksource: 'tsc' cs_now: 464e52249b0e cs_last: 464e2e249be6 mask: ffffffffffffffff
Jul 01 22:36:02 linux-i7cx kernel: tsc: Marking TSC unstable due to clocksource watchdog
Jul 01 22:36:02 linux-i7cx kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Jul 01 22:36:02 linux-i7cx kernel: sched_clock: Marking unstable (25796992168374, 664656330)<-(25797798036017, -141204367)
Jul 01 22:36:05 linux-i7cx kernel: sched: RT throttling activated
Hi
Can you add the grub kernel boot option amdgpu.dc=1 do the same capture trick, if it fails the same way, change the 1 to a 0 and test again…
WARNING: CPU: 10 PID: 22324 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold+0x29/0x30 [amdgpu]
If it keeps crashing then with those three captures would raise a bug report against the kernel and see how it goes.
Okay, thanks. Will do.
Boy, I thought that last post was going to be my last, but the results from adding amdgpu.dc=1 and amdgpu.dc=0 were different enough that I thought I would run it by you before I went ahead with the bug report. When adding amdgpu.dc=1 to the boot parameter, instead of crashing, the machine acted like it was going to crash (I guess it did, but did not freeze?) and then restarted itself. What is even stranger is that I never got any error messages on the journalctl -f output from the sshed laptop. The last line from the output was the same things that were going the whole time I was playing the game, which I (think) was:
Jul 01 22:34:55 linux-i7cx org_kde_powerdevil[2487]: powerdevil: Enforcing inhibition from ":1.13" "My SDL application" with cookie 459 and reason "Playing a game"
That was not really it. I copied it from my previous post because I failed to keep the output sorry. But I am pretty confident that it was the same message over and over. When I changed the boot parameter to amdgpu.dc=0, the computer would no longer start and I had a black screen and no tty (lol). Well, I guess it WAS starting, I just could not see it. I was thankfully still able to ssh into the system with my laptop so I changed the boot back to [FONT=arial][FONT=arial]amdgpu.dc=1 via yast’s command line interface (pretty cool that yast can do that, btw!).
So anyway, let me know if I should do anything else or go ahead with the bug report. I should say, btw, that the behavior has gotten less terrible. Instead of crashing within 10 minutes of playing HOI4, it is now taking about 40. And I got through 3 games of Dota before it happened. Not sure what changed there, but it is still happening.[/FONT][/FONT]
Hi
So it was lasting longer with dc=1 then? Can you look at disabling powerdevil and then see how it goes. Looks like getting down to what may be the issue, if it runs happily without powerdevil running, then remove the dc=1 line and test again.
Dangit, I’m sorry, I cannot figure this one out. I see that powerdevil is a kde thing, but I am not seeing what to disable. In the system settings power management sections I could turn off the screen energy savings and the suspend session settings (they are both currently set to 10 minutes). Is this what I should do? Again, sorry.
Hi
I’m no Plasma user, but those will probably be the things to disable for the moment.
Okay, this is interesting. I tried it with the screen energy savings and the suspend session settings turned off. The system crashed immediately – within about 30 seconds. I rebooted, and found powerdevil in the system activity monitor and killed the process. I then tried to play again. Same thing – crash within 30 seconds of playing the game. I tried this again (no powerdevil) but this time without the [FONT=arial][FONT=arial]amdgpu.dc=1 variable. Same result.
I added the variable back and let powerdevil run this time because I wanted to make sure I was not crazy. I played HOI4 for an hour just to make sure. The difference is dramatic. It will crash eventually I am sure, but at least it is playable. Having said that, I noticed something. The powerdevil message is not showing up when the game starts, but rather when Steam starts. (You said you are not a gamer, so if you don’t know, Steam is a game library / launcher / store). Here is what it is saying:
Jul 02 20:46:38 linux-i7cx org_kde_powerdevil[2497]: powerdevil: Enforcing inhibition from ":1.13" "My SDL application" with cookie 1 and reason "Playing a game"
Jul 02 20:46:38 linux-i7cx org_kde_powerdevil[2497]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
It repeats this over and over again, with the “cookie” number going up. It is now at cookie 182. I have no idea if it matters or not.
[/FONT][/FONT]
Hi
I have/use Steam Just use Gnome DE not Plasma/KDE
So it would appear to be something with the amdgpu driver and powerdevil, I suggest carry on with your tests until it crashes and see if any more details available.