Regular freezing on Ryzen based system, 16.04 LTS and newer kernelHow to update kernel to the latest mainline...

How to deny access to SQL Server to certain login over SSMS, but allow over .Net SqlClient Data Provider

I can't die. Who am I?

How would we write a misogynistic character without offending people?

Should I choose Itemized or Standard deduction?

How to avoid being sexist when trying to employ someone to function in a very sexist environment?

What can I substitute for soda pop in a sweet pork recipe?

Equivalent to "source" in OpenBSD?

You'll find me clean when something is full

What is better: yes / no radio, or simple checkbox?

If nine coins are tossed, what is the probability that the number of heads is even?

Is my plan for fixing my water heater leak bad?

Where is this triangular-shaped space station from?

Compare four integers, return word based on maximum

How to mitigate "bandwagon attacking" from players?

How can I be pwned if I'm not registered on that site?

Auto Insert date into Notepad

How to approximate rolls for potions of healing using only d6's?

What are these green text/line displays shown during the livestream of Crew Dragon's approach to dock with the ISS?

Multiplication via squaring and addition

Skis versus snow shoes - when to choose which for travelling the backcountry?

How can atoms be electrically neutral when there is a difference in the positions of the charges?

If a druid in Wild Shape swallows a creature whole, then turns back to her normal form, what happens?

How to speed up a process

Sometimes a banana is just a banana



Regular freezing on Ryzen based system, 16.04 LTS and newer kernel


How to update kernel to the latest mainline version without any Distro-upgrade?Random Crashes Ubuntu 12.04Ubuntu 16.04 LTS freezingUbuntu 16.04 seemingly random freezing on AMD systemMy NUC computer keeps freezing regularly. The syslog doesn't tell me anythingRandom freezing and crashes on 16.04Regular crash / freeze Ubuntu 16.04 LTS UnityUbuntu 16.04 LTS freezing randomlysystem freezes and kernel panicks ubuntu 16.04System Constantly Freezes with Ryzen x1700 and Ubuntu 18.04Ryzen System Freezing When Under Heavy Load













5















I am running Ryzen 1700X CPU and doing computations. Every now and then the system crashes, while running 16.04 LTS (Kernel 4.10). The system does not reboot. There is no signal on display and the keyboard + mouse do not work. I cannot connect via SSH.



I saved the kern.log and syslog files while running 16.04 LTS.



After reading several posts, and reading issues about the new architecture and issues, I decided to try more recent kernel and I moved to 4.12.8 (dated 16th Aug, 2017) from here.
I used this post on AskUbuntu to update the kernel.
System booted fine and my application ran fine for ~10 hours now.



After about ~11 hours system crashed again, with the same messages in the syslog as seen with kernel 4.10 on 16.04 LTS, given below. {Kernel and syslog files, with 4.12 kernel: kern.log with new kernel and syslog with new kernel }



Aug 18 17:27:13 vriksha systemd[1]: Starting Cleanup of Temporary Directories...
Aug 18 17:27:13 vriksha systemd-tmpfiles[4661]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Aug 18 17:27:13 vriksha systemd[1]: Started Cleanup of Temporary Directories.
Aug 18 17:28:25 vriksha ntpd[1516]: 209.242.224.117 local addr 192.168.2.15 -> <null>
Aug 18 17:35:01 vriksha CRON[4821]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:35:40 vriksha systemd[1]: Started Session 5 of user vani.
Aug 18 17:42:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 17:42:18 vriksha sensord: Adapter: PCI adapter
Aug 18 17:42:18 vriksha sensord: fan1: 1423 RPM
Aug 18 17:42:18 vriksha sensord: temp1: 43.0 C
Aug 18 17:42:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 17:42:18 vriksha sensord: Adapter: ISA adapter
Aug 18 17:42:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 17:45:01 vriksha CRON[6142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:55:01 vriksha CRON[6431]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:05:01 vriksha CRON[6607]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:09:52 vriksha kernel: [ 3459.913711] perf: interrupt took too long (2529 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Aug 18 18:12:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 18:12:18 vriksha sensord: Adapter: PCI adapter
Aug 18 18:12:18 vriksha sensord: fan1: 1431 RPM
Aug 18 18:12:18 vriksha sensord: temp1: 40.0 C
Aug 18 18:12:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 18:12:18 vriksha sensord: Adapter: ISA adapter
Aug 18 18:12:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 18:15:01 vriksha CRON[6785]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:17:01 vriksha CRON[6825]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 18 18:25:01 vriksha CRON[6967]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)


After the last line in the above message (in syslog) the system froze. I had to reset to reboot again. This happened again with the new kernel.



System details:



CPU-1700X Ryzen, No SMT, BIOS version- 3401 dated 12/08/2017 (AGESA 1071)
RAM 32 GB
AMD RX 470 GPU
Lubuntu 16.04 LTS, LXDE with Openbox


Can somebody help me out.





Updates



The application I am running is not using gcc, g++.




  1. lspci output is here.


  2. dmesg | egrep 'drm|radeon' output is here


  3. (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) is related to the sysstat package which I removed. The problem still exists.



  4. glxinfo | grep -i open output for AMD RX 470 GPU is given below



    glxinfo | grep -i open 
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.15.0 / 4.12.8-041208-generic, LLVM 4.0.0)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 17.0.7
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.7
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    OpenGL ES profile extensions:


  5. I have connected only one display to this computer. The crashes happen only when running CPU intensive tasks for long durations of time. ( I leave the system with its display off, controlling it, checking it from a SSH connection. After 5-6 hours or so, SSH connection becomes unavailable. After coming back to the machine, moving mouse and keyboard do nothing to bring the display back. A hard reset is required).



  6. To check if this is because of GPU or not, I changed to nVidia GTX 1080 for which I installed the proprietary driver and still under the similar load, the system freezes. I changed back to AMD GPU and there the problem persists. I rule out this behavior due to GPU build type. For the nVidia card the glxinfo | grep -i open output is following;



    OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
    OpenGL core profile version string: 4.5.0 NVIDIA 384.81
    OpenGL core profile shading language version string: 4.50 NVIDIA
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5.0 NVIDIA 384.81
    OpenGL shading language version string: 4.50 NVIDIA
    OpenGL context flags: (none)
    OpenGL profile mask: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.81
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:



    1. Updated the BIOS to version 3401 (12/08/2017, AGESA 1071) and the problem persists.












share|improve this question

























  • mine too 1600X '__') latest ubuntu 4.10.x kernel..

    – Kokizzu
    Aug 19 '17 at 5:03






  • 1





    I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

    – scottkosty
    Aug 23 '17 at 7:10











  • For graphics driver info, post info from the following command: glxinfo | grep -i open

    – scottkosty
    Aug 23 '17 at 7:11











  • glxinfo | grep -i open output is added in the update section of the question.

    – ankit7540
    Aug 23 '17 at 15:07
















5















I am running Ryzen 1700X CPU and doing computations. Every now and then the system crashes, while running 16.04 LTS (Kernel 4.10). The system does not reboot. There is no signal on display and the keyboard + mouse do not work. I cannot connect via SSH.



I saved the kern.log and syslog files while running 16.04 LTS.



After reading several posts, and reading issues about the new architecture and issues, I decided to try more recent kernel and I moved to 4.12.8 (dated 16th Aug, 2017) from here.
I used this post on AskUbuntu to update the kernel.
System booted fine and my application ran fine for ~10 hours now.



After about ~11 hours system crashed again, with the same messages in the syslog as seen with kernel 4.10 on 16.04 LTS, given below. {Kernel and syslog files, with 4.12 kernel: kern.log with new kernel and syslog with new kernel }



