Commen=
t # 3
on bug 10953=
9
from jon
>The freezing doesn't seem to be nece=
ssarily caused by by something in amdgpu >from a glance at your log.
I thought the same thing, but after disabling direct code I went from the
system freezing up to 5 or 6 times a day, depending on use, every day to ha=
ving
an uptime over 2 days and 4 hours now. So there's no question that disabli=
ng
direct code solved the problem. It is night and day after that change.
>There are some DC warnings/errors that describe w=
hat you're seeing with your monitor not waking from sleep however.
>
>Please post a full dmesg log from system boot and=
an xorg log if you're using X. >It may also help to know what window ma=
nager you're using when you see this >issue occur.
I am using X and my window manager is dwm. I will attach an Xorg log as we=
ll
as dmesg. Keep in mind these will be the most recent logs with direct code
disabled, which may not matter, just wanted to be clear.=20=20
>Does adding idle=3Dnomwait to the kernel command =
line in grub help?
No, according to my notes I added idle=3Dnomwait on 1/31/19 and experienced=
many
freezes per day since then. I also used the following kernel boot paramete=
rs,
which had no affect:
rcu_nocbs=3D0-15
processor.max_cstate=3D5
All three of these, along with disabling direct code, are still in my kernel
boot parameters. None of those had any affect, frequent crashes still. Af=
ter
disabling direct code and restarting I have not had one freeze yet. Stabil=
ity
went from a couple of hours (usually long enough for me to be away from it =
long
enough to sleep) to an uptime of >2 days.