All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98520] System randomly crashes / freezes while playing certain games
Date: Fri, 03 Mar 2017 01:14:30 +0000	[thread overview]
Message-ID: <bug-98520-502-N3sPMNWUjk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98520-502@http.bugs.freedesktop.org/>


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

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

--- Comment #36 from Filip <filip@openmailbox.org> ---
Update:
Didn't have the time to test amdgpu-pro on KDE Neon, but freezes have been
reduced in frequency quite a bit starting with linux 4.9.4.

However,
(In reply to Ali Hakkı Demiral from comment #34)
> My problem is almost solved.
> The north bridge of my motherboard is unstable.
> i test rx480 on ubuntu zesty live image, no crash 5+ hours with other
> mainboard. mesa 13.0.2 
> https://community.amd.com/message/2775902#comment-2775902

Turns out I had the similar issue. P35 didn't like the RX460 for some reason,
which has been 100%* stable since I moved it to Gigabyte GA-880GA-UD3H about 20
days ago.

*Except that sometimes I get flickering when (HDMI) monitor wakes from sleep (
solved by switching to TTY and back ), but there were no freezes & nothing of
note in dmesg/xorg logs.

And, like I've mentioned in comment #21, that same P35 board has no issues with
HD6450 which it runs with now.

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

[-- Attachment #1.2: Type: text/html, Size: 2116 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:[~2017-03-03  1:14 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 20:18 [Bug 98520] System randomly crashes / freezes while playing certain games bugzilla-daemon
2016-10-31 20:21 ` bugzilla-daemon
2016-10-31 20:23 ` bugzilla-daemon
2016-10-31 20:26 ` bugzilla-daemon
2016-10-31 20:29 ` bugzilla-daemon
2016-10-31 20:32 ` bugzilla-daemon
2016-10-31 20:40 ` bugzilla-daemon
2016-10-31 20:43 ` bugzilla-daemon
2016-10-31 22:43 ` bugzilla-daemon
2016-11-01  1:04 ` bugzilla-daemon
2016-11-01  1:21 ` bugzilla-daemon
2016-11-01 18:46 ` bugzilla-daemon
2016-11-21  3:52 ` bugzilla-daemon
2016-11-21  3:54 ` bugzilla-daemon
2016-12-02  0:53 ` bugzilla-daemon
2016-12-21  7:32 ` bugzilla-daemon
2016-12-24  0:57 ` bugzilla-daemon
2016-12-27  4:14 ` bugzilla-daemon
2016-12-27 14:17 ` bugzilla-daemon
2016-12-28  2:56 ` bugzilla-daemon
2016-12-28 20:27 ` bugzilla-daemon
2017-01-01 14:42 ` bugzilla-daemon
2017-01-01 18:21 ` bugzilla-daemon
2017-01-01 18:27 ` bugzilla-daemon
2017-01-05  1:51 ` bugzilla-daemon
2017-01-05 11:14 ` bugzilla-daemon
2017-01-05 12:33 ` bugzilla-daemon
2017-01-06  8:36 ` bugzilla-daemon
2017-01-06  8:52 ` bugzilla-daemon
2017-01-13 15:22 ` bugzilla-daemon
2017-01-18 14:07 ` bugzilla-daemon
2017-01-19  6:20 ` bugzilla-daemon
2017-01-20 14:26 ` bugzilla-daemon
2017-01-21  7:17 ` bugzilla-daemon
2017-01-21 17:51 ` bugzilla-daemon
2017-01-23 10:38 ` bugzilla-daemon
2017-01-24  6:27 ` bugzilla-daemon
2017-03-03  0:50 ` bugzilla-daemon
2017-03-03  1:14 ` bugzilla-daemon [this message]
2017-04-02 15:33 ` bugzilla-daemon
2017-05-01 23:19 ` bugzilla-daemon
2017-09-19  8:11 ` bugzilla-daemon
2018-01-19 13:24 ` bugzilla-daemon
2018-01-19 14:28 ` bugzilla-daemon
2018-04-04  0:45 ` bugzilla-daemon
2018-04-04  1:05 ` bugzilla-daemon
2018-04-04  1:06 ` 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-98520-502-N3sPMNWUjk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.