Aug 18 17:27:13 vriksha systemd[1]: Starting Cleanup of Temporary Directories...
Aug 18 17:27:13 vriksha systemd-tmpfiles[4661]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Aug 18 17:27:13 vriksha systemd[1]: Started Cleanup of Temporary Directories.
Aug 18 17:28:25 vriksha ntpd[1516]: 209.242.224.117 local addr 192.168.2.15 -> <null>
Aug 18 17:35:01 vriksha CRON[4821]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:35:40 vriksha systemd[1]: Started Session 5 of user vani.
Aug 18 17:42:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 17:42:18 vriksha sensord: Adapter: PCI adapter
Aug 18 17:42:18 vriksha sensord: fan1: 1423 RPM
Aug 18 17:42:18 vriksha sensord: temp1: 43.0 C
Aug 18 17:42:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 17:42:18 vriksha sensord: Adapter: ISA adapter
Aug 18 17:42:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 17:45:01 vriksha CRON[6142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:55:01 vriksha CRON[6431]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:05:01 vriksha CRON[6607]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:09:52 vriksha kernel: [ 3459.913711] perf: interrupt took too long (2529 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Aug 18 18:12:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 18:12:18 vriksha sensord: Adapter: PCI adapter
Aug 18 18:12:18 vriksha sensord: fan1: 1431 RPM
Aug 18 18:12:18 vriksha sensord: temp1: 40.0 C
Aug 18 18:12:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 18:12:18 vriksha sensord: Adapter: ISA adapter
Aug 18 18:12:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 18:15:01 vriksha CRON[6785]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:17:01 vriksha CRON[6825]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 18 18:25:01 vriksha CRON[6967]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)


After the last line in the above message (in syslog) the system froze. I had to reset to reboot again. This happened again with the new kernel.



System details:



CPU-1700X Ryzen, No SMT, BIOS version- 3401 dated 12/08/2017 (AGESA 1071)
RAM 32 GB
AMD RX 470 GPU
Lubuntu 16.04 LTS, LXDE with Openbox


Can somebody help me out.





Updates



The application I am running is not using gcc, g++.




  1. lspci output is here.


  2. dmesg | egrep 'drm|radeon' output is here


  3. (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) is related to the sysstat package which I removed. The problem still exists.



  4. glxinfo | grep -i open output for AMD RX 470 GPU is given below



    glxinfo | grep -i open 
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.15.0 / 4.12.8-041208-generic, LLVM 4.0.0)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 17.0.7
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.7
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    OpenGL ES profile extensions:


  5. I have connected only one display to this computer. The crashes happen only when running CPU intensive tasks for long durations of time. ( I leave the system with its display off, controlling it, checking it from a SSH connection. After 5-6 hours or so, SSH connection becomes unavailable. After coming back to the machine, moving mouse and keyboard do nothing to bring the display back. A hard reset is required).



  6. To check if this is because of GPU or not, I changed to nVidia GTX 1080 for which I installed the proprietary driver and still under the similar load, the system freezes. I changed back to AMD GPU and there the problem persists. I rule out this behavior due to GPU build type. For the nVidia card the glxinfo | grep -i open output is following;



    OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
    OpenGL core profile version string: 4.5.0 NVIDIA 384.81
    OpenGL core profile shading language version string: 4.50 NVIDIA
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5.0 NVIDIA 384.81
    OpenGL shading language version string: 4.50 NVIDIA
    OpenGL context flags: (none)
    OpenGL profile mask: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.81
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:



    1. Updated the BIOS to version 3401 (12/08/2017, AGESA 1071) and the problem persists.












share|improve this question

























  • mine too 1600X '__') latest ubuntu 4.10.x kernel..

    – Kokizzu
    Aug 19 '17 at 5:03






  • 1





    I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

    – scottkosty
    Aug 23 '17 at 7:10











  • For graphics driver info, post info from the following command: glxinfo | grep -i open

    – scottkosty
    Aug 23 '17 at 7:11











  • glxinfo | grep -i open output is added in the update section of the question.

    – ankit7540
    Aug 23 '17 at 15:07














5












5








5


5






I am running Ryzen 1700X CPU and doing computations. Every now and then the system crashes, while running 16.04 LTS (Kernel 4.10). The system does not reboot. There is no signal on display and the keyboard + mouse do not work. I cannot connect via SSH.



I saved the kern.log and syslog files while running 16.04 LTS.



After reading several posts, and reading issues about the new architecture and issues, I decided to try more recent kernel and I moved to 4.12.8 (dated 16th Aug, 2017) from here.
I used this post on AskUbuntu to update the kernel.
System booted fine and my application ran fine for ~10 hours now.



After about ~11 hours system crashed again, with the same messages in the syslog as seen with kernel 4.10 on 16.04 LTS, given below. {Kernel and syslog files, with 4.12 kernel: kern.log with new kernel and syslog with new kernel }



