From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16140] Suspend To RAM/ Resume broken - Radeon KMS on RV250
Date: Sun, 10 Oct 2010 13:41:06 GMT [thread overview]
Message-ID: <201010101341.o9ADf6hc031198@demeter2.kernel.org> (raw)
In-Reply-To: <bug-16140-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16140
--- Comment #32 from Sedat Dilek <sedat.dilek@gmail.com> 2010-10-10 13:40:58 ---
(Patch see https://bugzilla.kernel.org/show_bug.cgi?id=16140#c26)
With applying my patch from above, it's this section (Line #1028 and following)
from r100_cp_init() doing the problem:
940 int r100_cp_init(struct radeon_device *rdev, unsigned ring_size)
...
1026 radeon_ring_start(rdev);
1027 r = radeon_ring_test(rdev);
1028 if (r) {
1029 DRM_ERROR("radeon: cp isn't working (%d).\n", r);
1030 return r;
1031 }
1032 rdev->cp.ready = true;
1033 return 0;
1034 }
...
Replacing "if (r) {" with "if (WARN_ON(r)) {" shows the above Call-trace.
I looked into r600.c source-code and put "rdev->cp.ready = true;" before Line
"r = radeon_ring_test(rdev);", not helping.
Again inspired from r600.c, I put Line #966 "r100_cp_load_microcode(rdev);"
after "r = radeon_ring_init(rdev, ring_size);", this resulted in a
not-so-garbled screen, after hanging:
pm-resume in X -> switching to vt-1 -> killing X -> restarting startx
This is doing no harm, see my logs.
- DRM_ERROR("radeon: ring test failed (sracth(0x%04X)=0x%08X)\n",
+ DRM_ERROR("radeon: ring test failed (scratch(0x%04X)=0x%08X)\n",
I am not sure what you mean with "radeon driver": the one in the kernel or the
DDX (xf86-video-ati).
One NOTE:
In Line #3728 there is a commented "r100_gpu_init(rdev);", it is nowhere
"defined". I see in r600.c a *_gpu_init() and a *_cp_start() in case of
resuming. Just a hint, if you wanna compare or dig into it.
IIRC it would make sense to interprete correctly the Call-trace, I am not that
familiar with "the internals".
Sorry, I don't wanna experiment with older Linux-Kernels as my graphics driver
stack is mostly latest-stable or from GIT, not sure what will happen.
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/gpu/drm/radeon/r100.c;h=e151f16a8f86d73090ec6a4eb17a3590661868db;hb=HEAD#l1028
[2]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/gpu/drm/radeon/r100.c;h=e151f16a8f86d73090ec6a4eb17a3590661868db;hb=HEAD#l966
[3]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/gpu/drm/radeon/r100.c;h=e151f16a8f86d73090ec6a4eb17a3590661868db;hb=HEAD#l3728
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
--
next prev parent reply other threads:[~2010-10-10 13:41 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16140-2300@https.bugzilla.kernel.org/>
2010-06-23 17:09 ` [Bug 16140] Suspend To RAM/ Resume broken - Radeon KMS on RV250 bugzilla-daemon
2010-06-23 17:20 ` bugzilla-daemon
2010-06-23 21:02 ` bugzilla-daemon
2010-06-23 21:14 ` bugzilla-daemon
2010-06-23 21:17 ` bugzilla-daemon
2010-06-24 17:20 ` bugzilla-daemon
2010-08-13 9:43 ` bugzilla-daemon
2010-08-13 9:48 ` bugzilla-daemon
2010-08-28 12:35 ` bugzilla-daemon
2010-08-28 12:36 ` bugzilla-daemon
2010-08-28 12:43 ` bugzilla-daemon
2010-09-17 11:30 ` bugzilla-daemon
2010-09-17 11:34 ` bugzilla-daemon
2010-09-17 11:35 ` bugzilla-daemon
2010-09-17 11:36 ` bugzilla-daemon
2010-09-17 15:58 ` bugzilla-daemon
2010-09-20 19:45 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:28 ` bugzilla-daemon
2010-10-07 21:29 ` bugzilla-daemon
2010-10-07 21:30 ` bugzilla-daemon
2010-10-07 21:31 ` bugzilla-daemon
2010-10-07 21:32 ` bugzilla-daemon
2010-10-07 21:38 ` bugzilla-daemon
2010-10-07 22:31 ` bugzilla-daemon
2010-10-07 22:32 ` bugzilla-daemon
2010-10-08 9:00 ` bugzilla-daemon
2010-10-08 9:01 ` bugzilla-daemon
2010-10-08 9:02 ` bugzilla-daemon
2010-10-08 11:52 ` bugzilla-daemon
2010-10-08 11:56 ` bugzilla-daemon
2010-10-08 11:59 ` bugzilla-daemon
2010-10-08 12:00 ` bugzilla-daemon
2010-10-08 17:49 ` bugzilla-daemon
2010-10-08 17:52 ` bugzilla-daemon
2010-10-10 13:41 ` bugzilla-daemon [this message]
2010-10-10 23:16 ` bugzilla-daemon
2010-10-29 18:00 ` bugzilla-daemon
2010-11-16 22:55 ` bugzilla-daemon
2010-12-04 16:22 ` bugzilla-daemon
2010-12-13 5:27 ` bugzilla-daemon
2011-03-07 18:49 ` [Bug 16140] [RADEON:KMS:RV250:RESUME] suspend to RAM resume broken bugzilla-daemon
2011-03-07 20:09 ` bugzilla-daemon
2011-03-07 20:24 ` bugzilla-daemon
2011-03-08 18:32 ` bugzilla-daemon
2011-03-08 18:34 ` bugzilla-daemon
2011-03-22 8:38 ` bugzilla-daemon
2011-08-29 3:45 ` bugzilla-daemon
2012-02-09 4:08 ` bugzilla-daemon
2012-02-09 13:54 ` bugzilla-daemon
2012-02-09 16:12 ` bugzilla-daemon
2012-02-09 16:42 ` bugzilla-daemon
2012-11-23 18:33 ` bugzilla-daemon
2013-12-10 21:43 ` 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=201010101341.o9ADf6hc031198@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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