dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199749] amdgpu on Ryzen 2400G freeze randomly
Date: Wed, 27 Jun 2018 13:39:06 +0000	[thread overview]
Message-ID: <bug-199749-2300-MxvaDsnTPG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199749-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=199749

--- Comment #24 from Andrey Grodzovsky (andrey.grodzovsky@amd.com) ---

(In reply to notsyncing from comment #23)
> In fact there is no specified graphic work. I just put an Android source
> compilation running and go to bed, besides only firefox and dolphin running.
> The next morning, I found the machine has already freezed. Still no log. The
> log I posted is just a lucky one.
> 
> Would you mind telling me if the umr had some system-wide debugging methods?
> Or should I make a netconsole to see if there was anything?

UMR is system wide any way, it's memory/registers/HW debugging tool. you can
provide the UMR outputs I asked before once the freeze happened assuming you
still have SSH access (which seems like you don't).

Since the memory faults you experience are clearly due to some graphic
rendering activity maybe you could try to isolate the app which triggers it,
repeat what you do but close both firefox and dolphin and check if this still
happens. If not try to find which of them was causing this and then we can run
it with MESA debug flags.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-27 13:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  9:21 [Bug 199749] New: amdgpu on Ryzen 2400G freeze randomly bugzilla-daemon
2018-06-12 21:27 ` [Bug 199749] " bugzilla-daemon
2018-06-13  7:17 ` bugzilla-daemon
2018-06-16 15:47 ` bugzilla-daemon
2018-06-16 16:29 ` bugzilla-daemon
2018-06-16 18:24 ` bugzilla-daemon
2018-06-16 18:31 ` bugzilla-daemon
2018-06-16 18:59 ` bugzilla-daemon
2018-06-17  9:37 ` bugzilla-daemon
2018-06-17  9:41 ` bugzilla-daemon
2018-06-18  6:16 ` bugzilla-daemon
2018-06-18  8:55 ` bugzilla-daemon
2018-06-21 13:34 ` bugzilla-daemon
2018-06-21 16:23 ` bugzilla-daemon
2018-06-24  6:12 ` bugzilla-daemon
2018-06-25 14:30 ` bugzilla-daemon
2018-06-26 12:03 ` bugzilla-daemon
2018-06-26 12:04 ` bugzilla-daemon
2018-06-26 12:40 ` bugzilla-daemon
2018-06-26 12:40 ` bugzilla-daemon
2018-06-26 14:58 ` bugzilla-daemon
2018-06-26 16:55 ` bugzilla-daemon
2018-06-27 11:44 ` bugzilla-daemon
2018-06-27 13:39 ` bugzilla-daemon [this message]
2018-06-29 19:59 ` bugzilla-daemon
2018-06-29 20:03 ` bugzilla-daemon
2018-06-30  3:09 ` bugzilla-daemon
2018-06-30  3:10 ` bugzilla-daemon
2018-06-30  4:17 ` bugzilla-daemon
2018-07-01  6:57 ` bugzilla-daemon
2018-07-01  8:56 ` bugzilla-daemon
2018-07-01  9:00 ` bugzilla-daemon
2018-07-14  6:45 ` bugzilla-daemon
2018-08-02 20:02 ` bugzilla-daemon
2018-08-04  4:46 ` 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-199749-2300-MxvaDsnTPG@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).