dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109539] System freezing
Date: Mon, 04 Feb 2019 23:49:37 +0000	[thread overview]
Message-ID: <bug-109539-502-cGkAvrZQ85@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109539-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1773 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109539

--- Comment #3 from jon <jon780@gmail.com> ---
>The freezing doesn't seem to be necessarily 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 having
an uptime over 2 days and 4 hours now.  So there's no question that disabling
direct code solved the problem.  It is night and day after that change.

>There are some DC warnings/errors that describe what 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 manager 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 well
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.  

>Does adding idle=nomwait to the kernel command line in grub help?

No, according to my notes I added idle=nomwait on 1/31/19 and experienced many
freezes per day since then.  I also used the following kernel boot parameters,
which had no affect:

rcu_nocbs=0-15
processor.max_cstate=5

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.  After
disabling direct code and restarting I have not had one freeze yet.  Stability
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2615 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-04 23:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 20:36 [Bug 109539] System freezing bugzilla-daemon
2019-02-04 11:35 ` bugzilla-daemon
2019-02-04 15:35 ` bugzilla-daemon
2019-02-04 19:02 ` bugzilla-daemon
2019-02-04 23:49 ` bugzilla-daemon [this message]
2019-02-04 23:52 ` bugzilla-daemon
2019-02-04 23:53 ` bugzilla-daemon
2019-02-05 17:07 ` bugzilla-daemon
2019-02-10 14:40 ` bugzilla-daemon
2019-02-12  1:45 ` bugzilla-daemon
2019-02-12  1:46 ` bugzilla-daemon
2019-11-19  9:12 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109539-502-cGkAvrZQ85@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox