Two hard freezes and systemctl shows two different results.

---

Hello everyone

So I am running Antergos on a new laptop (Acer Aspier 3 A315-41 with Ryzen 5 2400U). Today I have had two hard freezes about 4 hours between. I took down information from systemctl around both freezes.
The first one:

júl 09 11:03:16 OVG-ACER org_kde_powerdevil[850]: powerdevil: Restoring DPMS features after inhibition release
júl 09 11:03:16 OVG-ACER org_kde_powerdevil[850]: powerdevil: Can't contact ck
júl 09 11:03:16 OVG-ACER org_kde_powerdevil[850]: powerdevil: Can't contact ck
júl 09 11:03:16 OVG-ACER org_kde_powerdevil[850]: powerdevil: Scheduling inhibition from ":1.13" "firefox" with cookie 4 and reason "audio-playing"
júl 09 11:03:21 OVG-ACER org_kde_powerdevil[850]: powerdevil: Enforcing inhibition from ":1.13" "firefox" with cookie 4 and reason "audio-playing"
júl 09 11:03:21 OVG-ACER org_kde_powerdevil[850]: powerdevil: Added change screen settings
júl 09 10:20:14 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000f(Transmitter ID)
júl 09 10:20:14 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00001000/00006000
júl 09 10:20:14 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 10:23:00 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 10:23:00 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000f(Transmitter ID)
júl 09 10:23:00 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00001000/00006000
júl 09 10:23:00 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 10:23:16 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 10:23:16 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000f(Transmitter ID)
júl 09 10:23:16 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00001000/00006000
júl 09 10:23:16 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 10:23:22 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 10:23:22 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000f(Transmitter ID)
júl 09 10:23:22 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=00001000/00006000
júl 09 10:23:22 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
-- Reboot --
júl 09 10:40:13 OVG-ACER kernel: Linux version 4.17.4-1-ARCH ([email protected]) (gcc version 8.1.1 20180531 (GCC)) #1 SMP PREEMPT Tue Jul 3 15:45:09 UTC 2018

And the second one:

júl 09 13:48:53 OVG-ACER org_kde_powerdevil[850]: powerdevil: Disabling DPMS due to inhibition
júl 09 13:48:53 OVG-ACER org_kde_powerdevil[850]: powerdevil: Can't contact ck
júl 09 13:50:21 OVG-ACER org_kde_powerdevil[850]: powerdevil: Releasing inhibition with cookie  89
júl 09 13:50:21 OVG-ACER org_kde_powerdevil[850]: powerdevil: Restoring DPMS features after inhibition release
júl 09 13:50:21 OVG-ACER org_kde_powerdevil[850]: powerdevil: Can't contact ck
júl 09 13:50:50 OVG-ACER wpa_supplicant[560]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:95:26:d4 [GTK=CCMP]
-- Reboot --
júl 09 13:54:19 OVG-ACER kernel: Linux version 4.17.4-1-ARCH ([email protected]) (gcc version 8.1.1 20180531 (GCC)) #1 SMP PREEMPT Tue Jul 3 15:45:09 UTC 2018
júl 09 13:54:19 OVG-ACER kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5a173693-9d59-4479-8b85-c65cd9313f99 rw quiet resume=UUID=1d5fdce5-e392-46b0-b95c-8fdaaf61c9b0

Yesterday my computer also froze, but at that time I didn’t think of it. The first freeze happened while I had to go away from the computer for a while, the second happened while I was listening to a podcast from the internet. This freezing seems to be happening randomly.

Note, the second time the computer froze, the time was 13:54 when the computer got unresponsive, so something might have happened which isn’t shown in the log.

Besides those freezing issues, I really like Antergos, and I really hope that this issue will get sorted.

And the third freeze just happened, while I was answering a post here.

The system did not freeze the first 2 days of operation, could an update have these affects?

