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: Sat, 23 Nov 2013 11:39:48 +0000 [thread overview]
Message-ID: <bug-71864-502-LkLukBqu6O@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71864-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71864
--- Comment #13 from reimth@gmail.com ---
(In reply to comment #12)
> (In reply to comment #11)
> > (In reply to comment #10)
> > > Is this still an issue with a newer kernel? Did you also update your
> > > userspace stack (mesa, xf86-video-ati)?
Bad news: I confirm this bug also on linux kernel 3.8:
Last night I upgraded the server to Ubuntu 12.04.3 with following kernel and
userspace stack versions:
Kernel: 3.8.0
Mesa: 9.1.4
xf86-video-ati: compiled for 1.13.3, module version = 7.1.0
Same configuration with two running X servers, one stand-alone on vt9, one
controlled by mdm on vt7. Firefox and xterm running. After about 1 h striped
screen, turning dark afterwards. Netconsole message a), then kernel oops.
We will stay for now with kernel 3.8. Any ideas how to solve this issue? In a
first step it would be sufficient, if keyboard and mouse control could be
retained, so that the magic keys allow for a smooth reboot. The frequently
frozen kernels are a nightmare.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2070 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-11-23 11:39 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 [this message]
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
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-LkLukBqu6O@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