Aug 18 17:27:13 vriksha systemd[1]: Starting Cleanup of Temporary Directories...
Aug 18 17:27:13 vriksha systemd-tmpfiles[4661]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Aug 18 17:27:13 vriksha systemd[1]: Started Cleanup of Temporary Directories.
Aug 18 17:28:25 vriksha ntpd[1516]: 209.242.224.117 local addr 192.168.2.15 -> <null>
Aug 18 17:35:01 vriksha CRON[4821]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:35:40 vriksha systemd[1]: Started Session 5 of user vani.
Aug 18 17:42:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 17:42:18 vriksha sensord: Adapter: PCI adapter
Aug 18 17:42:18 vriksha sensord: fan1: 1423 RPM
Aug 18 17:42:18 vriksha sensord: temp1: 43.0 C
Aug 18 17:42:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 17:42:18 vriksha sensord: Adapter: ISA adapter
Aug 18 17:42:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 17:45:01 vriksha CRON[6142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:55:01 vriksha CRON[6431]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:05:01 vriksha CRON[6607]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:09:52 vriksha kernel: [ 3459.913711] perf: interrupt took too long (2529 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Aug 18 18:12:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 18:12:18 vriksha sensord: Adapter: PCI adapter
Aug 18 18:12:18 vriksha sensord: fan1: 1431 RPM
Aug 18 18:12:18 vriksha sensord: temp1: 40.0 C
Aug 18 18:12:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 18:12:18 vriksha sensord: Adapter: ISA adapter
Aug 18 18:12:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 18:15:01 vriksha CRON[6785]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:17:01 vriksha CRON[6825]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 18 18:25:01 vriksha CRON[6967]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)


After the last line in the above message (in syslog) the system froze. I had to reset to reboot again. This happened again with the new kernel.



System details:



CPU-1700X Ryzen, No SMT, BIOS version- 3401 dated 12/08/2017 (AGESA 1071)
RAM 32 GB
AMD RX 470 GPU
Lubuntu 16.04 LTS, LXDE with Openbox


Can somebody help me out.





Updates



The application I am running is not using gcc, g++.




  1. lspci output is here.


  2. dmesg | egrep 'drm|radeon' output is here


  3. (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) is related to the sysstat package which I removed. The problem still exists.



  4. glxinfo | grep -i open output for AMD RX 470 GPU is given below



    glxinfo | grep -i open 
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.15.0 / 4.12.8-041208-generic, LLVM 4.0.0)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 17.0.7
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.7
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    OpenGL ES profile extensions:


  5. I have connected only one display to this computer. The crashes happen only when running CPU intensive tasks for long durations of time. ( I leave the system with its display off, controlling it, checking it from a SSH connection. After 5-6 hours or so, SSH connection becomes unavailable. After coming back to the machine, moving mouse and keyboard do nothing to bring the display back. A hard reset is required).



  6. To check if this is because of GPU or not, I changed to nVidia GTX 1080 for which I installed the proprietary driver and still under the similar load, the system freezes. I changed back to AMD GPU and there the problem persists. I rule out this behavior due to GPU build type. For the nVidia card the glxinfo | grep -i open output is following;



    OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
    OpenGL core profile version string: 4.5.0 NVIDIA 384.81
    OpenGL core profile shading language version string: 4.50 NVIDIA
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5.0 NVIDIA 384.81
    OpenGL shading language version string: 4.50 NVIDIA
    OpenGL context flags: (none)
    OpenGL profile mask: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.81
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:



    1. Updated the BIOS to version 3401 (12/08/2017, AGESA 1071) and the problem persists.












share|improve this question
















I am running Ryzen 1700X CPU and doing computations. Every now and then the system crashes, while running 16.04 LTS (Kernel 4.10). The system does not reboot. There is no signal on display and the keyboard + mouse do not work. I cannot connect via SSH.



I saved the kern.log and syslog files while running 16.04 LTS.



After reading several posts, and reading issues about the new architecture and issues, I decided to try more recent kernel and I moved to 4.12.8 (dated 16th Aug, 2017) from here.
I used this post on AskUbuntu to update the kernel.
System booted fine and my application ran fine for ~10 hours now.



After about ~11 hours system crashed again, with the same messages in the syslog as seen with kernel 4.10 on 16.04 LTS, given below. {Kernel and syslog files, with 4.12 kernel: kern.log with new kernel and syslog with new kernel }



