This didn't stop the crashing from happening, but what it did was make RESUIB work. Before there was no response even to that.
Regardless, I am still not getting anything in the journal. But I am able to force the issue pretty consistently, it requires ~30min of gaming. But it has also happened simply while browsing the web or even in idle.
I did try blacklisting sp5100-tco, but I am not certain if I was succesfull.
]]>The reason I'm somewhat bumping this thread few months later is because the exact problem resurfaced again a few days ago. And I realized that it was because I had installed amd-ucode. And after that, not even kernel parameter helped. Removing it helped again. So as a workaround for anyone who are still experiencing this issue and this issue and can live without microcode, try to uninstall it.
]]>Same symptoms here. No visible errors in the logs (except my Corsair keyboard). Random freezes between some hours of use up to to ~2 days. Freeze after some minutes up to 2 hour in a wayland session.
For both X11 and wayland the freezes occur on random occasions: Web use, rendering, office work, gaming and even on idle desktop. Music from a media player or inside games keeps playing. But no kb input, tty switching or whatever is possible.
For me the freezes seems to be a problem with KDE / Plasma, even with all compositor effects disabled. A test setup with default LXQt (openbox, X11) went smooth without crashes for about a week time. Same with a test setup of Win 10. Both with heavy system loads for testing.My HW
-----------
CPU: Ryzen 1700x, old "faulty" type
MB: ASUS C6H with Agesa 1.0.0.2c UEFI
RAM: 2 x 16 GB Trident 3200
Graphics: Vega 64 (AMDGPU driver)
SDD: 512 GB PM961
NIC: Intel X520As much as I want to switch to LXQT anyway, there is still too much missing for every day use :-(
Gnome is not my kind of thing, so the remaining option would be to go bach to XFCE which gets kind of old...Any ideas would be highly welcome!
I was following a wrong lead for blaming the DE for my freezes (posting above).
Finally blacklisting sp5100-tco seems to do the trick. Stable system now for 2 weeks, further testing. The only side effect I noticed so far is that powering down the system (not hibernate) sometimes hangs for several seconds (up to ~20) on a black screen with blinking cursor before actually powering down.
]]>CPU: Ryzen 3 2200G
MB: MSI x370 gaming plus
RAM: 2 x 4 GB Gskill
At this stage I have turn off iommu (https://bugs.launchpad.net/ubuntu/+sour … ug/1747463) and set the option "Typical idel current " in the bios. I still experiencing the following issue
- freeze during the boot process
- freeze during use (gaming, web surfing)
As I've bought 2 identical config, I will finish to assemble the second one to see if I experience the same problem. Here are the log
on boot :
sept. 23 16:31:26 Viper kernel: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316)
sept. 23 16:31:26 Viper kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221)
sept. 23 16:31:26 Viper kernel: ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594)
sept. 23 16:31:26 Viper kernel: AMD-Vi: Unable to write to IOMMU perf counter.
sept. 23 16:31:26 Viper kernel: usbhid 1-14:1.2: couldn't find an input interrupt endpoint
sept. 23 16:31:26 Viper kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
sept. 23 16:31:26 Viper kernel: ata3.00: ATAPI: ASUS DRW-24B5ST, 1.00, max UDMA/100
sept. 23 16:31:26 Viper kernel: ata3.00: configured for UDMA/100
sept. 23 16:31:26 Viper kernel: scsi 2:0:0:0: CD-ROM ASUS DRW-24B5ST 1.00 PQ: 0 ANSI: 5
sept. 23 16:31:26 Viper kernel: ata4: SATA link down (SStatus 0 SControl 300)
sept. 23 16:31:26 Viper kernel: ata5: failed to resume link (SControl 0)
sept. 23 16:31:26 Viper kernel: ata5: SATA link down (SStatus 0 SControl 0)
sept. 23 16:31:26 Viper kernel: ata6: SATA link down (SStatus 0 SControl 330)
sept. 23 16:31:26 Viper kernel: ata7: SATA link down (SStatus 0 SControl 300)
sept. 23 16:31:26 Viper kernel: random: fast init done
sept. 23 16:31:26 Viper kernel: ata8: SATA link down (SStatus 0 SControl 300)
sept. 23 16:31:26 Viper kernel: sd 0:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
sept. 23 16:31:26 Viper kernel: sd 1:0:0:0: [sdb] 234441648 512-byte logical blocks: (120 GB/112 GiB)
sept. 23 16:31:26 Viper kernel: sd 1:0:0:0: [sdb] Write Protect is off
sept. 23 16:31:26 Viper kernel: sd 0:0:0:0: [sda] Write Protect is off
sept. 23 16:31:26 Viper kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sept. 23 16:31:26 Viper kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sept. 23 16:31:26 Viper kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sept. 23 16:31:26 Viper kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sept. 23 16:31:26 Viper kernel: sda: sda1 sda2
sept. 23 16:31:26 Viper kernel: sd 0:0:0:0: [sda] Attached SCSI disk
sept. 23 16:31:26 Viper kernel: sdb: sdb4
sept. 23 16:31:26 Viper kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
sept. 23 16:31:26 Viper kernel: sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
sept. 23 16:31:26 Viper kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
sept. 23 16:31:26 Viper kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
sept. 23 16:31:26 Viper kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
sept. 23 16:31:26 Viper systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GC>
sept. 23 16:31:26 Viper systemd[1]: Detected architecture x86-64.
sept. 23 16:31:26 Viper systemd[1]: Set hostname to <Viper>.
sept. 23 16:31:26 Viper kernel: random: systemd: uninitialized urandom read (16 bytes read)
sept. 23 16:31:26 Viper systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
sept. 23 16:31:26 Viper kernel: random: systemd: uninitialized urandom read (16 bytes read)
sept. 23 16:31:26 Viper systemd[1]: Listening on LVM2 metadata daemon socket.
sept. 23 16:31:26 Viper kernel: random: systemd: uninitialized urandom read (16 bytes read)
sept. 23 16:31:26 Viper systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
sept. 23 16:31:26 Viper systemd[1]: Listening on Process Core Dump Socket.
sept. 23 16:31:26 Viper systemd[1]: Created slice system-getty.slice.
sept. 23 16:31:26 Viper systemd[1]: Created slice User and Session Slice.
sept. 23 16:31:26 Viper systemd[1]: Reached target Login Prompts.
sept. 23 16:31:26 Viper kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
sept. 23 16:31:26 Viper kernel: audit: type=1130 audit(1537713086.254:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="syst>
sept. 23 16:31:26 Viper kernel: audit: type=1130 audit(1537713086.268:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed com>
sept. 23 16:31:26 Viper kernel: audit: type=1130 audit(1537713086.271:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="sy>
sept. 23 16:31:26 Viper kernel: audit: type=1130 audit(1537713086.274:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup->
sept. 23 16:31:26 Viper systemd-journald[255]: Journal started
sept. 23 16:31:26 Viper systemd-journald[255]: Runtime journal (/run/log/journal/a04cd6c2e6d04af4a6a2e7a336802aeb) is 8.0M, max 348.7M, 340.7M free.
sept. 23 16:31:26 Viper audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd>
sept. 23 16:31:26 Viper audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/>
sept. 23 16:31:26 Viper audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-binfmt comm="systemd" exe="/usr/lib/syste>
sept. 23 16:31:26 Viper audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/u>
sept. 23 16:31:26 Viper audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/sys>
sept. 23 16:31:26 Viper systemd[1]: Starting Flush Journal to Persistent Storage...
sept. 23 16:31:26 Viper kernel: audit: type=1130 audit(1537713086.288:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm=">
sept. 23 16:31:26 Viper systemd-journald[255]: Time spent on flushing to /var is 29.840ms for 913 entries.
During use :
-- Logs begin at Wed 2018-09-19 22:47:38 CEST, end at Mon 2018-09-24 07:40:01 C>
sept. 23 19:33:02 Viper kernel: iommu ivhd0: AMD-Vi: Event logged [
sept. 23 19:33:02 Viper kernel: iommu ivhd0: ILLEGAL_DEV_TABLE_ENTRY device=38:>
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[0]: 6010000000000003
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[1]: 0000000100000009
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[2]: 20000002131a0011
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[3]: 0000000000000000
sept. 23 19:33:12 Viper kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring>
sept. 23 19:33:12 Viper kernel: [drm] GPU recovery disabled.
sept. 23 19:38:08 Viper Thunar[1462]: JS method call SharedConnection.SendMsg w>
-- Reboot --
sept. 24 07:35:11 Viper kernel: Linux version 4.18.8-arch1-1-ARCH (builduser@he>
sept. 24 07:35:11 Viper kernel: Command line: root=UUID=d6871969-46ff-41ba-81d9>
sept. 24 07:35:11 Viper kernel: KERNEL supported cpus:
sept. 24 07:35:11 Viper kernel: Intel GenuineIntel
sept. 24 07:35:11 Viper kernel: AMD AuthenticAMD
sept. 24 07:35:11 Viper kernel: Centaur CentaurHauls
sept. 24 07:35:11 Viper kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 f>
sept. 24 07:35:11 Viper kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE r>
sept. 24 07:35:11 Viper kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX r>
sept. 24 07:35:11 Viper kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2>
sept. 24 07:35:11 Viper kernel: x86/fpu: Enabled xstate features 0x7, context s>
sept. 24 07:35:11 Viper kernel: BIOS-provided physical RAM map:
lines 1-23...skipping...
-- Logs begin at Wed 2018-09-19 22:47:38 CEST, end at Mon 2018-09-24 07:40:01 CEST. --
sept. 23 19:33:02 Viper kernel: iommu ivhd0: AMD-Vi: Event logged [
sept. 23 19:33:02 Viper kernel: iommu ivhd0: ILLEGAL_DEV_TABLE_ENTRY device=38:00.0 pasid=0x00000 address=0x000000018b94d000 flags=0x0180]
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[0]: 6010000000000003
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[1]: 0000000100000009
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[2]: 20000002131a0011
sept. 23 19:33:02 Viper kernel: AMD-Vi: DTE[3]: 0000000000000000
sept. 23 19:33:12 Viper kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=361020, last emitted seq=361022
sept. 23 19:33:12 Viper kernel: [drm] GPU recovery disabled.
sept. 23 19:38:08 Viper Thunar[1462]: JS method call SharedConnection.SendMsg with 2 arguments
My HW
-----------
CPU: Ryzen 1700x, old "faulty" type
MB: ASUS C6H with Agesa 1.0.0.2c UEFI
RAM: 2 x 16 GB Trident 3200
Graphics: Vega 64 (AMDGPU driver)
SDD: 512 GB PM961
NIC: Intel X520
As much as I want to switch to LXQT anyway, there is still too much missing for every day use :-(
Gnome is not my kind of thing, so the remaining option would be to go bach to XFCE which gets kind of old...
Any ideas would be highly welcome!
]]>...processor.nocst kernel parameters instead to impact cstates?
I'm trying `processor.nocst=1` to see if it helps. It suspends and shuts down properly, so now I just have to wait if I get a freeze. Unfortunately, I don't know how to reproduce the freeze and it's not that often (fortunatelly), so I will report back if it didn't help.
]]>My run failed with this output:
[loop-10] TIME TO FAIL: 158 s
[KERN] 2018-09-16T13:04:17-0400 boobytrap kernel: sh[16940]: segfault at dfdfdfde ip 000055e8a27d8ad6 sp 00007ffe4e0d1e30 error 6 in bash[55e8a2776000+cd000]
[KERN] 2018-09-16T13:04:17-0400 boobytrap kernel: Code: 48 63 05 59 87 27 00 8d 50 01 89 15 50 87 27 00 48 8b 15 3d 87 27 00 48 89 1c c2 e9 64 ff ff ff 0f 1f 40 00 48 89 df 67 e8 07 <86> 01 00 e9 52 ff ff ff 66 90 48 83 3d 28 87 27 00 00 74 26 53 8b
[KERN] 2018-09-16T13:04:17-0400 boobytrap kernel: audit: type=1701 audit(1537117457.508:57): auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=16940 comm="sh" exe="/usr/bin/bash" sig=11 res=1
I'm gonna try to capture some logs from a kernel panic still. I have journalctl printing out to TTY1. If that doesn't work I'll setup kdump. While my issue maybe different, I'm experiencing very similar symptoms so I thought this info may help either JonnyRobbie or thepanu.
UPDATE: I got a full system freeze since installing a Ryzen 7 2700x that passed the ryzen-test. Will comment bellow if I get more info.
]]>