[Bug 28402] random radeon/kms/drm related freezes with kernel 2.6.34

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=28402

--- Comment #68 from Martin Steigerwald <Martin at Lichtvoll.de> 2010-09-14 06:17:18 PDT ---
I have two questions:

1) Now since we established that the vmembase at zero patch fixes or works
around the problem - while the patch to align vram from comment #47 does not,
and now that I bisected the range of commits down to about 10 and as far as I
understand Da Fox and Lukas even bisected down to exact one commit: What next?
Is the vmembase at zero patch the proper fix? Actually to me it seems more like
a work-around. Is there another fix you propose? I would love to see a fix in
time for 2.6.36, although I still have to figure out on how to get a kernel
after 2.6.33 that does either userspace software suspend or TuxOnIce stably on
my ThinkPad T42 (see bug #18162 regarding userspace software suspend and
tuxonice-devel mailing list for TuxOnIce related stuff).

2) Re Comment #65:

"The AGPMode xorg option isn't used with kms (the AGP mode is set before X
starts when the drm loads).  To force a particular AGP mode with kms, use the
agpmode module parameter: radeon.agpmode=x where x=-1,1,2,4,8.  -1 disables AGP
and uses the on-chip gart mechanism instead."

Is it necessary? How do I find out with AGP mode is used. I'd prefer when it
used best AGP mode (that should be 4x on my ThinkPad T42) automatically.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.