Aug 18 17:27:13 vriksha systemd[1]: Starting Cleanup of Temporary Directories...
Aug 18 17:27:13 vriksha systemd-tmpfiles[4661]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Aug 18 17:27:13 vriksha systemd[1]: Started Cleanup of Temporary Directories.
Aug 18 17:28:25 vriksha ntpd[1516]: 209.242.224.117 local addr 192.168.2.15 -> <null>
Aug 18 17:35:01 vriksha CRON[4821]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:35:40 vriksha systemd[1]: Started Session 5 of user vani.
Aug 18 17:42:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 17:42:18 vriksha sensord: Adapter: PCI adapter
Aug 18 17:42:18 vriksha sensord: fan1: 1423 RPM
Aug 18 17:42:18 vriksha sensord: temp1: 43.0 C
Aug 18 17:42:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 17:42:18 vriksha sensord: Adapter: ISA adapter
Aug 18 17:42:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 17:45:01 vriksha CRON[6142]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 17:55:01 vriksha CRON[6431]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:05:01 vriksha CRON[6607]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:09:52 vriksha kernel: [ 3459.913711] perf: interrupt took too long (2529 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Aug 18 18:12:18 vriksha sensord: Chip: amdgpu-pci-2700
Aug 18 18:12:18 vriksha sensord: Adapter: PCI adapter
Aug 18 18:12:18 vriksha sensord: fan1: 1431 RPM
Aug 18 18:12:18 vriksha sensord: temp1: 40.0 C
Aug 18 18:12:18 vriksha sensord: Chip: asus-isa-0000
Aug 18 18:12:18 vriksha sensord: Adapter: ISA adapter
Aug 18 18:12:18 vriksha sensord: cpu_fan: 0 RPM
Aug 18 18:15:01 vriksha CRON[6785]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Aug 18 18:17:01 vriksha CRON[6825]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 18 18:25:01 vriksha CRON[6967]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)


After the last line in the above message (in syslog) the system froze. I had to reset to reboot again. This happened again with the new kernel.



System details:



CPU-1700X Ryzen, No SMT, BIOS version- 3401 dated 12/08/2017 (AGESA 1071)
RAM 32 GB
AMD RX 470 GPU
Lubuntu 16.04 LTS, LXDE with Openbox


Can somebody help me out.





Updates



The application I am running is not using gcc, g++.




  1. lspci output is here.


  2. dmesg | egrep 'drm|radeon' output is here


  3. (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) is related to the sysstat package which I removed. The problem still exists.



  4. glxinfo | grep -i open output for AMD RX 470 GPU is given below



    glxinfo | grep -i open 
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.15.0 / 4.12.8-041208-generic, LLVM 4.0.0)
    OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7
    OpenGL core profile shading language version string: 4.50
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 17.0.7
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.0.7
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
    OpenGL ES profile extensions:


  5. I have connected only one display to this computer. The crashes happen only when running CPU intensive tasks for long durations of time. ( I leave the system with its display off, controlling it, checking it from a SSH connection. After 5-6 hours or so, SSH connection becomes unavailable. After coming back to the machine, moving mouse and keyboard do nothing to bring the display back. A hard reset is required).



  6. To check if this is because of GPU or not, I changed to nVidia GTX 1080 for which I installed the proprietary driver and still under the similar load, the system freezes. I changed back to AMD GPU and there the problem persists. I rule out this behavior due to GPU build type. For the nVidia card the glxinfo | grep -i open output is following;



    OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
    OpenGL core profile version string: 4.5.0 NVIDIA 384.81
    OpenGL core profile shading language version string: 4.50 NVIDIA
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.5.0 NVIDIA 384.81
    OpenGL shading language version string: 4.50 NVIDIA
    OpenGL context flags: (none)
    OpenGL profile mask: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.81
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:



    1. Updated the BIOS to version 3401 (12/08/2017, AGESA 1071) and the problem persists.









16.04 kernel freeze crash amd-processor






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 18 '17 at 12:11







ankit7540

















asked Aug 19 '17 at 3:57









ankit7540ankit7540

3,25311633