júl 09 14:58:32 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 14:58:32 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 14:58:32 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 14:58:32 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:00:59 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:00:59 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:00:59 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:00:59 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:02:25 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:02:25 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:02:25 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:02:25 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:03:18 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:03:18 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:03:18 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:03:18 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:04:10 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:04:10 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:04:10 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:04:10 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:05:14 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:05:14 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:05:14 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:05:14 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:16 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:17 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), s>
júl 09 15:06:17 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), se>
júl 09 15:06:17 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), se>
júl 09 15:06:18 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), se>
júl 09 15:06:19 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), se>
júl 09 15:06:19 OVG-ACER plasmashell[827]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), se>
júl 09 15:06:21 OVG-ACER plasmashell[827]: org.kde.plasmaquick: Applet "Forritaræsir" loaded after>
júl 09 15:06:21 OVG-ACER plasmashell[827]: org.kde.plasmaquick: Increasing score for "Forritaræsir>
júl 09 15:06:22 OVG-ACER kernel: pcieport 0000:00:01.7: AER: Corrected error received: id=0008
júl 09 15:06:22 OVG-ACER kernel: pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=D>
júl 09 15:06:22 OVG-ACER kernel: pcieport 0000:00:01.7:   device [1022:15d3] error status/mask=000>
júl 09 15:06:22 OVG-ACER kernel: pcieport 0000:00:01.7:    [12] Replay Timer Timeout  
júl 09 15:06:23 OVG-ACER kwin_x11[821]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequ>
júl 09 15:06:23 OVG-ACER dbus-daemon[729]: [session uid=1000 pid=729] Activating service name='org>
júl 09 15:06:24 OVG-ACER dbus-daemon[729]: [session uid=1000 pid=729] Successfully activated servi>
-- Reboot --

So in the end I gave up and installed Antergos with Deepin desktop. The desktop I was coming from was KDE.
I will update if I will continue having these freezing problems.

So I am guessing that I installed Intel microcode which affected my Ryzen system. It is possible to remove packages in update manager and it is also have it ignore Intel updates in settings.

This link might help:
https://forum.antergos.com/topic/10264/update-manager-wants-to-install-intel-driver-for-my-ryzen-apu

@developers is intel-ucode installed by default? or by checking hardware?

@developers
I made a mistake, sorry.

So the intel-ucode was a package that I had to install.

I was installing the KDE DE again and disabled the intel-ucode upgrade. Still my computer froze again. So it is not the code, it is something in the KDE environment which affects my computer. I also had bad crashes using GNOME DE.

I was just getting my computer back with the Deepin DE so I haven’t been able to edit my post.

I am very sorry for jumping to conclusion.

Thanks for clearification :)

@developers

I have now had hard freezes with Antergos KDE DE, Antergos GNOME DE and Antergos Deepin DE. I will try some other OS and see if this resolves that way.

Hi,

Having no idea of that what’s causing those crashes, a wild guess would be some kind of problem with the newest version of the kernel. I know it’s too late and you probably have moved to another distro, but installing the LTS kernel maybe would have helped.

Also, using the amdgpu driver maybe would have helped (who knows).

Cheers!

Probably for my old computer yes :)

But I somehow managed to brick my Mint boot (was messing with it) so I am installing the OS there now

Anyway, Deepin DE works fine for me on my laptop.

I hope you figure something out :)

@developers

Greetings, so I figured out that I need kernel 4.17 to install Linux on my new computer (the one with the freezes).

I am running Antergos again and I have set up the amdgpu driver.

I have also checking for a solution to this problem:

AMD-Vi: IOAPIC[4] not in IVRS table

I used the change to grub provided in this thread.:
https://ubuntuforums.org/showthread.php?t=2254677

What do you say that I check how the computer performs next week or so and monitor freezes.

BTW, I am loving the MATE desktop on Antergos

So I did continue to have CPU soft lockup, so I installed Antergos one more time. I have installed amdgpu driver.
Then I found this post:
https://forum.level1techs.com/t/ryzen-vega-laptop-pcie-bus-error/124661/58
Where a change to grub seems to work by putting processor.max_cstate=1 to /etc/default/grub and then upgrading grub.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash processor.max_cstate=1"

This workaround worked for another person with the same computer running Linux Mint 19

@olividir do you try this solution already and does it work for you? Or do you have any question on how to do it?

@joekamprad
I am have done these changes, and for the first time in a long time I have not noticed any soft lockup on my CPU.

I have have heard of a code which can help with power optimization. I am not sure how to implement that, because I would be adding some commands to the kernel, and I am a bit hesitate to do so.
The first comment in this post mentions these changes:

CONFIG_RCU_EXPERT=y
CONFIG_RCU_NOCB_CPU=y

and to add this line rcu_nocbs=0-15
Link:
https://plus.google.com/u/0/+ÓlafurViðir/posts/8J6GtrZWjoJ

If you could share your experience about adding to the kernel, I would appreciate :)