From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63599] [r600] SUMO2 GPU lockup CP stall (kernel 3.2.47, 3.4, 3.8, 3.9, 3.10)
Date: Wed, 17 Jul 2013 06:22:49 +0000 [thread overview]
Message-ID: <bug-63599-502-862w0evoCr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63599-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63599
--- Comment #16 from Paul Wolneykien <manowar@altlinux.org> ---
Hi, there. I don't absolutely sure I've got the same issue, but at least, my
problem is very close to one reported here.
System:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo
[Radeon HD 6480G]
xorg-server-1.14.2-alt1
xorg-drv-radeon-7.1.0-alt2
Linux 3.9.10-std-def-alt1
I'm asking you to test the following thing, please: try to
modprobe radeon vramlimit=32
On my system it helps, but only a little: the X screen doesn't freeze, just
highly corrupted. And VTs could be switched. The vramlimit=16 option works the
same way, but any other value I've tried -- 64, 128 --- doesn't!
Does it mean something we can use to trace down this bug?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1683 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-07-17 6:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:43 [Bug 63599] New: [r600][r600] GPU lockup CP stall (kernel 3.8, 3.9) bugzilla-daemon
2013-04-16 11:44 ` [Bug 63599] " bugzilla-daemon
2013-04-16 11:45 ` bugzilla-daemon
2013-04-16 11:46 ` bugzilla-daemon
2013-05-17 19:18 ` bugzilla-daemon
2013-05-17 19:52 ` bugzilla-daemon
2013-05-17 19:54 ` bugzilla-daemon
2013-05-17 20:04 ` bugzilla-daemon
2013-05-17 21:47 ` bugzilla-daemon
2013-06-07 18:33 ` bugzilla-daemon
2013-06-07 18:33 ` bugzilla-daemon
2013-06-19 15:29 ` bugzilla-daemon
2013-06-19 15:43 ` bugzilla-daemon
2013-06-27 20:30 ` [Bug 63599] [r600][r600] GPU lockup CP stall (kernel 3.2.47, 3.4, " bugzilla-daemon
2013-07-04 19:51 ` bugzilla-daemon
2013-07-05 14:15 ` [Bug 63599] [r600] SUMO2 GPU lockup CP stall (kernel 3.2.47, 3.4, 3.8, 3.9, 3.10) bugzilla-daemon
2013-07-05 16:04 ` bugzilla-daemon
2013-07-17 6:22 ` bugzilla-daemon [this message]
2013-07-17 6:27 ` bugzilla-daemon
2013-07-17 6:27 ` bugzilla-daemon
2013-07-17 6:30 ` bugzilla-daemon
2013-07-17 12:13 ` bugzilla-daemon
2013-07-17 12:59 ` bugzilla-daemon
2013-07-24 10:18 ` bugzilla-daemon
2013-07-25 22:43 ` bugzilla-daemon
2013-07-25 22:57 ` bugzilla-daemon
2013-08-01 21:30 ` bugzilla-daemon
2013-08-01 21:32 ` bugzilla-daemon
2013-08-01 21:33 ` bugzilla-daemon
2013-08-01 21:33 ` bugzilla-daemon
2013-10-01 23:21 ` bugzilla-daemon
2013-12-21 0:06 ` bugzilla-daemon
2013-12-21 0:39 ` bugzilla-daemon
2013-12-21 0:39 ` bugzilla-daemon
2013-12-21 9:15 ` bugzilla-daemon
2013-12-21 14:32 ` bugzilla-daemon
2013-12-23 12:28 ` bugzilla-daemon
2013-12-23 14:34 ` bugzilla-daemon
2013-12-23 20:20 ` bugzilla-daemon
2013-12-23 21:16 ` 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-63599-502-862w0evoCr@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