3,25311633













  • mine too 1600X '__') latest ubuntu 4.10.x kernel..

    – Kokizzu
    Aug 19 '17 at 5:03






  • 1





    I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

    – scottkosty
    Aug 23 '17 at 7:10











  • For graphics driver info, post info from the following command: glxinfo | grep -i open

    – scottkosty
    Aug 23 '17 at 7:11











  • glxinfo | grep -i open output is added in the update section of the question.

    – ankit7540
    Aug 23 '17 at 15:07



















  • mine too 1600X '__') latest ubuntu 4.10.x kernel..

    – Kokizzu
    Aug 19 '17 at 5:03






  • 1





    I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

    – scottkosty
    Aug 23 '17 at 7:10











  • For graphics driver info, post info from the following command: glxinfo | grep -i open

    – scottkosty
    Aug 23 '17 at 7:11











  • glxinfo | grep -i open output is added in the update section of the question.

    – ankit7540
    Aug 23 '17 at 15:07

















mine too 1600X '__') latest ubuntu 4.10.x kernel..

– Kokizzu
Aug 19 '17 at 5:03





mine too 1600X '__') latest ubuntu 4.10.x kernel..

– Kokizzu
Aug 19 '17 at 5:03




1




1





I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

– scottkosty
Aug 23 '17 at 7:10





I am not an expert at all, but until one comes along, here is my advice: collect your syslogs from 10 crashes. Look for patterns. Sometimes it's not obvious. e.g. it could be an error 300 lines before the crash that is the root issue. How many monitors are you using? Do you still see a crash if you disconnect all but one? Are you using the proprietary drivers for the Radeon? If so, is there a reason you're not using Mesa? Describe the crashes better. How often do they happen? Do they happen when you are using the computer? Browsing web? Video games?

– scottkosty
Aug 23 '17 at 7:10













For graphics driver info, post info from the following command: glxinfo | grep -i open

– scottkosty
Aug 23 '17 at 7:11





For graphics driver info, post info from the following command: glxinfo | grep -i open

– scottkosty
Aug 23 '17 at 7:11













glxinfo | grep -i open output is added in the update section of the question.

– ankit7540
Aug 23 '17 at 15:07





glxinfo | grep -i open output is added in the update section of the question.

– ankit7540
Aug 23 '17 at 15:07










3 Answers
3






active

oldest

votes


















4














I had the same problem... What I did to solve this issue:



Performance:



sudo cpufreq-set -r -g performance


Set on boot:



sudo apt-get install cpufrequtils
echo 'GOVERNOR="performance"' | sudo tee /etc/default/cpufrequtils
sudo systemctl disable ondemand





share|improve this answer


























  • I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

    – ankit7540
    Oct 18 '18 at 2:46





















1














I had kind of the same problem as you. Ryzen 1800x



I suggest you to:



Re-enable SMT - No need to disable it.



Go back to the normal current kernel for Ubuntu 16.04 which is currently 4.4.0-93



Disable all "power saving" Global C-State options in BIOS.



Disable cool n quiet option as well.



Increase the voltage of your SoC to 1.1 for stability, this is recommended.
As stated in this video: https://www.hardocp.com/news/2017/05/01/how_to_stabilize_your_amd_ryzen_memory_cpu_overclocking_attempts



The above recommendation is valid for if you are stressing the CPU or if you are idling.



Download latest AMD Drivers on the AMD website for your card.
You can also try the latest open-source drivers via: "Additional Drivers" under "Software & Updates". I recommend this option first.



Before doing the above, just reset the BIOS to default and check if there is a newer version available.






share|improve this answer
























  • I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

    – ankit7540
    Sep 15 '17 at 11:15



















0














I have a ryzen 5 1600x and I've been struggling with this for about a year. I've been hoping a bios or os update would fix this, however none of the many updates ever helped.



I'm not sure why it took me so long to notice, but I saw debian-sa1 in /var/log/syslog followed by silence until a reboot. So, I disabled the cron entries in /etc/cron.d/sysstat and the problem appears to be resolved! Not sure what I'm missing by disabling sysstat, but I don't miss it yet.






share|improve this answer








New contributor




chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f947680%2fregular-freezing-on-ryzen-based-system-16-04-lts-and-newer-kernel%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    I had the same problem... What I did to solve this issue:



    Performance:



    sudo cpufreq-set -r -g performance


    Set on boot:



    sudo apt-get install cpufrequtils
    echo 'GOVERNOR="performance"' | sudo tee /etc/default/cpufrequtils
    sudo systemctl disable ondemand





    share|improve this answer


























    • I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

      – ankit7540
      Oct 18 '18 at 2:46


















    4














    I had the same problem... What I did to solve this issue:



    Performance:



    sudo cpufreq-set -r -g performance


    Set on boot:



    sudo apt-get install cpufrequtils
    echo 'GOVERNOR="performance"' | sudo tee /etc/default/cpufrequtils
    sudo systemctl disable ondemand





    share|improve this answer


























    • I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

      – ankit7540
      Oct 18 '18 at 2:46
















    4












    4








    4







    I had the same problem... What I did to solve this issue:



    Performance:



    sudo cpufreq-set -r -g performance


    Set on boot:



    sudo apt-get install cpufrequtils
    echo 'GOVERNOR="performance"' | sudo tee /etc/default/cpufrequtils
    sudo systemctl disable ondemand





    share|improve this answer















    I had the same problem... What I did to solve this issue:



    Performance:



    sudo cpufreq-set -r -g performance


    Set on boot:



    sudo apt-get install cpufrequtils
    echo 'GOVERNOR="performance"' | sudo tee /etc/default/cpufrequtils
    sudo systemctl disable ondemand






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 5 '18 at 4:44









    Henry WH Hack v2.1.2

    50351123




    50351123










    answered Oct 5 '18 at 1:41









    Omar PalamingOmar Palaming

    412




    412













    • I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

      – ankit7540
      Oct 18 '18 at 2:46





















    • I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

      – ankit7540
      Oct 18 '18 at 2:46



















    I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

    – ankit7540
    Oct 18 '18 at 2:46







    I tried this. After running sudo systemctl disable ondemand, I received ondemand.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable ondemand insserv: warning: current start runlevel(s) (empty) of script ondemand overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (2 3 4 5) of script ondemand overrides LSB defaults (empty). Is this normal.

    – ankit7540
    Oct 18 '18 at 2:46















    1














    I had kind of the same problem as you. Ryzen 1800x



    I suggest you to:



    Re-enable SMT - No need to disable it.



    Go back to the normal current kernel for Ubuntu 16.04 which is currently 4.4.0-93



    Disable all "power saving" Global C-State options in BIOS.



    Disable cool n quiet option as well.



    Increase the voltage of your SoC to 1.1 for stability, this is recommended.
    As stated in this video: https://www.hardocp.com/news/2017/05/01/how_to_stabilize_your_amd_ryzen_memory_cpu_overclocking_attempts



    The above recommendation is valid for if you are stressing the CPU or if you are idling.



    Download latest AMD Drivers on the AMD website for your card.
    You can also try the latest open-source drivers via: "Additional Drivers" under "Software & Updates". I recommend this option first.



    Before doing the above, just reset the BIOS to default and check if there is a newer version available.






    share|improve this answer
























    • I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

      – ankit7540
      Sep 15 '17 at 11:15
















    1














    I had kind of the same problem as you. Ryzen 1800x



    I suggest you to:



    Re-enable SMT - No need to disable it.



    Go back to the normal current kernel for Ubuntu 16.04 which is currently 4.4.0-93



    Disable all "power saving" Global C-State options in BIOS.



    Disable cool n quiet option as well.



    Increase the voltage of your SoC to 1.1 for stability, this is recommended.
    As stated in this video: https://www.hardocp.com/news/2017/05/01/how_to_stabilize_your_amd_ryzen_memory_cpu_overclocking_attempts



    The above recommendation is valid for if you are stressing the CPU or if you are idling.



    Download latest AMD Drivers on the AMD website for your card.
    You can also try the latest open-source drivers via: "Additional Drivers" under "Software & Updates". I recommend this option first.



    Before doing the above, just reset the BIOS to default and check if there is a newer version available.






    share|improve this answer
























    • I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

      – ankit7540
      Sep 15 '17 at 11:15














    1












    1








    1







    I had kind of the same problem as you. Ryzen 1800x



    I suggest you to:



    Re-enable SMT - No need to disable it.



    Go back to the normal current kernel for Ubuntu 16.04 which is currently 4.4.0-93



    Disable all "power saving" Global C-State options in BIOS.



    Disable cool n quiet option as well.



    Increase the voltage of your SoC to 1.1 for stability, this is recommended.
    As stated in this video: https://www.hardocp.com/news/2017/05/01/how_to_stabilize_your_amd_ryzen_memory_cpu_overclocking_attempts



    The above recommendation is valid for if you are stressing the CPU or if you are idling.



    Download latest AMD Drivers on the AMD website for your card.
    You can also try the latest open-source drivers via: "Additional Drivers" under "Software & Updates". I recommend this option first.



    Before doing the above, just reset the BIOS to default and check if there is a newer version available.






    share|improve this answer













    I had kind of the same problem as you. Ryzen 1800x



    I suggest you to:



    Re-enable SMT - No need to disable it.



    Go back to the normal current kernel for Ubuntu 16.04 which is currently 4.4.0-93



    Disable all "power saving" Global C-State options in BIOS.



    Disable cool n quiet option as well.



    Increase the voltage of your SoC to 1.1 for stability, this is recommended.
    As stated in this video: https://www.hardocp.com/news/2017/05/01/how_to_stabilize_your_amd_ryzen_memory_cpu_overclocking_attempts



    The above recommendation is valid for if you are stressing the CPU or if you are idling.



    Download latest AMD Drivers on the AMD website for your card.
    You can also try the latest open-source drivers via: "Additional Drivers" under "Software & Updates". I recommend this option first.



    Before doing the above, just reset the BIOS to default and check if there is a newer version available.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Sep 13 '17 at 21:20









    User08721User08721

    111




    111













    • I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

      – ankit7540
      Sep 15 '17 at 11:15



















    • I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

      – ankit7540
      Sep 15 '17 at 11:15

















    I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

    – ankit7540
    Sep 15 '17 at 11:15





    I disabled SMT intentionally since the application(s) I use may suffer from cache miss and hence the numerical accuracy of results. These scenario happens in high performance computing when parallel computations for long duration.

    – ankit7540
    Sep 15 '17 at 11:15











    0














    I have a ryzen 5 1600x and I've been struggling with this for about a year. I've been hoping a bios or os update would fix this, however none of the many updates ever helped.



    I'm not sure why it took me so long to notice, but I saw debian-sa1 in /var/log/syslog followed by silence until a reboot. So, I disabled the cron entries in /etc/cron.d/sysstat and the problem appears to be resolved! Not sure what I'm missing by disabling sysstat, but I don't miss it yet.






    share|improve this answer








    New contributor




    chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      I have a ryzen 5 1600x and I've been struggling with this for about a year. I've been hoping a bios or os update would fix this, however none of the many updates ever helped.



      I'm not sure why it took me so long to notice, but I saw debian-sa1 in /var/log/syslog followed by silence until a reboot. So, I disabled the cron entries in /etc/cron.d/sysstat and the problem appears to be resolved! Not sure what I'm missing by disabling sysstat, but I don't miss it yet.






      share|improve this answer








      New contributor




      chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        I have a ryzen 5 1600x and I've been struggling with this for about a year. I've been hoping a bios or os update would fix this, however none of the many updates ever helped.



        I'm not sure why it took me so long to notice, but I saw debian-sa1 in /var/log/syslog followed by silence until a reboot. So, I disabled the cron entries in /etc/cron.d/sysstat and the problem appears to be resolved! Not sure what I'm missing by disabling sysstat, but I don't miss it yet.






        share|improve this answer








        New contributor




        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        I have a ryzen 5 1600x and I've been struggling with this for about a year. I've been hoping a bios or os update would fix this, however none of the many updates ever helped.



        I'm not sure why it took me so long to notice, but I saw debian-sa1 in /var/log/syslog followed by silence until a reboot. So, I disabled the cron entries in /etc/cron.d/sysstat and the problem appears to be resolved! Not sure what I'm missing by disabling sysstat, but I don't miss it yet.







        share|improve this answer








        New contributor




        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 14 mins ago









        chevettchevett

        1012




        1012




        New contributor




        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        chevett is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f947680%2fregular-freezing-on-ryzen-based-system-16-04-lts-and-newer-kernel%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            List of shipwrecks in 1808...

            Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

            Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...