On Fri, Sep 19, 2008 at 7:02 AM, Jeff Chua <[EMAIL PROTECTED]>
wrote:
> Swtiching to console resulted in X crashing. Same problem with trying
> to suspend to ram.
>
> X: intel_bufmgr_fake.c:1302: intel_bufmgr_fake_evict_all: Assertion
> `((&bufmgr_fake->fenced)->next == (&bufmgr_fake->fenced))' failed.
>
This turns out to be the drm module that's emitting this problem.
Taking out the assert() calls fixed the problem with switching to VT
consoles and suspending to ram.
I don't know what's the implication of taking away these two calls. Please
advise.
Thanks,
Jeff
--- /v6/src2/cvs/drm/drm/libdrm/intel/intel_bufmgr_fake.c 2008-09-12
20:02:27 +0800
+++ /v6/src2/drm/drm/libdrm/intel/intel_bufmgr_fake.c 2008-09-19 08:35:29
+0800
@@ -1296,12 +1296,6 @@
*/
dri_bufmgr_fake_wait_idle(bufmgr_fake);
- /* Check that we hadn't released the lock without having fenced the last
- * set of buffers.
- */
- assert(DRMLISTEMPTY(&bufmgr_fake->fenced));
- assert(DRMLISTEMPTY(&bufmgr_fake->on_hardware));
-
DRMLISTFOREACHSAFE(block, tmp, &bufmgr_fake->lru) {
/* Releases the memory, and memcpys dirty contents out if necessary. */
free_block(bufmgr_fake, block);
_______________________________________________
xorg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xorg
