From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16376] random - possibly Radeon DRM KMS related - freezes
Date: Sat, 14 Aug 2010 17:03:51 GMT [thread overview]
Message-ID: <201008141703.o7EH3p0I018560@demeter.kernel.org> (raw)
In-Reply-To: <bug-16376-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16376
--- Comment #25 from Martin Steigerwald <Martin@Lichtvoll.de> 2010-08-14 17:03:47 ---
Dave, I hope you do not mind adding you to the CC list, but since this happens
on a ThinkPad T42 your feedback might help.
I thought
----------------------------------------
From: Michel Dänzer <daenzer@vmware.com>
commit e376573f7267390f4e1bdc552564b6fb913bce76 upstream.
This fixes a problem where on low VRAM cards we'd run out of space for
validation.
[airlied: Tested on my M7, Thinkpad T42, compiz works with no problems.]
Signed-off-by: Michel Dänzer <daenzer@vmware.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
----------------------------------------
might have fixed this bug since I read something about this having been tested
on a T42. I did not recognize that it was your comment, so I contacted Michel
Dänzer about it.
He said its unlikely that it will fix my issue, but I should try it anyway.
Well as said above, I tried 2.6.35.2 and it still hung.
You say compiz works without problems for you. I read this as you do not get
any hard freezes with any kernel since 2.6.34 on your ThinkPad T42. Did you try
KDE 4 KWin compositing as well? What X.org / driver versions do you use. There
must be a difference why it works for your ThinkPad, but not for mine.
Here are my current versions:
martin@shambhala:~> apt-show-versions | egrep
"(xserver-xorg/|xserver-xorg-core/|xserver-xorg-video-radeon/|libgl1-mesa-dri/|libdrm2/|libdrm-radeon1/|kde-window-manager/|kdelibs5/)"
kde-window-manager/squeeze uptodate 4:4.4.5-1
kdelibs5/squeeze uptodate 4:4.4.5-1
libdrm-radeon1/experimental uptodate 2.4.21-1
libdrm2/experimental uptodate 2.4.21-1
libgl1-mesa-dri/experimental uptodate 7.8.2-2
xserver-xorg/squeeze uptodate 1:7.5+6
xserver-xorg-core/squeeze uptodate 2:1.7.7-3
xserver-xorg-video-radeon/squeeze uptodate 1:6.13.1-2
As noted above in the bug report: Kernel 2.6.33 works rock stable for me with
Radeon KMS. But that said, I am not even sure whether its a Radeon KMS issue.
That it only happens after a KDE 4 compositing session has started points at
it, but is no proof anyway.
I want to help to provide information to get this fixes, but I feel uneasy
about doing a full bisect between 2.6.33 and 2.6.34. I might start trying out
whether it starts happening at some rc, starting with rc3 and going forwards or
backwards from there.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-08-14 17:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 9:24 [Bug 16376] New: random - possibly Radeon DRM KMS related - freezes bugzilla-daemon
2010-07-13 10:11 ` [Bug 16376] " bugzilla-daemon
2010-07-13 10:15 ` bugzilla-daemon
2010-07-13 10:24 ` bugzilla-daemon
2010-07-13 12:43 ` bugzilla-daemon
2010-07-13 13:32 ` bugzilla-daemon
2010-07-13 15:12 ` bugzilla-daemon
2010-07-13 15:14 ` bugzilla-daemon
2010-07-15 21:12 ` bugzilla-daemon
2010-07-16 18:15 ` bugzilla-daemon
2010-07-16 19:18 ` bugzilla-daemon
2010-07-16 21:09 ` bugzilla-daemon
2010-07-16 21:15 ` bugzilla-daemon
2010-07-23 14:30 ` bugzilla-daemon
2010-07-23 15:17 ` bugzilla-daemon
2010-07-23 15:19 ` bugzilla-daemon
2010-07-25 18:51 ` bugzilla-daemon
2010-07-26 7:08 ` bugzilla-daemon
2010-07-26 14:59 ` bugzilla-daemon
2010-07-28 12:05 ` bugzilla-daemon
2010-07-28 12:51 ` bugzilla-daemon
2010-07-28 14:32 ` bugzilla-daemon
2010-08-01 14:17 ` bugzilla-daemon
2010-08-14 16:47 ` bugzilla-daemon
2010-08-14 16:54 ` bugzilla-daemon
2010-08-14 17:03 ` bugzilla-daemon [this message]
2010-08-23 12:39 ` bugzilla-daemon
2010-08-23 14:20 ` bugzilla-daemon
2010-08-23 14:22 ` bugzilla-daemon
2010-08-23 14:31 ` bugzilla-daemon
2010-08-23 14:37 ` bugzilla-daemon
2010-08-23 14:39 ` bugzilla-daemon
2010-08-23 19:44 ` bugzilla-daemon
2010-08-24 18:30 ` bugzilla-daemon
2010-08-25 10:45 ` bugzilla-daemon
2010-08-26 19:18 ` bugzilla-daemon
2010-08-26 19:28 ` bugzilla-daemon
2010-09-05 7:27 ` bugzilla-daemon
2010-09-05 7:36 ` bugzilla-daemon
2010-09-05 13:29 ` bugzilla-daemon
2010-09-08 16:36 ` bugzilla-daemon
2010-09-08 16:41 ` bugzilla-daemon
2010-09-08 21:49 ` bugzilla-daemon
2010-09-14 13:30 ` [Bug 16376] random Radeon DRM KMS related freezes bugzilla-daemon
2010-12-07 21:18 ` 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=201008141703.o7EH3p0I018560@demeter.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