From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98298] System freezes 380X
Date: Mon, 17 Oct 2016 19:03:13 +0000 [thread overview]
Message-ID: <bug-98298-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98298
Bug ID: 98298
Summary: System freezes 380X
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: kuehner.moritz@gmail.com
Created attachment 127368
--> https://bugs.freedesktop.org/attachment.cgi?id=127368&action=edit
dmesg output
I'm having random system freezes with my Amd R9 380X. The freezes happen under
3d load maybe once a hour.
This happens on both Arch (linux 4.7) and Ubuntu 16.04 (4.4 with backports).
The freeze itself produces no output (nether kernel nor any other log) but I
just found that after 2 min the kernel will produce a hung task info. (See
attachment)
The freeze affects all graphical output: No mouse movement or switching to
virtual terminal. The rest of the system still works.
Please let me know of any debugging steps I can try.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2571 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
next reply other threads:[~2016-10-17 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 19:03 bugzilla-daemon [this message]
2016-10-26 20:03 ` [Bug 98298] System freezes 380X bugzilla-daemon
2016-12-11 16:19 ` bugzilla-daemon
2016-12-11 16:19 ` 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-98298-502@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;
as well as URLs for NNTP newsgroup(s).