From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71864] [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
Date: Mon, 02 Dec 2013 10:00:01 +0000 [thread overview]
Message-ID: <bug-71864-502-g49mm9P1ls@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71864-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71864
--- Comment #18 from reimth@gmail.com ---
(In reply to comment #17)
> I would suggest trying newer versions of the userspace gfx stack (mesa,
> xf86-video-ati). GPU resets are usually caused by bad command combinations
> sent by the userspace drivers.
Status with following kernel and userspace stack versions:
Kernel: 3.8.0
Mesa: 9.1.7
xf86-video-ati: compiled for 1.13.3, module version = 7.1.0
The system is more stable again. We had only one kernel freeze and this was
preceeded by a failed GPU reset.
One root cause of the previously increased instability seems to be that the
second X server runs wine-1.4. Wine requires also the 32-bit i386 userspace
drivers, which had to be manually upgraded to the above mentioned latest
versions.
Is the wine required combined use of 32-bit (i386) and 64-bit (amd64) userspace
drivers on an AMD platform supposed to be valid and stable approach?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1887 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-12-02 10:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 8:42 [Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) bugzilla-daemon
2013-11-21 8:44 ` [Bug 71864] " bugzilla-daemon
2013-11-21 8:44 ` bugzilla-daemon
2013-11-21 8:45 ` bugzilla-daemon
2013-11-21 8:45 ` bugzilla-daemon
2013-11-21 8:50 ` bugzilla-daemon
2013-11-21 8:51 ` bugzilla-daemon
2013-11-21 8:55 ` bugzilla-daemon
2013-11-21 8:56 ` bugzilla-daemon
2013-11-21 9:00 ` bugzilla-daemon
2013-11-21 16:10 ` bugzilla-daemon
2013-11-22 14:49 ` bugzilla-daemon
2013-11-22 15:08 ` bugzilla-daemon
2013-11-23 11:39 ` bugzilla-daemon
2013-11-23 21:41 ` bugzilla-daemon
2013-11-24 15:37 ` bugzilla-daemon
2013-11-24 16:17 ` bugzilla-daemon
2013-11-24 17:15 ` bugzilla-daemon
2013-12-02 10:00 ` bugzilla-daemon [this message]
2013-12-02 17:55 ` bugzilla-daemon
2013-12-05 10:23 ` bugzilla-daemon
2013-12-05 15:10 ` bugzilla-daemon
2019-11-19 8:40 ` 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-71864-502-g49mm9P1ls@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