From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90621] New: Graphics card locks up fom time to time (*ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD))
Date: Fri, 02 Jan 2015 18:08:38 +0000 [thread overview]
Message-ID: <bug-90621-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=90621
Bug ID: 90621
Summary: Graphics card locks up fom time to time (*ERROR*
radeon: ring 0 test failed
(scratch(0x8504)=0xCAFEDEAD))
Product: Drivers
Version: 2.5
Kernel Version: 3.18.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: andros@all-ein.net
Regression: No
Created attachment 162311
--> https://bugzilla.kernel.org/attachment.cgi?id=162311&action=edit
last message in log
The System is locking up, not even magic keys work only hard reset. Not often
maybe 2 times a week.
Screen blackens for a second than gets back again but everything is frozen.
I NEVER do Resume or Hibernation or Standby. So this happens occasionally.
If you search can find some others who have the same problem starting with 3.17
https://www.google.de/search?q=radeon++fence+driver+on+ring+5+use+gpu+addr++and+cpu+addr++%5Bdrm%3Ar600_ring_test%5D+*ERROR*+radeon%3A+ring+0+test+failed+%28scratch%280x8504%29%3D0xCAFEDEAD%29+
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-01-02 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 18:08 bugzilla-daemon [this message]
2015-01-02 18:10 ` [Bug 90621] Graphics card locks up fom time to time (*ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)) bugzilla-daemon
2015-01-02 22:35 ` bugzilla-daemon
2015-01-05 13:31 ` 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-90621-2300@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 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.